At some point my 1st disk decided to crap its pants or the filesystem decided to corrupt itself. I'm not sure what exactly is going on. It says "Unmountable: Unsupported or no file system" Could someone help me narrow down what has happened? I thought maybe a restart would rectify the issue, but it wasn't until after that that I found the issue with the filesystem. I have been wanting to build a backup server for this exact reason but haven't had the funds. If I can do something to fix this issue without completely losing data I would be so grateful.

Any help anyone can give me would be greatly appreciated.

emily-diagnostics-20241215-2045.zip

Check filesystem on disk1, run it without -n

4 hours ago, JorgeB said:

Check filesystem on disk1, run it without -n

Thank you, Jorge. I run into this issue when I attempt to run the xfs_repair : xfs_repair -v /dev/md1 : "  /dev/md1: No such file or directory /dev/md1: No such file or directory fatal error -- couldn't initialize XFS library. "

I did try this in maintenance mode and in with the array started and stopped and I get the same message. Do you have an idea what could be wrong or does the issue exist between chair and keyboard?

Edited December 16, 20241 yr by squirreltats

You should be running it from the GUI which will then put in the correct device name.

1 hour ago, itimpi said:

You should be running it from the GUI which will then put in the correct device name.

I figured it out, thank you. I have a lost+found file but I can't seem to see the content via the CLI. Is there a way of looking at the file via the GUI?

17 minutes ago, squirreltats said:

I can't seem to see the content via the CLI. Is there a way of looking at the file via the GUI?

You should be able to use the Dynamix File Manager plugin (which is built in if using Unraid 7).

6 minutes ago, itimpi said:

You should be able to use the Dynamix File Manager plugin (which is built in if using Unraid 7).

I wasn't clear and I apologize. I can see the file and I can open it, but I cannot make sense of the text. Is there a way of seeing the file with it's content in proper form or seeing the content so I might have an idea of where it needs to go? Many thanks for your patience.

Just now, squirreltats said:

I wasn't clear and I apologize. I can see the file and I can open it, but I cannot make sense of the text. Is there a way of seeing the file with it's content in proper form or seeing the content so I might have an idea of where it needs to go? Many thanks for your patience.

The files in lost+found will have cryptic numeric names as they are ones for which the directory entry could not be found.

 

You can use the Linux 'file' command from the command line to give you an idea of the content type of each file so you can then allocate it a sensible file extension and then use an app for that file type to look at its contents.

 

Sorting out lost+found is a lot of manual work and if you have any sort of backups it is often easier to use those instead.

4 minutes ago, itimpi said:

The files in lost+found will have cryptic numeric names as they are ones for which the directory entry could not be found.

 

You can use the Linux 'file' command from the command line to give you an idea of the content type of each file so you can then allocate it a sensible file extension and then use an app for that file type to look at its contents.

 

Sorting out lost+found is a lot of manual work and if you have any sort of backups it is often easier to use those instead.

Is there a(n) guide/instructions that I may have overlooked on how to use the 'file' command? I am having an issue where when I attempt to use it I get a "XXXXXXX cannot open  'XXXXXXX' (No such file or directory)"

Thankfully the lost+found file is small so I don't have much to go through, but I don't have backups currently as I am saving funds and waiting on Unraid 7 to release before I build a backup server for my current one.

you can try 'file --help' to get the syntax, or try googling for 'linux file command' to get some examples.

4 hours ago, itimpi said:

you can try 'file --help' to get the syntax, or try googling for 'linux file command' to get some examples.

I did as you suggest and use the -d (--debug) and saw some of what is in there, but I couldn't pick out anything that distinguished where it came from or what exactly was in it, I could only guess it was from a backup. Thank you for your assistance. Would parity be able to fill in the gap that is made by the lost+found?

 

I just realized I did not get anywhere with the "file command". I will do some more research and see what I can come up with before bugging the community/mods about this. I appreciate everyone's help!

Edited December 17, 20241 yr by squirreltats