applejack

I've been out of town for 6 weeks for work and left my Unraid array running for the family to use, and came home to find one drive dead (disk12) and one drive (disk5) showing tens of thousands of "Reported uncorrect" errors in SMART. Right now I can still browse those drives and the few media files I tried seem to be okay, so parity is reconstructing on disk12. Any advice on how to minimize potential data loss? My first thought was that attempting a parity rebuild after replacing disk12 would be too taxing on disk5 (and might lead to errors anyways), so I was going to copy as many files as I can from those 2 drives off the array first, then replace the drives and redo parity, then copy them back. syslog.txt ST4000DM000-1F2168_W300859D-20220211-0904.txt

Thanks for this docker, dlandon, I've been using it since release. Any chance for an update to the 8.1.x branch? TIDAL is no longer working in 8.0.x (and I believe that Deezer Hi Fi also requires 8.1.x).

Forcing a parity rebuild didn't bring the data back, it basically just left with me with an empty disk. Given that I formatted the disk for another file system (Reiser to XFS), I pretty much gave up on any other data recovery efforts. The disk contained media files, not mission critical data, but I would have liked to have kept it if possible. Lesson learned, though I'm still not entirely sure of the reason why removing a disk from the array and reformatting it to a different file system wouldn't at least trigger the option to rebuild it's contents from parity, given unRAID is a system that supports multiple file systems and users do change those for various reasons.

No, never did a New Config. Should I have?

My assumption (a very incorrect one as it turns out) was that if I remove the disk from the array, format it outside the array with a new FS, and then add it back to the array, it would be no different than adding a new disk and I could rebuild the disk contents from parity. So those were the steps I did--stopped the array, unassigned the disk, formatted it to XFS, and then added it back to the array. I could be wrong, but I don't think you can format a disk through the GUI when it's still assigned and mounted in the array (same with the preclear plugin). When the parity came back as valid and the disk was marked "green", with all it's space being free and no option to rebuild parity, I knew I was likely in trouble and those disk contents were gone. So no, the disk contents are not emulated if I unassign the disk and start the array. The parity was obviously updated when I added it back as an empty disk with a new FS. I guess I don't see why formatting an existing disk outside the array with a different FS and then adding it back in would update parity automatically instead of asking for a parity rebuild as an option.

I'm pretty sure I'm out of luck on this, but just wanted to double check. My 15 disk array (v 6.6.7) is a mix of 4 & 8 TB disks, all on ReiserFS. As is not uncommon with ReiserFS, I've been having write delays and other hiccups when the disks are nearly full, which most currently are. So I've been wanting to switch to XFS (for that and all the other reasons listed in the user guide and forums), but was looking to avoid the rsync method with an empty drive. I typically do a monthly parity build, so I though I'd just shut down the array, remove a disk from the array, reformat it in XFS, start the array and do a parity rebuild on the newly formatted drive. Rinse and repeat over several months to convert all the disks over to XFS (or faster if I replaced any disks). Oops. Didn't realize that reformatting a disk outside the array and then adding it back in would update the parity and not give the option for a parity rebuild (still not really sure why that's the case, would seem to be obvious to me). So I'm pretty sure I've lost all data on the drive I formatted to XFS, but just checking to see if there was any way to go back to the previous parity and rebuild the disk.

I have three disks in a 15 disk array showing SMART prefail. I have replacement drives (though not pre-cleared yet), but wanted to gauge opinions on which order to replace them as to minimize chances of data loss. SMART reports for each drive are below. Thanks. Disk 2 / sdm ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 090 006 Pre-fail Always - 64612936 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 66 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 400 7 Seek_Error_Rate 0x000f 070 060 030 Pre-fail Always - 11248558 9 Power_On_Hours 0x0032 055 055 000 Old_age Always - 39539 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 66 183 Runtime_Bad_Block 0x0032 099 099 000 Old_age Always - 1 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 099 099 000 Old_age Always - 1 188 Command_Timeout 0x0032 100 097 000 Old_age Always - 3 3 3 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 067 056 045 Old_age Always - 33 (Min/Max 23/34) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 10 193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 475843 194 Temperature_Celsius 0x0022 033 044 000 Old_age Always - 33 (0 19 0 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 5436h+05m+33.849s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1411727509962 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 31791961878189 Disk 3 / sdm ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 119 096 006 Pre-fail Always - 211546592 3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 65 5 Reallocated_Sector_Ct 0x0033 097 097 010 Pre-fail Always - 3800 7 Seek_Error_Rate 0x000f 050 050 030 Pre-fail Always - 476753486599 9 Power_On_Hours 0x0032 057 057 000 Old_age Always - 38487 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 66 183 Runtime_Bad_Block 0x0032 099 099 000 Old_age Always - 1 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 1 1 1 189 High_Fly_Writes 0x003a 097 097 000 Old_age Always - 3 190 Airflow_Temperature_Cel 0x0022 069 057 045 Old_age Always - 31 (Min/Max 22/33) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 13 193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 447757 194 Temperature_Celsius 0x0022 031 043 000 Old_age Always - 31 (0 18 0 0 0) 197 Current_Pending_Sector 0x0012 099 099 000 Old_age Always - 176 198 Offline_Uncorrectable 0x0010 099 099 000 Old_age Offline - 176 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 5034h+41m+05.185s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 22770899496 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 139423370898 Disk 9 / sdg ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 135 135 054 Pre-fail Offline - 85 3 Spin_Up_Time 0x0007 136 136 024 Pre-fail Always - 420 (Average 420) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 103 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 61 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 133 133 020 Pre-fail Offline - 27 9 Power_On_Hours 0x0012 093 093 000 Old_age Always - 53222 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 103 192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 1633 193 Load_Cycle_Count 0x0012 099 099 000 Old_age Always - 1633 194 Temperature_Celsius 0x0002 187 187 000 Old_age Always - 32 (Min/Max 20/45) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 67 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0