xtrap225 Posted April 16, 2019 Share Posted April 16, 2019 I wonder if anyone has any experience with this. so when i have spin down disabled i do not get these errors. i am running a Lenovo desktop, connected to NetApp DS4246 72TB 24x 3TB 7.2K SATA X308A-R5 with a Dell LSI SAS 9202-16e 6Gb/s SAS Host Bus Adapter. I am hoping to be able to figure out how to spin down drives without the error. (ill have to find my serial adapter and try to connect to the storage shelf but i also want to figure out how to properly send shutdown command to the shel when the ups shuts down the server in case of power outage). i only bring that up because i am wondering if they two could be solved with a similar fix. that is connecting usb to serial adapter to the server and figuring out how to tell unraid (or slackware) to issue commands to the netapp. Commands like spinning down and up drives, or shutting down or turning on the whole shelf. desktop details Model: Custom M/B: LENOVO - SHARKBAY CPU: Intel® Core™ i5-4570 CPU @ 3.20GHz HVM: Enabled IOMMU: Enabled Cache: 1024 kB, 256 kB, 6144 kB Memory: 32 GB (max. installable capacity 32 GB) Network: eth0: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.18.20-unRAID x86_64 OpenSSL: 1.1.1a Uptime: 0 days, 04:34:28 system log errors ErrorWarningSystemArrayLogin Apr 15 21:45:49 WORK-PC kernel: mdcmd (49): spindown 9 Apr 15 21:45:50 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:50 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:51 WORK-PC kernel: mdcmd (50): spindown 9 Apr 15 21:45:52 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:52 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:53 WORK-PC kernel: mdcmd (51): spindown 9 Apr 15 21:45:54 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:54 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:55 WORK-PC kernel: mdcmd (52): spindown 9 Apr 15 21:45:56 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:56 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:57 WORK-PC kernel: mdcmd (53): spindown 9 Apr 15 21:45:58 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:45:58 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:45:59 WORK-PC kernel: mdcmd (54): spindown 9 Apr 15 21:46:00 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:00 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:01 WORK-PC kernel: mdcmd (55): spindown 9 Apr 15 21:46:02 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:02 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:03 WORK-PC kernel: mdcmd (56): spindown 9 Apr 15 21:46:04 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:04 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:05 WORK-PC kernel: mdcmd (57): spindown 9 Apr 15 21:46:06 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:06 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:07 WORK-PC kernel: mdcmd (58): spindown 9 Apr 15 21:46:08 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:08 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:09 WORK-PC kernel: mdcmd (59): spindown 9 Apr 15 21:46:10 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:10 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:11 WORK-PC kernel: mdcmd (60): spindown 9 Apr 15 21:46:13 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:13 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:14 WORK-PC kernel: mdcmd (61): spindown 9 Apr 15 21:46:15 WORK-PC emhttpd: error: mdcmd, 2639: Input/output error (5): write Apr 15 21:46:15 WORK-PC kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5 Apr 15 21:46:16 WORK-PC kernel: mdcmd (62): spindown 9 Quote Link to comment
JorgeB Posted April 16, 2019 Share Posted April 16, 2019 Unraid won't spin down SAS devices (or SATA devices that look like SAS devices because of the enclosure) Quote Link to comment
xtrap225 Posted April 16, 2019 Author Share Posted April 16, 2019 (edited) fair enough, thank you for the response. does anyone have any experience talking to the iom6 controller from a non-netapp server. i believe i would telnet into it? no that can't be right, just connect on a serial terminal, maybe? Edited April 16, 2019 by xtrap225 Quote Link to comment
mistah Posted January 22, 2020 Share Posted January 22, 2020 OP: Did it fix your issue? I've just found this thread because of a similar problem. /var/log was full, and had this error over and over again in my log file. Quote Link to comment
xtrap225 Posted January 23, 2020 Author Share Posted January 23, 2020 (edited) unfortunately no, i have it set it disabled. i did find my serial to usb cable but i haven't had time to see if it works on unraid to telnet into iom6 Edited January 23, 2020 by xtrap225 Quote Link to comment
JarDo Posted March 8, 2020 Share Posted March 8, 2020 (edited) I am on v6.8.3. How do I spin down unassigned devices. I seem to remember I could click on the green orb and that would do it, but the orbs on my unassigned devices are already grey but my unassigned drives are showing a temp. I have to assume if the drives are showing a temp that they are not spun down. Edited March 8, 2020 by JarDo Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.