I've upgraded the OS to 7.2.2 the other day. It warned me about 4 resierfs drives for future support.

I was trying to upgrade my file system from reiserfs to xfs. I was successful with 2 out of 4 drives. But on the 3rd I wasn't paying attention and while I stopped the array in phase 1 where I should have selected the drive to Empty, I skipped to selecting the new OS on the drive.

I realized what I did before I started the array, so I selected the device in the slot as None as if I was going to replace the drive and started the array. It said it was being Emulated. So I stopped the array selected the same drive and started it and then it stated it was rebuilding the drive and completed after about 13 hours. But I get the unmountable error on the drive. I stopped it and started it, but the same issue. It does still show the filesystem as XFS and not the original ReiserFS.

What steps can I do at this point to hopefully recover that drive/data? Could I unmount, emulate the drive, then change it back to reiserfs and rebuild again?

Please post the diagnostics

17 hours ago, JorgeB said:

Please post the diagnostics

Okay, after removing the drive from my array again, I noticed my Unassigned Devices plugin showed the filesystem as ReiserFS, which is was/is. So I set it to Read-Only and share the drive and mounted it outside of the array, and all my missing data is there in the drive share. I'm in the process of extracting the data to an external drive.

So now what are my options after I get all my data off the drive? The emulated drive didn't work after unassigning it as I think the array is still trying to access the drive as XFS. When I had the array stopped, I don't think it gave me the option to change it back to ReiserFS, as it was grayed out.

How can I remove that drive from the system entirely without parity trying to rebuild it, and then copy the data back into the array? If that would be a better route to go after getting the data backed up.

After recovering the data you can format the emulated disk, rebuild it, and then restore the data.

8 hours ago, JorgeB said:

After recovering the data you can format the emulated disk, rebuild it, and then restore the data.

Ok, to be clear, the array is started and the drive is being emulated but not accessible. I have the drive Unassigned Mounted and recovering the data.

Once the data is recovered, would the correct procedure be to unmount the drive, Format the unmountable drive, stop the array, assign it back to the disabled slot and then start the array? Would the array try to rebuild the missing drive? I just don't want to do it in the wrong order and have the array start the rebuild process again which won't work.

You can format the unmountable drive at any time, before or after assigning the disk back, and also before or after rebuilding, important part is to have the recovered data outside.

Once the rebuild is finished (and the drive formatted), restore the data.