Hi guys,

 

I'm looking for a little help from you experienced unRAID people once again please.

 

I am setting up my unRAID server to go into sleep mode after disk spin down, and then Wake On Lan by sending a 'magic packet'. I have followed the Wiki guide to the letter, and have also read through the entire 24 pages of the main topic on this subject.

 

I can get the server to go into automatic sleep mode without a problem, timed after all disks have spun down. I can also send the server the magic packet by using the WOLcmd program via a batch file (I can even send it one wirelessly via my iPhone). The server starts to wake up, and all disks spin up, but then the 'wake' process seems to lock up, and all the hard drive activity lights (on the Icydock hotswap backpane caddys that I have in my server) on those drives connected to my Supermicro SASLP-MV8 controller just flash orange and green (green is for when a drive is powered, orange is when it is spinning).

 

I can't seem to get past this point. I have a monitor attached, but this does not recieve any further video signal from the server so it displays nothing, and the attached keyboard does not have any effect. The only thing I can do to sort it is a hard reboot.

 

I'm assuming this might be an issue with the reboot of the Supermicro card, but have no idea how to trouble shoot it.

 

I don't have a syslog to attach because I have to do a hard reboot (I am right in thinking that this clears out the syslog?). If I need to list any other system details to aid any advice, please let me know. unRAID version is 4.7beta (haven't upgraded it yet) and apro licence.

 

ANy ideas you might have would be greatly appreciated?

Anyone??

Have you tried the same sleep/wake without the SM card installed?

 

What sleep level have you been using? Lower states won't save as much power but can work around issues like those you describe. There might be a more graceful solution but it'd be nice to narrow things down a little.

I am using S3; my BIOS only has options for S1 and/or S3. I can try pulling the Supermicro card I suppose, though I was hoping to diagnose the problem without. I will have a go!

Definitely try S1. There may be issues with the SM card/driver in sleeping or waking. S1 will leave it powered (unless it says otherwise) and avoid a few power management pitfalls.

 

Ok, will give that a go too - do I need to edit the scripts at all to go into S1 sleep (my Linux knowledge is patchy at best)?

My own n*x knowledge is rusty or worse. Can you say System V?

 

Standby modes have been problematic since the first battery powered systems. Linux doesn't get as much attention as Windows, and in the best of cases Windows can die horribly if a poorly implemented driver gets involved. Some combinations of systems and add-ons just do not handle sleep modes.

 

I'd first check your BIOS to see if your system supports S1, set it. Then, sub S1 for S3 in the scripts. I haven't looked at them to see what's passed vs. being a passive tag/label, so hopefully someone who's played with it more will wander in.