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?

@kizer I haven't tried booting another machine with the flash drive, but I've plugged it into my windows box to take a backup -- everything appeared fine there.

[Edit: I'm an idiot: my box has two HDDs, one data, one parity, not three as I originally wrote!] Hi, my unRAID box stopped working properly yesterday and I'm lost as to how to diagnose the problem. My box is running unRAID 6.2.4. Installed are three two 4 TB discs (one parity, two data), a 60 GB SDD cache drive, and the obligatory flash drive. This is all on an Intel G1840 with 4 GB RAM. The symptoms: - the box will not boot properly; - I can ssh into it and run bash etc. (although PuTTY warns that the ssh keys have changed, which it's never done before, and I'm not asked for the password, which I always had to provide in the past); - however there is no web UI; - running `ps aux | grep -i emhttp` comes up blank; - there is nothing obviously alarming in /var/log/syslog; - /boot/config/plugins/ contains only /dynamix/ and that is empty -- which is odd, because I definitely had the Dynamix 'sleep' plugin installed and running; - after a few hours trawling the forums for advice, I tried this magic incantation in bash: `nohup /usr/local/sbin/emhttp &` which did succeed in getting the web UI up and running; - however, I was required to re-enter my licence key URL (the GUID for my USB flash drive was recognised correctly); - all my configuration is missing -- it's as though I have a blank system again; - I can re-start the array with the two data HDDs, but it can't find the parity HDD (i.e., nothing is listed in the drop-down menues on the 'Main' web tab); - if I reboot after doing this, it still won't start the web UI; - all my Docker apps (Plex etc.) appear to be gone -- at least, there is no Docker tab on the web UI. I've gone to the web UI Tools > Hardware Profile page and clicked 'Upload'. I've gone to the web UI Tools > Diagnostics page, clicked 'Download', and attached the resulting ZIP file to this message. I'd be tremendously grateful for any help at all at this point! Ralph tower-diagnostics-20170321-1416.zip

It's the weirdest thing. I write about the problem here and *poof*, it mysteriously vanishes... Thanks everybody for the advice, anyway.

To add insult to injury, the problem appears intermittent. I just tried WoL and it worked (as it sometimes does). I have no idea why it isn't reliable.

Hi, I have a happy UnRAID system except for one thing: wake-on-lan basically doesn't work properly. Here's the symptom: If I put it to sleep from the Main page, then I can reliably wake it again by sending the appropriate magic WoL packet. If the server goes to sleep by itself, it does not respond to the WoL packet. Instead I have to prod it back into life by tapping the power button. Most annoying when the server is in an out-of-the way place. Here's what I have installed: UnRAID 6.2.4 Dynamix Sleep plugin 3.0.4 Dynamix is configured to use sleep mode; exclude 10:00-13:00 and 17:00-23:00 (I rather hoped this meant the server would automatically wake during these periods); wait 60 minutes after array inactivity; wait for < 100kbps ethernet traffic; not wait for user inactivity; use WoL option 'g' before sleep. The output from 'ethtool eth0' includes "Supports Wake-on: pumbg" and "Wake-on: g". I've set Dynamix Sleep to log what it's doing and here's what I see: Mar 2 00:01:53 Tower s3_sleep: Enter sleep state now Mar 2 00:01:53 Tower kernel: PM: Syncing filesystems ... done. Mar 3 15:15:02 Tower kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. Mar 3 15:15:02 Tower kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Mar 3 15:15:02 Tower kernel: Suspending console(s) (use no_console_suspend to debug) Mar 3 15:15:02 Tower kernel: sd 6:0:0:0: [sdd] Synchronizing SCSI cache Mar 3 15:15:02 Tower kernel: sd 6:0:0:0: [sdd] Stopping disk Mar 3 15:15:02 Tower kernel: serial 00:07: disabled Mar 3 15:15:02 Tower kernel: serial 00:07: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: parport_pc 00:05: disabled Mar 3 15:15:02 Tower kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache Mar 3 15:15:02 Tower kernel: sd 2:0:0:0: [sdc] Stopping disk Mar 3 15:15:02 Tower kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache Mar 3 15:15:02 Tower kernel: sd 1:0:0:0: [sdb] Stopping disk Mar 3 15:15:02 Tower kernel: PM: suspend of devices complete after 1529.904 msecs Mar 3 15:15:02 Tower kernel: PM: late suspend of devices complete after 0.247 msecs Mar 3 15:15:02 Tower kernel: pcieport 0000:00:1c.4: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: pcieport 0000:00:1c.3: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI Mar 3 15:15:02 Tower kernel: PM: noirq suspend of devices complete after 10.732 msecs Mar 3 15:15:02 Tower kernel: ACPI: Preparing to enter system sleep state S3 Mar 3 15:15:02 Tower kernel: PM: Saving platform NVS memory Mar 3 15:15:02 Tower kernel: Disabling non-boot CPUs ... Mar 3 15:15:02 Tower kernel: smpboot: CPU 1 is now offline Mar 3 15:15:02 Tower kernel: ACPI: Low-level resume complete Mar 3 15:15:02 Tower kernel: PM: Restoring platform NVS memory Mar 3 15:15:02 Tower kernel: Enabling non-boot CPUs ... Mar 3 15:15:02 Tower kernel: x86: Booting SMP configuration: Mar 3 15:15:02 Tower kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2 Mar 3 15:15:02 Tower kernel: cache: parent cpu1 should not be sleeping Mar 3 15:15:02 Tower kernel: CPU1 is up Mar 3 15:15:02 Tower kernel: ACPI: Waking up from system sleep state S3 Mar 3 15:15:02 Tower kernel: ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: pcieport 0000:00:1c.4: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI Mar 3 15:15:02 Tower kernel: PM: noirq resume of devices complete after 11.295 msecs Mar 3 15:15:02 Tower kernel: PM: early resume of devices complete after 0.149 msecs I have very little idea of what's really going on here, but those "System wakeup enabled by ACPI" followed by "System wakeup disabled by ACPI" messages look suspicious to me. If anyone could offer some advice in words of few syllables (assume you're talking to someone who knows nothing!) that would be very kindly received.

I'm embarrassed to say I found the "excluded hours" option for the Sleep plugin; this seems to do just what I want, waking the computer during the hours specified. Thanks everyone for your suggestions.

Thanks, but surely there must be some way of doing this at the OS level? Windows does this just fine. I really don't want to have to reboot every time I have to change the wake settings.

Hi, I'm running an up-to-date version of unRAID (6.1.9, I believe), I have installed the Dynamix Sleep plugin, and I have enabled wake-on-lan on the motherboard. My unRAID machine will now happily sleep after the disks spin down (per the Sleep plugin schedule) or if I use the 'Sleep' button from the web UI. WoL is working perfectly. What I haven't fathomed yet, is how to schedule the machine to wake up for various maintenance (e.g., I would like my Plex server to update the libraries every day at 3 AM -- but this currently won't happen when the machine is asleep). I could set up a scheduled task on one of my Windows boxes to send the WoL command, but it seems rather inelegant to have to schedule one PC just to wake up another PC! Can anyone offer some advice here as to how to make my unRAID machine wake up for maintenance at a given time every day? Many thanks!

D'oh! I am an idiot. I'd left my docker.img on disk1, I had forgotten to move it to the cache drive when I installed it. That now done, all is fixed.

Yup, it's Plex. Well, off to the Plex forums now!