Pumped

Thanks @Squid and @trurl, I ended up rebuilding the data drive. It was either that or the parity and I think I preferred the idea of rebuilding the data. Cheers

Hi all, I ran into an issue with a disk today. It would not mount and found the drive being emulated. After some troubleshooting I found the issue was not the drive itself but the SATA port being used. After switching ports the drive appeared but did not mount in it's usual place. The device is showing up in unassigned devices, where I am able to mount it and can see the data. Edit: Disk 6 has an error saying "Device is missing. Contents emulated." The unassigned device mentioned above is the exact device that was working in the array yesterday. If I try and assign the device to Disk 6 (where it was previously) it is being treated as a new device. Is there a way to assign the device without triggering a rebuild of the parity and the device? tower-diagnostics-20240228-1019.zip

The emulated disk mounted so I assigned the same disk and it is rebuilding as we speak. Thanks again @johnnie.black. You've saved me from the wrath of my wife 😂🤣

Ok, good news. Rebuild completed overnight and was sucessful. Everything is green. I ran xfs_repair -v /dev/md2 -L on disk2 and the disk mounted 🙌 I can also see all the data correctly on disk 2 so it looks like it worked. Running the same filesystem check on disk 4 did not yield any changes and I am still seeing the "Unmountable: Unsupported partition layout" tower-diagnostics-20190401-1329.zip

I had the data recovery place give me a copy of the available data on a secondary drive so I have already been able to retrieve the disk4 data. Hoping the clone will help repair disk2. Waiting patiently for the rebuild (~20 hours remaining). Either way, very much appreciate your help @johnnie.black. You're a legend.

Damn. That doesn't sound good. Attached diags. tower-diagnostics-20190401-0335.zip

Disk 4 is showing "Unmountable: Unsupported partition layout" Is this an issue?

Ok, Disk 2 and 4 are "Unmountable" but a data rebuild and parity sync is running.

Ok got the drives back today. I have done the disk assignments and double checked them. I see this message near my parity drive 'All existing data on this device will be OVERWRITTEN when array is Started' And Starting the array without "parity is already valid" presents the warning "Parity disk(s) content will be overwritten" Is this correct? If I am to recover the content of disk 2 don't I require the parity to remain in tact? I haven't proceeded past this dialog yet.

Sorry. Yes, disk 2 is the one that will be missing. Thanks for your help. I will post results back here when I get the drive returned.

It is a data drive. I am running 6.6.7. Attached a screenshot of the drives. Disk 3 is the drive that can't be fixed, and disk 4 is the one they are attempting to clone.

Hey guys, I had the unthinkable happen recently and had 2 drives fail due to an electrical surge. Unfortunately I only have a single parity drive (+4 storage drives). I have sent the drives to a data recovery centre and they are able to recover one of the drives, the other drive is unfortunately not able to be recovered. They have said that it is possible to do a block level clone of the "good" drive onto a new drive. Would it be possible to use this cloned drive back in the array to emulate/rebuild the drive that they cannot fix? Essentially I would need to update the unraid config to think that the new drive is the old drive. If this is possible how can I do it? Thanks.