ralphbecket

No problem, I'm just grateful to receive advice (for which many thanks!). I'll try both your suggestions over the weekend and let you know how it works out. What's interesting is that this is a replacement flash drive: I was seeing the same kinds of problems with my previous flash, but this suggests the problem lies elsewhere.

Hi, I've been trying to get WoL to work reliably under unRAID for nearly two years now. I recently tried sending my unRAID box to sleep via the Dynamix S3 Sleep plugin, waking it using 'rtcwake' (see https://forums.lime-technology.com/topic/58194-scheduled-wake-from-sleep/), which appeared to work, but after waking there was no 'Docker' tab or apps and the system was in a rather confused state. Clicking on the 'Log' button, I got the following immediately after the wake-from-sleep: Jun 20 11:49:32 Tower kernel: xhci_hcd 0000:03:00.0: HC died; cleaning up Jun 20 11:49:32 Tower kernel: dpm_run_callback(): usb_dev_resume+0x0/0x10 returns -22 Jun 20 11:49:32 Tower kernel: PM: Device 6-2 failed to resume async: error -22 Jun 20 11:49:32 Tower kernel: PM: resume of devices complete after 11021.862 msecs Jun 20 11:49:32 Tower kernel: Restarting tasks ... Jun 20 11:49:32 Tower kernel: usb 6-2: USB disconnect, device number 2 Jun 20 11:49:32 Tower kernel: done. Jun 20 11:49:32 Tower kernel: udevd[18947]: inotify_add_watch(5, /dev/sda, 10) failed: No such file or directory Jun 20 11:49:32 Tower s3_sleep: Wake-up from sleep mode Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed Jun 20 11:49:32 Tower root: Jun 20 11:49:32 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Jun 20 11:49:32 Tower root: Jun 20 11:49:32 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Jun 20 11:51:50 Tower kernel: fat__get_entry: 182 callbacks suppressed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed Jun 20 11:51:50 Tower root: Jun 20 11:51:50 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed Jun 20 11:51:50 Tower root: Jun 20 11:51:50 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 This is characteristic of the sleep issues that have plagued my unRAID experience. Has anyone else had this problem and found a solution?

@primeval_god, do you happen to know if there's something else required in the 'before sleep' command to prevent that flash drive problem from occurring on wake?

@primeval_god Ha ha, that worked! Thanks a million. I just tried out the following experiment and it worked perfectly: https://ragsagar.wordpress.com/2011/08/15/how-to-automatically-wake-up-your-computer-at-a-particular-time-resume-by-rtc-alarm-in-arch-linux/ I spoke too soon, I think I see what has been corrupting my flash drives now. Resuming from sleep as above, I observe that my docker tab is gone and the log file contains the following: Jun 20 11:49:32 Tower kernel: xhci_hcd 0000:03:00.0: HC died; cleaning up Jun 20 11:49:32 Tower kernel: dpm_run_callback(): usb_dev_resume+0x0/0x10 returns -22 Jun 20 11:49:32 Tower kernel: PM: Device 6-2 failed to resume async: error -22 Jun 20 11:49:32 Tower kernel: PM: resume of devices complete after 11021.862 msecs Jun 20 11:49:32 Tower kernel: Restarting tasks ... Jun 20 11:49:32 Tower kernel: usb 6-2: USB disconnect, device number 2 Jun 20 11:49:32 Tower kernel: done. Jun 20 11:49:32 Tower kernel: udevd[18947]: inotify_add_watch(5, /dev/sda, 10) failed: No such file or directory Jun 20 11:49:32 Tower s3_sleep: Wake-up from sleep mode Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed Jun 20 11:49:32 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed Jun 20 11:49:32 Tower root: Jun 20 11:49:32 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Jun 20 11:49:32 Tower root: Jun 20 11:49:32 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Jun 20 11:51:50 Tower kernel: fat__get_entry: 182 callbacks suppressed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8192) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8193) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8194) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8195) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8196) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8197) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8198) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8199) failed Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8200) failed Jun 20 11:51:50 Tower root: Jun 20 11:51:50 Tower root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Jun 20 11:51:50 Tower kernel: FAT-fs (sda1): Directory bread(block 8201) failed Jun 20 11:51:50 Tower root: Jun 20 11:51:50 Tower root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39

