Hi all, hoping you can help. Im running unraid 6.5 - upgraded from a lower version (6.2 I think?!) but have been getting notifications from the CA common problems, and can also see on the dashboard, that my log files keep filling up. I fairly recently added some donated drives - so just wondering if that is the issue, and what i need to do about it. Are the drives too broken to use, or is it the SAS card going wrong? I've tried reading into it, but a bit unsure of what to do next. 

I've attached diagnostic files as well to help out, but tried to dig out what i think are issues below:

 

The setup is a SC-4320S case with a few Dell perc cards (H310) connected to the case backplane (with SAS 36p/8087 cables), and then a mix of SATA and SAS drives (plus 2 SSD cache drives connected directly to the motherboard). The motherboard is an old gaming type, which I imagine doesnt matter too much with these errors! (I can post specs if needed!). Parity is on one of the SATA drives (6TB ironwolf)

 

I think the errors relate to the SAS drives I was given. They seem to read and write fine, but smart did show some corrections going on.

One of the drives looks like this, the others are similar:
 

Error counter log:
           Errors Corrected by           Total   Correction     Gigabytes    Total
               ECC          rereads/    errors   algorithm      processed    uncorrected
           fast | delayed   rewrites  corrected  invocations   [10^9 bytes]  errors
read:          0        0         0  1625825723          0     260819.243           0
write:         0        0         0         0          0       3968.940           0

 

I think the main errors in the logs are of the format (random snippet taken - this repeats through the logs)

Apr 24 06:41:34 pong emhttpd: error: mdcmd, 2639: Input/output error (5): write
Apr 24 06:41:34 pong kernel: md: do_drive_cmd: disk6: ATA_OP e0 ioctl error: -5
Apr 24 06:41:34 pong kernel: mdcmd (1168462): spindown 7
Apr 24 06:41:34 pong kernel: mdcmd (1168463): spindown 8
Apr 24 06:41:34 pong emhttpd: error: mdcmd, 2639: Input/output error (5): write
Apr 24 06:41:34 pong kernel: md: do_drive_cmd: disk8: ATA_OP e0 ioctl error: -5
Apr 24 06:41:35 pong emhttpd: error: mdcmd, 2639: Input/output error (5): write
Apr 24 06:41:35 pong kernel: mdcmd (1168464): spindown 5
Apr 24 06:41:35 pong kernel: md: do_drive_cmd: disk5: ATA_OP e0 ioctl error: -5
Apr 24 06:41:35 pong kernel: mdcmd (1168465): spindown 6

 

 

Hopefully someone can work out what is going wrong  

Thanks!

pong-diagnostics-20180424-1308.zip

You SAS disks don't spindown, it's a known issue with current unRAID.

 

You should disable it for those disks for now, so at least you won't fill the syslog.

 

 

Edited April 24, 20188 yr by johnnie.black

4 minutes ago, johnnie.black said:

You SAS disks don't spindown, it's a known issue with current unRAID.

 

You should disable it for those disks for now, so at least you won't fill the syslog.

 

 

 

That's great, thanks! :-) 

Simple solution that way too I guess!

 

I'll give it a try - and watch my logs over the next few days.