Zonediver

You can install the user scripts plugin and execute this command in a script: hdparm -y $(ls /dev/sd*|grep '[a-z]$') >/dev/null 2>&1 Set the cron to lets say 15min and after this timeperiod the script will send all HDDs to standby.

Guys, I found the solution to this problem... Long story short: Its a "logical" problem. Description: The hard disks have two operating states: "active/idle" and "standby". For a successful sleep, the hard drives must be in standby. But when the server is taken out of sleep, all disks have the state "active/idle". This mode prevents the server from going to sleep next time (The "wait until array inactive" setting must be enabled in the sleep plugin). The server will never go back to sleep. The sleep plugin has a setting to implement custom commands after wakup. I got this custom Command from bonienl to set all HDDs to "standby": hdparm -y $(ls /dev/sd*|grep '[a-z]$') >/dev/null 2>&1 This setting seems to interfere the initialization process - maybe the SAS 9207 is not fast enough or the command is executed too soon. And that's the reason for the errors in the logfile. Solution: I removed this command from the sleep plugin custom command setting and execute it now every 15min over an other plugin "user scripts" and a cron setting. The controller now has enough time to correctly initialize the hard drives after a wakup and the errors are gone - and done 😉 Note: This custom command does not affect running hard disks!

Strange - usually that should not be a problem. Check the two LEDs on the network card when the server is turned off. The amber LED should blink constantly if everything is configured correctly. If the LED is OFF then there is something wrong with your config. What kind of NIC do you use? Intel or something else? Recommended is Intel. And set the BIOS to "wake from PCIe" - otherwise the WOL will not work. Regarding Android: That's just an alternative. The prerequisite is that the WOL config works properly. In my case i use Android to wakup the server over WOW without loging into my router. I do this over a broadcast but that is complicated to explain and assumes that the router is configured accordingly. Example of a broadcast over a *.bat file (from Windows) - in this case over the tool wolcmd: wolcmd FFFFFFFFFFFF 10.10.10.10 255.255.255.255 44444 The Fs are the MAC of your unraid server-nic the 10s are your "external" IP on the router - for this i recommend a dynamic DNS adress The 255s are the broadcast adress and the 4s are the port where the broadcast comes into the router Next you need to config your router to take the broadcast on port 44444 and sent it on Port 9 to the IP of your unraid-server. But beware: The router MUST support this forward - if not, then its not working. Some routers dont support this "trick". In my case the IPFire (router) needs a discrete Firewall-rule.

You want to WOL from where? Inside or outside your LAN? If its outside then its WOW. You can do this over Android as well but beware: Your Router must support this (over a broadcast). And dont use Port 7 or 9 - these ports will not be routed.

Just a short question: Is the S3-Sleep Plugin still under support? The last update was on 4. Feb 2018 - a long time... 😉

Of course, I am aware of that and perfectly clear. If this error is not recoverable, I will live with it. The sleep-function is essential for me - a 24/7 running server isn't an option...

I found a test for the Enermax 700W powersupply (in german) and it says: OCP: 3,3V ... 30A 5V ... 46A 12V1 ... 40A 12V2 ... 41A 12V3 ... 38A Voltage from 5% to 110% Load: 12,17V - 11,99V This should be ok for a short phase (powerup/spinup). I would exclude the power supply - but you never know ... 😉

I dont think its a problem - measured max. power input (during boot) is 220W for 2sec (whole Server) - so it cant be that the spinup of "all" disks will exceed the max. powerrange auf 696W on the 12V-rails... The disks are grouped into 4 blocks (powercables) at 4 disks each, the last block has only 3 disk. The 13 WD-RED's are rated with 1,75A/12V max. so we have a max. of ~ 24A on the 12V-rails (288W) or 6A on each 12V-output-connector of the PSU. This is working since 2010 - why should it be a problem now? I swapped only the both Adaptecs against one LSI-controller - powerconsumption is the same (~9,5W). Biggest problem: Find a PSU with 16 SATA-Powerconnectors... 😉

Yes - The error appears exactly once after waking up on all 8 connected disk. The server works otherwise perfectly. But I'm not sure if I should ignore that...

I have already considered that - unfortunately I have no spare power supply at hand to test it. The built-in power supply unfortunately has more than "one" 12V rail - so it could be that the power supply is to blame...

