Hi community,

 

I'm using the latest version (6.12.8) of Unraid in a 3x20 TB TOSHIBA MG10ACA20TE Setup. In order to save power, I'd like to make use of the sleep mode and wake on the server either via PC or mobile phone. So I used this guide (https://docs.unraid.net/unraid-os/guides/wol-setup-for-unraid). It worked for a couple of times (wake up via PC -> Server) until I experienced a "device disabled" issue on one of my drives. After the first nervous breakdown, I checked the SMART data, it looked fine, so I started to rebuild the array which was successful.

 

Now, a couple of days later I found the "Dynamix S3 Sleep" app on the Community Market, but unfortunately after the first usage, I ran into the same "device disabled" issue again. So I'm pretty sure that the Sleep mode somehow negatively impacts my array / one disk within the array.

 

The disk itself is brand-new, I did a complete Unassigned Devices Pre-Clear before to be sure that the HDDs are (most likely) fine.

 

I would be very happy if one of you could give me some guidance:

- Any idea how to re-enable the disk without a painfully-long rebuild?

- Any idea what could cause the issue in regards to the sleep mode?

 

Thanks a lot for your support.

 

Best,

Blueeye

26 minutes ago, Blueeye said:

- Any idea how to re-enable the disk without a painfully-long rebuild?

If nothing was written to the emulated disk you could do a new config, but then will need a correcting parity check, and that will take the same time, that's why we usually recommend rebuilding instead.

 

27 minutes ago, Blueeye said:

Any idea what could cause the issue in regards to the sleep mode?

Not with out the diags showing the error, but I would say sleep can be a good suspect, try running the server without sleeping for a few days.

Thanks for the reply. The diags are lost after each reboot correct? Thanks.

 

Guess I have to re-start just another 28-32 hours rebuild 😕

20 minutes ago, Blueeye said:

The diags are lost after each reboot correct?

The syslog is, it should remain after sleep/wake up, it keeps happening you can also enable the syslog server.

Hi @JorgeB,

 

thanks for your reply. The rebuild was done successful, I will now monitor the "device disbabled" issue. I will make use now for some time of the regular shutdown function and combined this with a "User Script" App change to set WOL g after every array start (which basically allows me to do exactly the same as with the sleep mode, the only downside is that it requires more time to boot than to wake up from sleep). I've tested a mobile phone / PC WOL already successfully.

 

Obviously the sleep mode is a little bit tricky 🙂

 

Thanks.

 

BR,

Blueeye

Hi @JorgeB,

 

the Server is now working without any issues for about 7 days. I use the regular shutdown function in combination with a User Script to enable the WOL function everytime the array starts and it works without any issues.

 

So my assumption would be that the issue is defenitely caused by the sleep function. Maybe it would be a good idea to note that the use of the sleep function could lead to a "Device disabled" issue potentially and to note that within the user guide. For energy saving, the automatic user script WOL enablement in combination with a mobile phone WOL app works perfectly, as far as I can tell.

 

Thanks for your support.

 

BR,

Blueeye

To conclude this topic.

 

- The server is now working without any issues for more than 6 months.

- I've added a User Script which is executed after every array startup:

• #!/bin/bash
• ethtool -s eth0 wol g

- I'm using the "Wake on Lan" app (Github)

 

Hope this might help somebody else

 

Best regards,

Blueeye

On 9/24/2024 at 3:10 PM, Blueeye said:

To conclude this topic.

 

- The server is now working without any issues for more than 6 months.

- I've added a User Script which is executed after every array startup:

• #!/bin/bash
• ethtool -s eth0 wol g

- I'm using the "Wake on Lan" app (Github)

 

Hope this might help somebody else

 

Best regards,

Blueeye

Hi I am having this same issue, if I put my unraid server to sleep and wake it up anyone one if my two 18 TB drives can go into disabled stated and I have to rebuild them. They are all new drives and both are 18 TB TOSHIBA drives. I also have a 8TB WD drive which dosesnt seem to have that issue as of yet.

Yup. Something is up with S3 sleep and Toshiba drives. I got the 16TB MG08 version and after the first sleep the drive is disabled. So that's fun.

Hey, I’m running into the same headaches with S3 sleep on Unraid, so I figured I’d share my setup and ask for advice.

• Main server with a big array + HBA → ~95 W idle

• Base system alone (CPU/RAM/fans, no HBA/array) → ~25 W idle

• So ~70 W are literally wasted 24/7 just to keep the array/HBA alive

• Electricity here is ~0.38 €/kWh → that’s expensive over a year

• So, I've built a low-power N100 box at ~12 W idle to host all Dockers/VMs and be the “master”

• Idea: keep the array sleeping and only wake it with WOL + autofs/NFS when files are needed

The problem: one wake ended up with a disabled/emulated disk and a full rebuild. That scared the hell out of me, and honestly I don’t trust S3 sleep anymore with this setup.

So I’m thinking: instead of sleep, maybe just fully shutdown the array server when idle and WOL it when needed. Downside: boot time ~1–2 minutes, which is annoying. But this box does nothing except serve the array (no Dockers, no VMs). But the idea of waiting 2 minutes before I can start a movie or listen to a music album ain't nice...

Question: is there a way to make Unraid boot in a really “lightweight” mode just for the array? Like, disable every unnecessary service/plugin so the boot + array mount is as fast as possible? Has anyone here tuned Unraid this way?

Or, is anyone here actually happy and safely using S3 using a great pre-sleep script ?

9 minutes ago, meaning said:

Hey, I’m running into the same headaches with S3 sleep on Unraid, so I figured I’d share my setup and ask for advice.

• Main server with a big array + HBA → ~95 W idle

• Base system alone (CPU/RAM/fans, no HBA/array) → ~25 W idle

• So ~70 W are literally wasted 24/7 just to keep the array/HBA alive

• Electricity here is ~0.38 €/kWh → that’s expensive over a year

• So, I've built a low-power N100 box at ~12 W idle to host all Dockers/VMs and be the “master”

• Idea: keep the array sleeping and only wake it with WOL + autofs/NFS when files are needed

The problem: one wake ended up with a disabled/emulated disk and a full rebuild. That scared the hell out of me, and honestly I don’t trust S3 sleep anymore with this setup.

So I’m thinking: instead of sleep, maybe just fully shutdown the array server when idle and WOL it when needed. Downside: boot time ~1–2 minutes, which is annoying. But this box does nothing except serve the array (no Dockers, no VMs). But the idea of waiting 2 minutes before I can start a movie or listen to a music album ain't nice...

Question: is there a way to make Unraid boot in a really “lightweight” mode just for the array? Like, disable every unnecessary service/plugin so the boot + array mount is as fast as possible? Has anyone here tuned Unraid this way?

Or, is anyone here actually happy and safely using S3 using a great pre-sleep script ?

Hi,

I've described my solution above. Full Shutdown plus WOL Script. S3 is not working. Haven't experienced any issues with it so far, and yes, boot time needs to be accepted.

Same problem here. Iam also using Thoshiba drives and the Dynamix S3 Sleep.

After rebuilding i will try Blueeyes suggestion. Thanks for sharing that.