Hmm, I'll try it: we've just installed a new router, it's possible the previous one was having trouble. On the other hand, I notice that unRAID comes with 'rtcwake' installed, but when I try it I get a write error: root@Tower:~# rtcwake -s 30 -v rtcwake: assuming RTC uses UTC ... Using UTC time. delta = -4 tzone = 0 tzname = UTC systime = 1497921001, (UTC) Tue Jun 20 01:10:01 2017 rtctime = 1497921005, (UTC) Tue Jun 20 01:10:05 2017 alarm 0, sys_time 1497921001, rtc_time 1497921005, seconds 30 rtcwake: wakeup from "suspend" using /dev/rtc0 at Tue Jun 20 01:10:36 2017 suspend mode: suspend; suspending system rtcwake: write error

Hi, @Fireball3. The Windows Task Scheduler includes an option to wake the computer from sleep if necessary, which has always worked reliably for me without requiring any extra BIOS tweaks. I'm just wondering how Windows manages this, but not Linux. Re: the iffy WoL results after the unRAID box has been sleeping for a day or so, yes: sometimes it will wake when I send the packed from another PC, sometimes it won't. I haven't been able to discern any pattern, unfortunately.

Thanks for the quick reply, I'll give that a go in the next few days. I wonder what Windows does to make this work that doesn't require BIOS changes.

Hi, like many, I would like my unRAID box to sleep when it is idle and either wake-on-lan or wake on schedule. I've installed the Dynamix S3 sleep plugin and it sort of works (that is, it works while I'm at my desk sending the unRAID box to sleep then reviving it by sending the WoL packet, but if I leave the unRAID box sleeping for a day and try again the results are very iffy). I have found absolutely no way of getting this box to wake on schedule other than by having another (Windows) PC wake up to send the WoL packet to the unRAID box! I'm sure there has to be something more elegant than this, can anyone tell me what I'm missing? For reference, I'm running a pretty vanilla set-up with the latest version of unRAID, on a motherboard that supports S3.

Hi, my unRAID box has worked mostly reliably for a couple of years, but has become increasingly unreliable of late. I've included a couple of diagnostics ZIP files here. My set up is 1 x 4 TB data HDD, 1 x 4 TB parity HDD, 1 x SSD cache drive. The main symptom is that the thing works for a few days, then stops. When I restart it, I've lost all my docker apps -- there isn't even a docker tab on the web UI. I suspect that the SSD may be part of the problem, but this time it seems to be able to find the SSD (in the past, when it's played up, it has been unable to find the SSD until I've powered the whole thing down for a day or two). Help! tower-diagnostics-20170419-2315 Working.zip tower-diagnostics-20170501-2000 Not quite right.zip

Anybody out there? I'd really appreciate advice on this.

Okay, I can now post "before" and "after" diagnostics illustrating the kind of problem that keeps recurring. The "not quite right" file has the server with the array running and, this time, the SSD cache drive present and recognised, but no docker apps, which means no Plex, which is a big problem here. Any help would be much appreciated, thanks! tower-diagnostics-20170419-2315 Working.zip tower-diagnostics-20170501-2000 - not quite right.zip

I have a 60 GByte SSD cache drive installed in my box (I'm running the latest version of unRAID). I have the Dynamix sleep plugin installed and that appears to work reasonably well, so the machine isn't even running 24/7. However, every few days the box gets into an unusable state and the symptom is always that it can no longer find the SSD cache drive. If I power down and leave it off for a few hours before restarting, things come back to life as expected, including the SSD. The SSD is in a well ventilated location in the case. I'm not sure why this should be happening. * Is there any way of checking the "health" of an SSD? * If the SSD is faulty and needs replacing, what do I need to do to copy the data on it to its replacement? Advice in words of one syllable would be much appreciated!

Sorry for the delay in responding (work, life, etc.). I copied over a backup on to the USB stick and, thank heavens, we're back in action -- many thanks indeed! I have a suspicion a series of power cuts may have been responsible, but either way, this is a good result and everybody's help is much appreciated!

I took the backup by physically removing the USB flash drive when the unRAID box started acting up (i.e., had lost the array, wouldn't boot to the web UI, etc.) I will try restoring the backup copy of super.dat to the flash drive config directory and see if that works. Thanks again for your help on this one.

Many thanks for this! So it's definitely a corrupt flash drive? I wonder how that could have happened. I've found a super.dat in the backup I took of the flash drive the other night: %unRAID Backup 2017-03-21%\logs\tower-diagnostics-20170205-1532.zip\tower-diagnostics-20170205-1532\config\super.dat which is a 4 Kbyte binary file of some kind with a modification date of 2017-02-05 -- I haven't changed anything other than the sleep plugin settings in over a year and a half. Assuming I can use this file to recover my previous state, can anyone tell me in simple terms what I should do next?