Warren, thanks for the additional info. I assume that the yottamaster device runs Linux, just like 99% of other such devices. as to whether it uses linux software raid or some cheap (megaraid???) chipset, I don't know, nor know how to tell. but I'll check that URL you sent and see what happens. Thanks again! Fred On Sat, Jan 2, 2021 at 12:28 PM Warren Young <warren at etr-usa.com> wrote:> On Jan 2, 2021, at 9:55 AM, Fred <fred.fredex at gmail.com> wrote: > > > > Plantronics USB headset/microphone? > > Yottamaster RAID-1 storage (USB3)? > > Behringer USB audio interface? > > Logitech wireless mouse? > > Leopold USB keyboard? > > HID devices won?t go to sleep when the computer does, else they couldn?t > wake it back up. (Keyboard & mouse, mainly.) > > The two audio interfaces may or may not sleep. Try checking their > indicator LEDs when the computer goes to sleep: I?d expect them to visibly > show that they?ve gone to sleep if they do. If they do, then on wake, they > *could* do this sort of thing. > > I?d go after the RAID enclosure first, particularly if it?s hardware RAID, > since that means it?s ?clever,? thus suspect. Check that you?ve got the > current firmware: > > https://www.yottamaster.com/?route=common/driver > > If it?s one of their JBOD models, requiring that you do some sort of > software RAID, I?d expect a much different report in the kernel log if the > corresponding software RAID component had a bug, which would mean it?s got > some fundamental USB compatibility problem if that?s the device causing the > problem. Again, check for firmware updates. > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >
> I assume that the yottamaster device runs Linux, just like 99% of > other > such devices. as to whether it uses linux software raid or some cheap > (megaraid???) chipset, I don't know, nor know how to tell. but I'll > check > that URL you sent and see what happens.Just add "x-systemd.automount,x-systemd.idle-timeout=10min" in the fstab mount options , or create an ".mount" + ".automount" entries for it (autofs is also an option) and test. The "x-systemd.automount" option will tell systemd to create a ".automount" unit which will monitor the mount point and automatically mount your drive, while the idle-timeout will tell systemd to automatically umount the share when not in use (ls, df, du and others count as usage and reset the counter). Also , if you use 7.6 - there is a bug in sysstat that forces autofs and systemd's automounter to mount the share. Best Regards, Strahil Nikolov
On Jan 2, 2021, at 11:17 AM, Fred <fred.fredex at gmail.com> wrote:> > I assume that the yottamaster device runs Linux, just like 99% of other > such devices.99% of NAS boxes, maybe, but not dumb RAID boxes like the one I believe you?re referring to. (And I doubt even that, with the likes of FreeNAS extending down from the enterprise space where consumer volume can affect that sort of thing.) I have more than speculation to back that guess: the available firmware images are far too small to contain a Linux OS image, their manuals don?t talk about Linux or GPL that I can see, and there?s no place to download their Linux source code per the GPL. While doing this exploration, I?ve run into multiple problems with their web site, which strengthens my suspicion that this box is your culprit. If they?re this slipshod with their marketing material, what does that say about their engineering department?