June 9, 20179 yr I updated from latest stable release to 6.4.0 rc 2 last night. this morning I woke up and my 2nd parity drive is disabled due to read errors. The errors started when the mover kicked off. I know there were a couple of mover changes in this release so I am not sure if it is related or not. Attached are my diagnostics. Should I shut down the box and re-seat the drive? Anything else I should try? Thanks! debo-server-diagnostics-20170608-2018.zip
June 9, 20179 yr Devices are never disabled due to read errors, however there are plenty of write errors on your parity2 device. Very unlikely due to 'mover'.
June 9, 20179 yr Parity2 dropped offline so there's no SMART report, power down, check cables, then grab and post new diags.
Archived
This topic is now archived and is closed to further replies.