February 15, 20197 yr A new server I put together is filling up it's syslog really quickly (2days). The same error is repeating quite a bit and I can't find anything using google. Hoping the great community here can give some insight. Feb 13 05:21:23 LakeHouse01 kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5 Feb 13 05:21:23 LakeHouse01 kernel: mdcmd (299316): spindown 29 Feb 13 05:21:23 LakeHouse01 kernel: md: do_drive_cmd: disk29: ATA_OP e0 ioctl error: -5 Feb 13 05:21:24 LakeHouse01 kernel: mdcmd (299317): spindown 0 Feb 13 05:21:24 LakeHouse01 emhttpd: error: mdcmd, 2639: Input/output error (5): write lakehouse01-diagnostics-20190214-1908.zip
February 15, 20197 yr Disable spindowns in Settings - Disk Settings. SAS drives can't be spun down and are generating the errors you're seeing.
February 24, 20206 yr On 2/14/2019 at 6:50 PM, Squid said: Disable spindowns in Settings - Disk Settings. SAS drives can't be spun down and are generating the errors you're seeing. hot damn fixed that error, the price you pay for mixing sas and sata drives......sas drive was cheap. is there a way to only have the sas drive spin and the other not?
February 25, 20206 yr Click on the disk from Main and change the spin down delay to neverSweet mother of Geezus,Fuck I love this forumThanks Sent from my iPhone using Tapatalk
Archived
This topic is now archived and is closed to further replies.