UNMOUNTABLE: NO FILE SYSTEM

[Mattlevant]

I lost disk 3 & 4 rebooted and both came back online but 4 showed no file system, stopped array started in maintenance mode, removed drive 4 and readded and started array, unraid completed a rebuild of the drive but it still shows unmountable

i have attached diagnostics and a screenshow of the home of the UI

how can i get it back without formatting?
 

tower-diagnostics-20230430-1419.zip

[itimpi]

Rebuilding a drive will not fix the ‘unmountable’ status as that is normally caused by file system level corruption that parity is not aware of.

 

The correct handling of unmountable drives is documented here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

[Mattlevant]

9 minutes ago, itimpi said:

Rebuilding a drive will not fix the ‘unmountable’ status as that is normally caused by file system level corruption that parity is not aware of.

 

The correct handling of unmountable drives is documented here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

it is currectly running a scheduled parity check, is it safe to cancel the parity check and go through the steps to correct the file system on the drive or have i to wait until the check is completed?

[itimpi]

In theory you could do them at the same time, although performance of the check is likely to be bad because of contention with the parity check

 

Are your regular scheduled checks correcting or non-correcting?

[Mattlevant]

1 hour ago, itimpi said:

In theory you could do them at the same time, although performance of the check is likely to be bad because of contention with the parity check

 

Are your regular scheduled checks correcting or non-correcting?

correcting

[itimpi]

23 minutes ago, Mattlevant said:

correcting

In which case I would suggest cancelling an existing parity check if it has not got too far.

 

We normally recommend that scheduled checks are set non-correcting so that if you have a drive playing up it does not corrupt parity.   Ideally you only want to run a correcting check manually when you are reasonably certain you have no outstanding hardware issues.

[Mattlevant]

13 hours ago, itimpi said:

In which case I would suggest cancelling an existing parity check if it has not got too far.

 

We normally recommend that scheduled checks are set non-correcting so that if you have a drive playing up it does not corrupt parity.   Ideally you only want to run a correcting check manually when you are reasonably certain you have no outstanding hardware issues.

I let the parity check finish because it was over 60%, ran the check -n then -L, UI said it could take hours, 5 minutes later it completed, restarted array and disk 4 back online and mounted

im guessing it must have only had a small corruption?

Edited May 1, 2023 by Mattlevant

[itimpi]

The check is normally very fast for xfs format drives so minutes sounds correct.    You should now look to see if you have a lost+found folder on the drive which is where the repair process would put any files for which it could not find the name.