Hi

When i logged in to my unraid server yesterday did I notice that one of the disks had collapsed (disk 4, sdc), many errors. So I turned of the server, replaced the disk with a new one and restarted and assigned the new disk the same place as the old one and started the array. Unraid started to read on the discs and write to the new one, ie restoring the data.

 

But when I logged in a day later when the restoring should be done, I get an error message from the disk saying:

"Unmountable: Wrong or no file system"

 

It is true that I did not format the new disk before starting to rebuild the array, I thought that this would be done automatically. It also seems like the monthly parity check started during the rebuild, finding zero errors.

 

What do I do now? Is the data lost forever, or can I assign a file system to the new disk?

 

Thanks!

store-diagnostics-20220901-2018.zip

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

 

I suggest you keep the disk you removed with its contents intact as it may prove an alternative recovery option for any data.

Thanks, I ran the "Check Filesystem Status" on the disk and got the follwing result, which do not looks good:

 

Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error

 

I get the same result if i remove the -n, it immediately reply as above.

Same strange crashing going on, please reboot and post new diags after array start.

Thanks for the reply JorgeB, I just did a reboot and created a diagnostics file.

 

I have the same behavior as when i discovered this the first time with the original crashed disk, it boots and gets online but many files are missing when I access the share via samba.

store-diagnostics-20220902-2141.zip

Disk4 still unmountable so that would explain missing files.

 

Did you check filesystem from the webUI or from the command line?

I believe that I did it from both the webgui and the terminal in the webgui.

 

But I did it again now from the webgui and got another result, see attached file.

 

BTW, thanks for the support everyone!

xfs_repair status disk 4 2022-09-02.txt

Easy to get the command wrong so better to use the webUI

On 9/1/2022 at 3:18 PM, itimpi said:

keep the disk you removed with its contents intact as it may prove an alternative recovery option for any data

  

Do you have enough ports to install the original disk? Don't assign it but it would be useful to get diagnostics with it and see if it is mountable as an Unassigned Device.

9 hours ago, Lidde said:

But I did it again now from the webgui and got another result, see attached file.

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

9 hours ago, trurl said:

  

Do you have enough ports to install the original disk? Don't assign it but it would be useful to get diagnostics with it and see if it is mountable as an Unassigned Device.

There is no bay free, but I could replace one of the cache disks with the original disk if needed.

 

1 hour ago, JorgeB said:

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

I needed to use the -L, see attached file.

 

xfs_repair status -L disk 4 2022-09-03.txt

Edited September 3, 20223 yr by Lidde

Disk should mount now, look for a lost+found folder.

30 minutes ago, JorgeB said:

Disk should mount now, look for a lost+found folder.

 

It does, thank you so much! Both JorgeB, Trurl and Itimpi!

 

I am using Crashplan for the important files, but there was a lot of files not backed up that is saved now. Really appreciate your support!

How much is in lost+found?

47 minutes ago, trurl said:

How much is in lost+found?

It was 5,27 GB

 

I am trying to figure out if there are files lost or if everything is in the lost+found. Both by moving files from lost+found to the original folders and restoring an crashplan backup.