Moved server to final location and booted it, now getting read errors on disk

[markc99]

I had my server on my desk while I was configuring it, today since everything seemed fine, moved it to my network closet and booted everything back up. Even though I used the shutdown command before moving it, it came up and said Unclean Shutdown Detected.

 

I started the array and it kicked off a parity check. The last one completed fine, without errors.

 

Now I'm getting read errors on a disk, and it disabled it. My gut tells me it's probably a loose connection to my SAS card. I was going to power it down again and reseat/check all the connections.

 

Is there a way to re-enable the drive?

tower-diagnostics-20220201-0923.zip

[markc99]

So, I powered everything off and sure enough, the drive with read errors was on SAS Cable 1, Port 2, which I feel like I had problems with before. I had a free Port on the other SAS cable, so I swapped it to that and booted everything up. Ran an SMART test on that drive and it passed.

 

Followed the instructions in another thread about unassigning the drive, starting the array and then stopping and reassigning the drive to kick off rebuild. That is running and I'll report back on my results.

Edited February 1, 2022 by markc99
Added SMART test to list of steps

[JorgeB]

21 minutes ago, markc99 said:

Is there a way to re-enable the drive?

You need to rebuild it, make sure the emulate disk is mounting and contents look correct before rebuilding on top of the old disk.

 

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

 

Other option is to do a new config and re-sync parity, just mentioning it since there's a chance parity is not 100% valid due to the unclean shutdown, but since no errors were found in the beginning of the check, and usually there are some there if there are any, it should be fine.