Disk 5 disabled...read and write errors in syslog

[Paulitix]

Hi,

 

Trying to help my pops troubleshoot his system.  Is it time to swap out disk5 (sdj)?

 

aramis-diagnostics-20200315-1353.zip

[trurl]

That disk has disconnected. Check connections and post new diagnostics.

[Paulitix]

New diagnostics as requested.  

aramis-diagnostics-20200319-1449.zip

[Dissones4U]

@Paulitix It looks like all of your disks' file systems are REISERFS if this is the case it has been recommend for years that anyone still using it convert to XFS.

• From: aramis-diagnostics-20200319-1449.zip ==> SMART ==> WDC_WD30EZRX-00DC0B0_WD-WMC1T0563613-20200319-1449 disk5 (sdj) - DISK_DSBL.txt

SMART overall-health self-assessment test result: PASSED

 1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    9 <== this doesn't necessarily mean anything unless it goes up

 5 Reallocated_Sector_Ct   PO--CK   200   200   140    -    0 <== Good
 7 Seek_Error_Rate         -OSR-K   200   200   000    -    0 <== Good

 

I think the drive is good, may have been the cable, consider replacing it.

 

When a disk is disabled

• From the unraid wiki

Quote

Once a disk is disabled it's contents (disk5 in your case) must be considered invalid (because there have been uncompleted writes). All further read requests to that disk will be serviced by reading Parity and all the other Data disks in order to reconstruct the requested data on-the-fly. All further write requests result in first reading all the other Data disks, and then updating the Parity disk. Normally, you would replace the hard drive of a disabled disk.

Disk replacement is considered best practice, this allows you to remove D5 and read it in another machine should data recovery become necessary. However, you can try to re-enable a disabled disk if you're sure that parity is good and you think the disk is okay:

1. Stop the array.
2. Power down the unit.
3. Physically remove the failed disk, leaving the slot empty.
4. Start the array with the disk unassigned to get unRaid to "forget" it
5. Stop the array.
6. Power down the unit.
7. Reassign your failed disk.
8. Power up the unit.
9. Start the array.

When you start the array in step 5, the system will notice the failed disk's slot is empty, and it will clear the identification data for that slot. Thus when you start the array in step 10, the system will treat the disk simply as a new disk.

 

If you chose to use the disabled disk rather than replace it, please make sure you understand this process before you proceed. If you do it incorrectly you will end up updating parity with the bad data from the disabled disk.

Edited March 20, 2020 by Dissones4U
tweaked steps

[trurl]

Not really necessary to physically remove the disk. You just have to start the array with the disk unassigned to get it to "forget" it.

 

So

1. Stop the array.
2. Unassign disabled disk.
3. Start the array with the disk unassigned.
4. Stop the array.
5. Reassign the disk.
6. Start the array to begin rebuild.