I have an addition to the errors in the log here - maybe that makes things a bit more transparent. Could this be a cable problem? Cables are brand new... Sep 21 20:22:07 unraid kernel: sd 1:0:0:0: Power-on or device reset occurred Sep 21 20:22:09 unraid kernel: sd 1:0:0:0: [sdb] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Sep 21 20:22:09 unraid kernel: sd 1:0:0:0: [sdb] tag#1 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00 Sep 21 20:22:09 unraid kernel: print_req_error: I/O error, dev sdb, sector 7814036992 Sep 21 20:22:09 unraid kernel: sd 1:0:1:0: Power-on or device reset occurred Sep 21 20:22:11 unraid kernel: sd 1:0:1:0: [sdc] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Sep 21 20:22:11 unraid kernel: sd 1:0:1:0: [sdc] tag#1 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00 Sep 21 20:22:11 unraid kernel: print_req_error: I/O error, dev sdc, sector 7814036992 Sep 21 20:22:11 unraid kernel: sd 1:0:2:0: Power-on or device reset occurred Sep 21 20:22:13 unraid kernel: sd 1:0:2:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Sep 21 20:22:13 unraid kernel: sd 1:0:2:0: [sdd] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00 Sep 21 20:22:13 unraid kernel: print_req_error: I/O error, dev sdd, sector 7814036992 Sep 21 20:22:13 unraid kernel: sd 1:0:3:0: Power-on or device reset occurred Sep 21 20:22:17 unraid kernel: sd 1:0:3:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Sep 21 20:22:17 unraid kernel: sd 1:0:3:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a3 00 00 00 00 08 00 00 Sep 21 20:22:17 unraid kernel: print_req_error: I/O error, dev sde, sector 5860532992 Sep 21 20:22:17 unraid kernel: sd 1:0:4:0: Power-on or device reset occurred Sep 21 20:22:20 unraid kernel: sd 1:0:4:0: [sdf] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Sep 21 20:22:20 unraid kernel: sd 1:0:4:0: [sdf] tag#1 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00 Sep 21 20:22:20 unraid kernel: print_req_error: I/O error, dev sdf, sector 7814036992 Sep 21 20:22:20 unraid kernel: sd 1:0:5:0: Power-on or device reset occurred Sep 21 20:22:22 unraid kernel: sd 1:0:5:0: [sdg] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Sep 21 20:22:22 unraid kernel: sd 1:0:5:0: [sdg] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00 Sep 21 20:22:22 unraid kernel: print_req_error: I/O error, dev sdg, sector 7814036992 Sep 21 20:22:22 unraid kernel: sd 1:0:6:0: Power-on or device reset occurred Sep 21 20:22:26 unraid kernel: sd 1:0:6:0: [sdh] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Sep 21 20:22:26 unraid kernel: sd 1:0:6:0: [sdh] tag#1 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a3 00 00 00 00 08 00 00 Sep 21 20:22:26 unraid kernel: print_req_error: I/O error, dev sdh, sector 5860532992 Sep 21 20:22:26 unraid kernel: sd 1:0:7:0: Power-on or device reset occurred Sep 21 20:22:32 unraid kernel: sd 1:0:7:0: [sdi] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 Sep 21 20:22:32 unraid kernel: sd 1:0:7:0: [sdi] tag#1 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a3 00 00 00 00 08 00 00 Sep 21 20:22:32 unraid kernel: print_req_error: I/O error, dev sdi, sector 5860532992

Thanks but this isn't an option 😉 As i mentioned, all is working fine - just the error in the log... i think i will ignore it...

...just a "little" bump to this... 95 views and no hint? At least one from an expert? 😉

Changed my both Adaptec 1430SA to a new LSI card with new cables and now i have errors in the log: Sep 15 10:44:57 unraid kernel: print_req_error: I/O error, dev sdb, sector 7814036992 Sep 15 10:45:00 unraid kernel: print_req_error: I/O error, dev sdc, sector 7814036992 Sep 15 10:45:02 unraid kernel: print_req_error: I/O error, dev sdd, sector 7814036992 Sep 15 10:45:07 unraid kernel: print_req_error: I/O error, dev sde, sector 5860532992 Sep 15 10:45:10 unraid kernel: print_req_error: I/O error, dev sdf, sector 7814036992 Sep 15 10:45:13 unraid kernel: print_req_error: I/O error, dev sdg, sector 7814036992 Sep 15 10:45:18 unraid kernel: print_req_error: I/O error, dev sdh, sector 5860532992 Sep 15 10:45:23 unraid kernel: print_req_error: I/O error, dev sdi, sector 5860532992 All eight drives on the controller are affected but the system is working normal. The errors only occur when I get the system out of sleep. I have read there is something wrong with IDE/AHCI and/or sleep. The question is now how to fix this or can this errors be ignored? Any advice will be welcome. Thanks for your help

Again: You need a HBA (HostBusAdapter) and "not" a RAID-Controller. All Controllers with a "0" in the lable are HBAs (IT-Mode) - see my signature - i use a LSI SAS 9207-8i (HBA, not RAID) See also my post above "Info about LSI-Controllers" 😉

Not without flashing to IT-Mode - the 9211-8i is a "RAID-Controller" - you need a HBA > flashing to IT-Mode by yourself at your own risk (i hope, this works) 😉.

Info about LSI-Controllers: All types with a "1" in the label (9211-8i, 9217-8i) are RAID-Controllers and must be flashed to IT-Mode.

Hi Frank, thanks for this info. Background why i was asking: I want do change my both very old Adaptec's (from 2008/2011) to only one controller. I did some research to find out if there could be problems. In the course of this, I found some reviews that described an extremely slow boot process, but it was not mentioned if that concerns the IT-mode. But it seems, there is all ok with this controllertype and i can use it without risks. Thanks again for your help

Hi trott and thanks for this info - 45sec is ok - so i dont know why some people told about 3-5min... Regarding the wakeup of the HDDs: What does this mean exactly? Is the sleeping disk not spin up or is it only "slow" so that the syslog get an entry? Can you provide the Google-Link to this "problem"? Thanks

To Point 1): I've probably put it that way badly. I've read that the controller takes up to 5 minutes to detect all attached drives, which significantly slows down the boot process. I wanted to know if anyone could confirm that?

Hi Guys, I have two questions about the LSI SAS 9207-8i: 1) I read that the controller takes up to 5 minutes to boot. A very long time... Can anybody confirm this? 2) Is the controller compatible with the sleep function of unraid? Thats very important for me because the server is not always needed and has to go to sleep for saving Money (and Energy). Thanks for your help

Its a problem with the RAM (maybe). My server did a boot-loop few days ago and i found out, that 1 of the 4 RAMs was broken. So check your RAM "one by one" and see if the server boots properly. Ah - too late - solved

Same here - Tautulli and Plex want an Update, but there isn't one... both from linuxserver 🤨

Hi folks, i am looking for a new solution for my unraid and like to know if someone knows, whether this Adaptec HBA is supported by unraid. The older Version HBA 1000-8i is compatible but very expensive in the meanwhile. If someone has some infos, please let me know - thanks 😉

Upgraded from 6.7.0 to 6.7.2 - looks good so far...