Hi, hoping someone can help me out with this. My Unraid system seems to have developed a problem. System was working fine at last shutdown, had a power cut while the system was shut down but still plugged in, and now I've got this fault on Disk 3 "Unmountable: No file system" Not sure if the power cut caused it, don't know how as it wasn't running at the time, but it's the only thing that has happened since last shutdown. I've included a copy of the Syslog as well as the results of a Check Filesystem Status check (I've "x" some of the file names as they contain personal info).

 

Can I simply repair in situ or do I need to pull and replace the drive, then rebuild via parity? Hoping for the former rather than the latter tbh.

 

Thanks for any help you can offer.

Check Filesystem Status.txt syslog.txt

Run xfs_repair again without -n or nothing will be done.

9 minutes ago, JorgeB said:

Run xfs_repair again without -n or nothing will be done.

Sorry if this sounds like a really silly question, but is it that simple to get the drive back up and running?

It's the first thing to do.

2 minutes ago, JorgeB said:

It's the first thing to do.

Comes back with this

 

"Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
Log inconsistent (didn't find previous header)
failed to find log head
zero_log: cannot find log head/tail (xlog_find_tail=5)
ERROR: The log head and/or tail cannot be discovered. Attempt to mount the
filesystem to replay the log or use the -L option to destroy the log and
attempt a repair."

Use -L

32 minutes ago, JorgeB said:

Use -L

Will that cause any damage to the data?

 

EDIT: Figured I'd give it a go anyway, doesn't appear to be many options available to me at the moment. Will post the results when it's done, thanks.

Edited November 3, 20232 yr by Alexw80

Results from -L

Check Filesystem Status -L result.txt

Usually it's fine, but it will depend on the actual filesystem corruption, but like you mentioned, there are no other options.

Start in normal mode now and it should mount, check contents and look for a lost+found folder.

6 minutes ago, JorgeB said:

Start in normal mode now and it should mount, check contents and look for a lost+found folder.

Done that, found the lost+found folder. Has 164 files in it, all with numbers for names. Assuming they've been renamed by the system. Do I need to go through them all and rename/move the files back manually?

Just now, Alexw80 said:

Do I need to go through them all and rename/move the files back manually?

Yes as these are ones where the directory entry giving the name could not be found by the repair process, although it can be easier to restore from backups.    If you need to go through them manually then the linux 'file' command can at least give you the content type for each file.

7 minutes ago, itimpi said:

Yes as these are ones where the directory entry giving the name could not be found by the repair process, although it can be easier to restore from backups.    If you need to go through them manually then the linux 'file' command can at least give you the content type for each file.

Think I know what file types they all are, just based on the size of the files. No idea what some of the original file names were though lol. Thankfully, it doesn't look like it contains anything serious, or at least nothing I can't get back.

 

22 minutes ago, JorgeB said:

Start in normal mode now and it should mount, check contents and look for a lost+found folder.

 

11 minutes ago, itimpi said:

Yes as these are ones where the directory entry giving the name could not be found by the repair process, although it can be easier to restore from backups.    If you need to go through them manually then the linux 'file' command can at least give you the content type for each file.

 

Any idea what might have caused this issue? Is it possible that the power cut cause it, even though the system wasn't actually running at the time?

9 minutes ago, Alexw80 said:

Is it possible that the power cut cause it, even though the system wasn't actually running at the time?

If you mean the server was off it couldn't have been that.

1 minute ago, JorgeB said:

If you mean the server was off it couldn't have been that.

Thought so, the power cut was the only thing that happened between the last time I used it (working fine then) and today when I fired it back up. So just assume it was one of those things, it threw a hissy fit and knocked out a drive for some random reason. Gotta love tech lol

 

Anyway, it seems to be running fine, for now at least. Thank you so much for you help, it really is appreciated.