[SOLVED] Unmountable: No file system

[KoNeko]

i replaced my USB stick after it was unmounted in unraid.

 

After starting up and replacing the key. i needed to assign all hdd's again. Might have mixed 2-3 hdd's up in the order because it says on 1 hdd Unmountable: No file system.

 

i have 3x 12 tbs 1 parity and 2 data 12 tb and others are 3 and 8 the 8 tb is on the same spot again and the 2x3 are also i think.

 

how can i fix this spot without losing the data?  it says format to give it a file system.

 

Edited September 9, 2020 by KoNeko
Solved

[JorgeB]

Do you known for sure which disk was parity? If not make sure you don't assign any disk to the parity slot, also please post diags.

[KoNeko]

31 minutes ago, JorgeB said:

Do you known for sure which disk was parity? If not make sure you don't assign any disk to the parity slot, also please post diags.

Not totally sure.  but i might have switched the parity and disk 2. and did start the array. Its now stopped.

thanekos-diagnostics-20200907-1829.zip

[JorgeB]

7 minutes ago, KoNeko said:

but i might have switched the parity and disk 2

According to previous diags you assigned old disk1 to parity slot, and that's a shame since you had the diags posted here, so just needed to check that if you weren't sure which disk was which, and since the parity sync run for a few minutes that disk will now also be unmountable.

 

You can force rebuilding that disk using the invalid slot command but note that since the array was started read/write parity won't be 100% valid, there may be at least some fs corruption, follow the instructions bellow carefully and ask if there's any doubt.

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-Check all assignments and assign any missing disk(s) if needed, assign old parity as parity, and current parity as disk2 (or 1 if you want, data disks order doesn't matter with single parity)
-Important - After checking the assignments leave the browser on that page, the "Main" page.

-Open an SSH session/use the console and type (don't copy/paste directly from the forum, as sometimes it can insert extra characters):

mdcmd set invalidslot 2 29

(assuming you assigned that disk as disk2, if it's now disk1 replace 2 with 1)

 

-Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box (GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the invalid slot command, but they won't be as long as the procedure was correctly done), disk2 will start rebuilding, disk should mount immediately (possibly not in this case) but if it's unmountable don't format, wait for the rebuild to finish (or cancel it) and then run a filesystem check.

 

 

[KoNeko]

8 minutes ago, JorgeB said:

According to previous diags you assigned old disk1 to parity slot, and that's a shame since you had the diags posted here, so just needed to check that if you weren't sure which disk was which, and since the parity sync run for a few minutes that disk will now also be unmountable.

 

You can force rebuilding that disk using the invalid slot command but note that since the array was started read/write parity won't be 100% valid, there may be at least some fs corruption, follow the instructions bellow carefully and ask if there's any doubt.

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-Check all assignments and assign any missing disk(s) if needed, assign old parity as parity, and current parity as disk2 (or 1 if you want, data disks order doesn't matter with single parity)
-Important - After checking the assignments leave the browser on that page, the "Main" page.

-Open an SSH session/use the console and type (don't copy/paste directly from the forum, as sometimes it can insert extra characters):

mdcmd set invalidslot 2 29

(assuming you assigned that disk as disk2, if it's now disk1 replace 2 with 1)

 

-Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box (GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the invalid slot command, but they won't be as long as the procedure was correctly done), disk2 will start rebuilding, disk should mount immediately (possibly not in this case) but if it's unmountable don't format, wait for the rebuild to finish (or cancel it) and then run a filesystem check.

 

8 minutes ago, JorgeB said:

 

ok did all steps

it does say now

Unraid Disk 2 error: 07-09-2020 20:56

Warning - Disk 2, drive not ready, content being reconstructed
WDC_WD120EDAZ-11F3RA0_8CKZESUF (sdf)

but it says unmountable.

 

Is there a big difference in stopping now and do the filessystem check or do it later after the rebuild is done ?

 

How do i do the filesystem check ?

[JorgeB]

You can do it now, you'll need to restart the rebuild but at least you'll know if it's worth it or not, since whatever is on the emulated disk will be on the actual disk after it's done rebuilding.

 

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

[KoNeko]

On 9/7/2020 at 9:47 PM, JorgeB said:

You can do it now, you'll need to restart the rebuild but at least you'll know if it's worth it or not, since whatever is on the emulated disk will be on the actual disk after it's done rebuilding.

 

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

i let the drive finsch it's check and that is done.

 

now im doing the preparing to test.

i put the array in maintenance mode and check the disk but i dont see the button check.  It was a XFS before like all hdd's

[JorgeB]

Set the filesystem to xfs and it should work, if not you can do it using the console:

https://wiki.unraid.net/Check_Disk_Filesystems#Drives_formatted_with_XFS

[KoNeko]

8 hours ago, JorgeB said:

Set the filesystem to xfs and it should work, if not you can do it using the console:

https://wiki.unraid.net/Check_Disk_Filesystems#Drives_formatted_with_XFS

Ok great its Fixed now