[SOLVED] Help with "Unmountable: Wrong or no file sysem"


Go to solution Solved by itimpi,

Recommended Posts

While cleaning up old VM templates I accidentally hit start all and it knocked my sata controller off Unraid. After a reboot I have 1 drive displaying "Unmountable: Wrong or no file system"

 

I've put the array into maintenance mode and run check on the disk and it's returned the following. Can someone advise what's the next step? 

 

Diags also attached. 

 

Phase 1 - find and verify superblock...
        - reporting progress in intervals of 15 minutes
        - block cache size set to 3023256 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 3555296 tail block 3555280
ALERT: The filesystem has valuable metadata changes in a log which is being
ignored because the -n option was used.  Expect spurious inconsistencies
which may be resolved by first mounting the filesystem to replay the log.
        - 01:26:17: zeroing log - 521728 of 521728 blocks done
        - scan filesystem freespace and inode maps...
sb_fdblocks 165905622, counted 170614505
        - 01:26:18: scanning filesystem freespace - 32 of 32 allocation groups done
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - 01:26:18: scanning agi unlinked lists - 32 of 32 allocation groups done
        - process known inodes and perform inode discovery...
        - agno = 15
        - agno = 0
        - agno = 30
        - agno = 31
        - agno = 16
        - agno = 1
        - agno = 17
        - agno = 2
        - agno = 18
        - agno = 3
        - agno = 19
        - agno = 4
        - agno = 20
        - agno = 5
        - agno = 6
        - agno = 21
        - agno = 22
        - agno = 7
        - agno = 8
        - agno = 23
        - agno = 24
        - agno = 9
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - 01:26:26: process known inodes and inode discovery - 60864 of 60864 inodes done
        - process newly discovered inodes...
        - 01:26:26: process newly discovered inodes - 32 of 32 allocation groups done
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - 01:26:26: setting up duplicate extent list - 32 of 32 allocation groups done
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 9
        - agno = 10
        - agno = 12
        - agno = 11
        - agno = 13
        - agno = 2
        - agno = 3
        - agno = 16
        - agno = 8
        - agno = 4
        - agno = 18
        - agno = 14
        - agno = 22
        - agno = 20
        - agno = 19
        - agno = 21
        - agno = 15
        - agno = 17
        - agno = 24
        - agno = 23
        - agno = 25
        - agno = 26
        - agno = 27
        - agno = 28
        - agno = 29
        - agno = 30
        - agno = 31
        - 01:26:26: check for inodes claiming duplicate blocks - 60864 of 60864 inodes done
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - agno = 0
        - agno = 30
        - agno = 15
        - agno = 31
        - agno = 16
        - agno = 1
        - agno = 2
        - agno = 17
        - agno = 3
        - agno = 18
        - agno = 4
        - agno = 19
        - agno = 5
        - agno = 20
        - agno = 6
        - agno = 21
        - agno = 7
        - agno = 8
        - agno = 22
        - agno = 9
        - agno = 23
        - agno = 24
        - agno = 10
        - agno = 25
        - agno = 26
        - agno = 11
        - agno = 27
        - agno = 12
        - agno = 28
        - agno = 13
        - agno = 29
        - agno = 14
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
        - 01:26:32: verify and correct link counts - 32 of 32 allocation groups done
No modify flag set, skipping filesystem flush and exiting.

        XFS_REPAIR Summary    Fri May 20 01:26:32 2022

Phase		Start		End		Duration
Phase 1:	05/20 01:26:16	05/20 01:26:17	1 second
Phase 2:	05/20 01:26:17	05/20 01:26:18	1 second
Phase 3:	05/20 01:26:18	05/20 01:26:26	8 seconds
Phase 4:	05/20 01:26:26	05/20 01:26:26
Phase 5:	Skipped
Phase 6:	05/20 01:26:26	05/20 01:26:32	6 seconds
Phase 7:	05/20 01:26:32	05/20 01:26:32

Total run time: 16 seconds

 

 

Quote

 

 

voyager-diagnostics-20220520-0136.zip

Edited by AceRimmer
Marking as solved
Link to comment
  • Solution

That looks as if no major corruption was found.

3 hours ago, AceRimmer said:
No modify flag set, skipping filesystem flush and exiting

You need to run without the -n option if you want anything to be fixed, and if it asks for it add the -L option.

 

Restarting in normal mode should mean the drive then mounts OK.   Look to see if you now have a lost+found folder - if not all data should be intact.

Link to comment

I just want to check before I proceed. I ran check without any options and got the below output I assume I re-run check with -L this time?

 

Phase 1 - find and verify superblock...
        - reporting progress in intervals of 15 minutes
Phase 2 - using internal log
        - zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair.  If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.

 

Link to comment

I've run the -L and restarted. My Disk4 no longer shows that unmountable error when I go to the disk settings but on my list of array drives it still has an "X" and when I hover it says "device is disabled, contents emulated"

PXL_20220520_115736073.jpg

PXL_20220520_115744559.jpg

Edited by AceRimmer
Link to comment
  • AceRimmer changed the title to [SOLVED] Help with "Unmountable: Wrong or no file sysem"

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.