curtis-r

Installing CA and then rclone through apps did the trick (thanks), but when I try to create the rclone config, when I get to the Amazon authentication, the unraid browser brings me to an amazon page, 'Error Summary: 400 bad request,' plus a bunch of other stuff. I've tried it with the Client Id & Secret ID blank, and filled-in through the terminal config process. I've tried manually loginng in to Amazon before the link also.

Is rclone working with unraid 6.5.3? I cannot get it to install using the plugin URL. Screenshot attached. I've tried somewhat manually using rclones' "Linux installation from precompiled binary" instructions, but I can't get past the Amazon verification. Tried using unraid GUI mode, but the link returns an Amazon error page. Also, rclone never shows under unraid's plugins.

What doe the 'Set WOL options before sleep' options mean. I searched but cannot find what p, u, m, b, g all mean. Could this be part of my problem? Mine is set to 'g'.

Excellent suggestions, especially the disabling the WOL. The only minor catch is that on very rare occasions I'll remote-in to my home and need to wake the unraid via WOL. For now I'll just delete the WOL shortcut from my home desktop PCs after I've done some repeated tests. thanks.

Good idea but maybe what I'll do is just not use WOL. It appears that if I only wake unraid via the power switch, all is fine. Unless some new information presents itself... thanks.

Good observation. The difference is that #3 follows a wake via WOL. It's only after a WOL success does then a WOL not work and the power switch causes a reboot. Of course manually shutting down my unraid is safest and works, but I'm primarily using it as a media server and it is not practical to have people understand and follow those steps each time after they are done using the server.

Finally ran some tests, which basically validate my issue of things being screwy after a successful WOL where by WOL no longer works and the power switch causes a reboot. Super weird. Though I broke the following into steps, it is actually one continuous sequence: 1) WOL -> auto sleep -> power sw. -> reboots (when it should just wake) 2) Sleep GUI Button -> WOL -> wakes normally 3) Sleep GUI Button -> WOL -> doesn't wake -> power sw. -> reboots 4) Stop array -> Power down -> WOL -> boots normally (no parity check) 5) Sleep GUI Button -> WOL -> doesn't wake -> power sw. -> reboots The bottom line is what different from waking via WOL vs. a power-switch? Either with Unraid or my mobo, something is critically different.

Exactly! Though I'm going to run some more tests, your idea to try the WOL->Sleep->WOL won't work because in addition to the power switch causing a reboot after WOL->Sleep, the subsequent WOL doesn't work at in that scenario. I'm fairly certain I changed the BIOS battery when I switched to this mobo 2 months ago.

I suppose then the question is whether the behavior I'm seeing is related to the Sleep function or something else. Why would waking by WOL be any different than the power switch?

@jonathanm Though Sleep was previously a Dynamix plug-in, it is included in v6. Regardless, it's odd that most of the time my unraid wakes fine from an automatic sleep. My problem is that it seems that if I use WOL to wake my unraid and later it automatically sleeps, the following attempt to wake via WOL doesn't work, and pressing the power switch causes a hard reboot when otherwise the power switch wakes without incident. Thanks for your interest, though.

The sleep that the unraid is waking from, occasionally rebooting and running a parity check, is an automatic sleep via the built-in function. Is there a way to prevent the automatic parity check after a forced reboot?

I wouldn't mind this issue if I could prevent an automatic parity check after a hard reboot. Anyway to do this?

Oops. I meant I use the power switch. My bad.

I realize a lot has been posted about WOL and sleep, but I think I have something a bit unusual: I usually wake my unraid from sleep by pressing the reset switch. The problem I've finally determined is if I instead wake my unraid through Wake on Lan (WOL), the next time unraid sleeps and I then try to wake the unraid through the reset switch, it actually forces a reboot and then an auto parity check. Why would waking the unraid from WOL lead to a reboot the next time it sleeps and I press the reset switch?

My Norco 4020 was also way too loud for my home theater rack, thus pimped mine too: Figured it might be worth $12 for each of the 3 XLF 140mm fans since they claim <16dB. Simply epoxied them together, with a strip of aluminum across the top. Two strips of wood, held in place with screws through the case side, to keep the fan assembly in place. I also built a mini thermostat to control the fans. See the variable resistor sticking through the front of my case. Honestly, there is no sound from these fans on, so the thermostat is simply to save a some watts of power when the system doesn't need the fans.