October 1, 201213 yr During the monthly parity check, I got a message saying disk 16 disabled or invalid. Did a clean shutdown, reseated it. Rebooted and now it's showing up as unformatted, but disk 9 is also showing up as unformatted? Running 4.7 syslog attached I'll add that the array appears to still be running fine. Streaming via NFS from a share that spans all drives is working from healthy drives. I can't remember what was on disk 9 to test it. syslog-2012-10-01.txt
October 2, 201213 yr why don't you enable disk view and browse the disk, most likely nothign will be there.
October 2, 201213 yr Author OK, a second reboot has disk9 back to normal (I think?). It seems disk9 showed as unformatted for reasons as described here: http://lime-technology.com/wiki/index.php/FAQ#Why_is_a_disk_showing_as_Unformatted.3F syslog attached OK but back to disk16, still showing redball. What's next? Run a smart report, I guess? It's strange - it's a re-purposed one-year-old disk that was pre-cleared and added last to my array about six months ago. It's never been written to. syslog-2012-10-01_1.txt
October 2, 201213 yr Author OK so here's the long smart report, can somebody please have a look? http://pastebin.com/PgACf3Gb
October 3, 201213 yr Hello, Saw 1461 current pending sectors. That is not a good sign. Might be time for a RMA. Have a good one, Jim S.
October 3, 201213 yr Author So I've put drive in a different slot in the 5x3 cage, different cable, and it's currently rebuilding. I'm really confused as to the state of this drive. It failed during a monthly parity check and I'm wondering if it was due to overheating? It was next to a hotter 7,200 but that one never goes above 40C. Weird
Archived
This topic is now archived and is closed to further replies.