Jump to content

Wrong or unsupported filesystem


Socrates

Recommended Posts

I have restarted my unraid after moving states, and during this move i had removed the drives from the server and put them in extremely well packed bubble wraps in a secure container.

Now, after a few months i have finally setup my server rack and after installing the hdd's into my 24 supermicro bay, unraid has come back online but two of the drives show "Unmountable: Wrong or no Filesystem" and "Unmountable: Unsupported or Wrong filesystem"

These drives were working before. They were a part of the unraid system, but now i get these. Diagnostic attached with this post.

 

image.thumb.png.658e17ec293f394a117d4aa39e87f522.png

tower-diagnostics-20221218-2345.zip

Edited by Socrates
Link to comment
6 hours ago, JorgeB said:

Assuming disk13 was also xfs, stop the array, click on disk13 and set the filesystem to xfs, start array and post new diags.

 

Thanks for looking into this.

I've performed the operation you recommended on both the disks, made them xfs from auto and started the array again, and still it shows the same result Unmountable: Wrong or no Filesystem" and "Unmountable: Unsupported or Wrong filesystem"

 

New logs from diags attached.

tower-diagnostics-20221219-1101.zip

Link to comment

So here is the final result.

FS: xfs

Executing file system check: /sbin/xfs_repair -n /dev/sdi1 2>&1
Phase 1 - find and verify superblock...
Phase 2 - using internal log
- zero log...
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.
- scan filesystem freespace and inode maps...
sb_fdblocks 1657832310, counted 1659752643
- found root inode chunk
Phase 3 - for each AG...
- scan (but don't clear) agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
- traversing filesystem ...
- traversal finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

File system corruption detected!
RUN WITH CORRECT FLAG
DONE

 

Link to comment
17 hours ago, Socrates said:

Filesystem is not hardware curroption, right? Can't i format the drive, format it with XFS filesystem, this way it becomes a new drive, and then plug it in and resover using the 2 parities I have?

No because file system corruption happens at a different level to hardware failures and is not visible to parity.   If a disk is showing file system corruption before starting a rebuild it would just show the same file system corruption after the rebuild.

Link to comment
On 12/20/2022 at 1:27 PM, JorgeB said:

Did you unassign the disk? Which disk is this one?

 

Steps i undertook

1. Stopped the array.

2. Started the Array in Maintenance mode.

3. Clicked on Disk 12 and then ran the check. No i did not unassign this disk.

 

Do u want to unassign this and then run the xfs check with no -n switch?

Link to comment
18 hours ago, JorgeB said:

That last UD xfs_repair log suggests the fs is fixable, which is strange since when the disk was in the array it didn't look fixable.

Do u want me to go ahead with the fix? Please could u post the steps for fixing this? Or do u want to first run the xfs check again after converting the disk to unassign mode?

Link to comment
  • Socrates changed the title to Wrong or unsupported filesystem

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.

×
×
  • Create New...