April 1, 20215 yr Hello, I woke up this morning to some errors from my unRAID server. A parity check had begun this morning (I run it monthly on the first of every month), but had failed a couple hours in. Now I see the message "Last check incomplete on Thu 01 Apr 2021 02:15:49 AM MST (today), finding 386 errors." when on the Main tab. Disk 2 has a red x instead of a green dot and says "Device is Disabled, Contents Emulated". This worried me, but I can't see anything wrong in the SMART data. Unfortunately, my next step was to reboot the server in order to see if the drive would come back to the array; I didn't think to grab the diagnostic log before doing so. Once the server came back up I was greeted with the same message about the disc being Disabled and its contents emulated. Any idea what could have caused this and how I can recover? Maybe a bad SATA cable? The drive in question has been in place for nearly 3 years at this point. I've attached the diagnostics log from after I rebooted. Thanks! tower-diagnostics-20210401-1106.zip Edited April 1, 20215 yr by sazrocks
April 1, 20215 yr Author Additionally, here is a screenshot of the archived notifications that show the timeline of what happened:
April 2, 20215 yr 8 hours ago, sazrocks said: I've attached the diagnostics log from after I rebooted. For that reason it isn't possible to say why the disk was disabled but bad connections are the most common cause. However, the disk seems ok from its SMART report, if rather too hot. I'd replace the SATA cable, check the power cable and then rebuild onto the same disk. With the array stopped, unassign Disk 2, start the array, stop the array, reassign Disk 2 and let it rebuild. And give some thought to improving the cooling.
April 2, 20215 yr Author 3 hours ago, John_M said: For that reason it isn't possible to say why the disk was disabled but bad connections are the most common cause. However, the disk seems ok from its SMART report, if rather too hot. I'd replace the SATA cable, check the power cable and then rebuild onto the same disk. With the array stopped, unassign Disk 2, start the array, stop the array, reassign Disk 2 and let it rebuild. And give some thought to improving the cooling. Thanks, yeah that was my thought, probably a bad connection somewhere since the smart report was clean. I've ordered a new set of sata cables, hopefully that fixes the issue. As for the logging, perhaps I should finally setup a proper external logging server. Thanks for your help!
Archived
This topic is now archived and is closed to further replies.