New Config when I shouldn't have. Unmountable error on some drives.

[gundy]

Long story short, I did New Config and tried to get the order of my missing drives correct. The first time one of the 14tb drives had the “Unmountable: Unsupported or no file system” error. I did New Config three more times to see if maybe I had some of the 14tb drives in the wrong place and now I’m left with three drives that have that error. Is there any way to fix this while retaining my data?

 

Long story: I wanted to add two 1TB nvme drives as parity in raid 0 to replace my 500GD sata ssd. I first tried to add an sn850x. Unraid wouldn’t recognize it. I updated the BIOS, still wouldn’t recognize it. My mobo ended up not being able to read it because there a was some pin mismatch. Tried another drive. Had it as a main drive in another computer, didn’t format it and thought it would work fine. Here it was booting up into my other computer's desktop. Removed it from the boot sequence. Boot up Unraid, only half my drives are showing up, others say missing. After that I read something on the forums, which was wrong, I did a New Config. It later turned out my mobo didn’t like the nvme in the slot I had it in and that was causing my second LSI card to not even be recognized. So I removed the nvme drive and now it recognizes the other LSI and the other half of the drives now show up. I ended up rolling back to the previous BIOS version, too. So now since I did a New Config earlier, those drives are all unassigned. So I did a new config to try to match them up, and one of the 14tb drives got the unmountable error. I did it three more times but now three drives have that error. I’m wondering if this can be fixed. I know that all of the 8tb drives are in the correct place. I included a diagnostic. I did all of the new config commands after the last reboot so it should all be in the logs.

unraid-diagnostics-20230705-0108.zip

[JorgeB]

Click on those disks and change the fs from auto to xfs, then check filesystem on all 3.

[gundy]

That option is greyed out, unfortunately.

 

edit: stopped array and put in maintenance mode. Here's the check from disk 11..

edit: and 12 and 13

disk11.txt

disk12.txt disk13.txt

Edited July 5, 2023 by gundy

[JorgeB]

Run it again without -n or nothing will be done, and if it asks for -L use it.

[gundy]

Disk 11 asked me for -L, others didn't.

disk11.1.txt disk12.1.txt disk13.1.txt

[JorgeB]

They should be repaired now, start array in normal mode.

[gundy]

Looks like it's working. The drive I had to do -L looks like it lost it's data, but that's better than three drives with no data. Thanks!

 

edit: It started a parity check, other than that it should be good to go? Or should I run another check after the parity check gets done?

Edited July 5, 2023 by gundy

[JorgeB]

13 hours ago, gundy said:

edit: It started a parity check, other than that it should be good to go?

One should be good.