So I rebooted the server yesterday and things were fine before and I thought after but when I woke up this morning, my parity drive was in the process of a read-check and had some weird numbers

Temp       Reads                           Writes       Errors

*

23,214,889,176,533

0

2558

 

i have no idea what's going on? THis is a fairly new drive, maybe 3 months old, 8TB, and I precleared it just fine.

 

I'm on the most recent beta btw

 

Dec 10 07:52:39 Tower emhttpd: req (6): cmdSpinup=parity&csrf_token=****************
Dec 10 07:52:39 Tower kernel: mdcmd (61): spinup 0
Dec 10 07:52:39 Tower kernel: md: do_drive_cmd: lock_bdev error: -2
Dec 10 07:57:48 Tower emhttpd: req (7): cmdSpindown=parity&csrf_token=****************
Dec 10 07:57:48 Tower emhttpd: error: mdcmd, 2631: No such file or directory (2): write

 

Edited December 10, 20178 yr by fgdjhakdftere
clarity

Most likely dropped offline, this can some times result in an absurd number of reads, diagnostics would show what happened.

so I rebooted and now it freaked about about parity being disabled so I removed it and re-added it to re-sync. I'll see what happens in about 24 hours.. 

Still having an issue. I resynced the parity drive and all was well until this morning where it I now have all the issues described in the first post again. Once again I'm resyncing the parity drive. Is this because it's spinning down and gets out of sync? Any ideas?

1 hour ago, ffhelllskjdje said:

Any ideas?

Post diagnostics

Did you at least check SMART for the parity disk before re-syncing? In doubt and like mentioned before post your diagnostics.

5 hours ago, johnnie.black said:

Did you at least check SMART for the parity disk before re-syncing? In doubt and like mentioned before post your diagnostics.

Yeah, smart was fine. I'll post diags

 

tower-diagnostics-20171213-1426.zip

Timeout error and since there are 16 CRC errors on the disk it's likely a bad SATA cable, replace and resync.

4 hours ago, johnnie.black said:

Timeout error and since there are 16 CRC errors on the disk it's likely a bad SATA cable, replace and resync.

Solid man! I was thinking the same thing, I'll replace and see how it goes!