I'm running Unraid 6.12.10

 

I had 2 drive failed recently, but also have 2 parity drives

1. disk4 dropped off the array, but came back on it's own, but when array is started, it showed that contents are emulated from parity. I see no SMART errors.
2. disk 5 died, still waiting for replacement drive to arrive

 

In order to fix issue number 1, I tried to retrigger a rebuild from parity, but did something stupid. It was not automatically triggering a rebuild from parity when starting the array, and I saw that disk4 was showing unmountable and it showed a format button. Being the genius that I am, I decided to format the drive, hoping that it would format, mount, then trigger rebuild from parity (I should have just googled how). Clearly I could not be any more wrong. After the format and realizing that parity rebuild did not trigger, I stopped the array, unassigned disk4, started and stopped the array, then reassigned disk4, which then triggered parity rebuild. After the rebuild finished, I noticed that all data on disk4 and disk5 are gone. The data on disk4 was not too important for me, but I would like to recover data from disk5.

 

Now here are a few things that I noticed

1. After formatting disk4, for some reason disk5 is showing that data is wiped as well. Was this a result of me formatting disk4?
2. During the parity rebuild of disk4, I noticed some xfs errors being thrown in syslog for disk4 and disk5 which can be seen in the attached logs. After the rebuild, I unmounted, mounted in maintenance mode, then ran the xfs_repair -v /dev/mdXp1 command for all of the drives, but it did not bring back any of the lost data.

 

Any chance that the data on disk5 is still recoverable?

 

daniel-nas-diagnostics-20241202-2234.zip

Edited December 3, 20241 yr by cpxazn

unriad is version 6.12.14 I do recommend upgrading to the most stable release. did you already power off the dive and confirm disk power and cables.

it appears that disk 5 per your picture may have bitten the dust so we have to look at parity if setup corectly for its data. But I don't think you have a backup/waay to recover the disk data... and it may be lost. A more expiernece user may need to assit you hear.

 

Thanks for your input. I'm preparing for the worst, but just hanging onto a sliver of hope that disk5 is recoverable since I'm still not sure how that data got wiped.

 

I have already replugged the cables for the drives and all drives are showing properly in the array. Parity is setup correctly so shouldn't be an issue there.

 

Edited December 3, 20241 yr by cpxazn

When you formatted disk4, disk5 was also formatted, because it was also unmountable:

 

Dec  1 19:00:46 daniel-nas emhttpd: shcmd (174): mkfs.xfs -m crc=1,finobt=1 -f /dev/md5p1

 

That disk would show in the list of disks that were going to be formatted, along with the warning that formatting is never used to recover data.

 

Is the old disk5 completely dead?

4 hours ago, JorgeB said:

When you formatted disk4, disk5 was also formatted, because it was also unmountable:

 

Dec  1 19:00:46 daniel-nas emhttpd: shcmd (174): mkfs.xfs -m crc=1,finobt=1 -f /dev/md5p1

 

That disk would show in the list of disks that were going to be formatted, along with the warning that formatting is never used to recover data.

 

Is the old disk5 completely dead?

Lesson learned. Thanks for checking, I had already shipped disk5 back for RMA.

 

Maybe one improvement here would be to improve the message to say that this would wipe parity as well. I thought this would perform something like a preclear before mounting and rebuilding from parity.

Edited December 3, 20241 yr by cpxazn

Parity is not wiped, it's updated, and the warning already mentions that:

 

 

You may still be able to recover the data, if you rebuild the disk, and then run a file recovery app, like UFS explorer.

On 12/3/2024 at 9:46 AM, JorgeB said:

Parity is not wiped, it's updated, and the warning already mentions that:

 

 

You may still be able to recover the data, if you rebuild the disk, and then run a file recovery app, like UFS explorer.

Thanks, although it took a long time, I was able to recover at least 90% of the data.