Problem with an Unmountable: Unsupported partition layout disk


Go to solution Solved by JorgeB,

Recommended Posts

Hi everyone,

 

I have checked my server today and discovered that one of my disk show the message "Unmountable: Unsupported partition layout". This is not a new disk. It is there for many years now and I don't know why I got this message today.

 

I have the option to format the disk but I'm not sure it's the way to go. What steps should I do to fix this? I have attached my diagnotics file in case it can help.

 

Thank you for your help!

 

image.thumb.png.cc756a28d284873a8d8acb461edebd05.png

tower-diagnostics-20220802-2027.zip

Link to comment
Posted (edited)

I don't mind losing the data on this disk if I can get it back by rebuilding the array but if I can fix it without doing that, it would be great. Here's the result for the Check Filesystem:

 

Phase 1 - find and verify superblock...
        - block cache size set to 148496 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 2270027 tail block 2270027
        - scan filesystem freespace and inode maps...
        - 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
        - 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
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

        XFS_REPAIR Summary    Tue Aug  2 22:21:54 2022

Phase        Start        End        Duration
Phase 1:    08/02 22:21:48    08/02 22:21:48
Phase 2:    08/02 22:21:48    08/02 22:21:49    1 second
Phase 3:    08/02 22:21:49    08/02 22:21:53    4 seconds
Phase 4:    08/02 22:21:53    08/02 22:21:53
Phase 5:    Skipped
Phase 6:    08/02 22:21:53    08/02 22:21:54    1 second
Phase 7:    08/02 22:21:54    08/02 22:21:54

Total run time: 6 seconds

Edited by skoub
Link to comment
8 minutes ago, skoub said:

don't mind losing the data on this disk if I can get it back by rebuilding the array

Rebuilding won't fix unmountable.

 

10 minutes ago, skoub said:

Here's the result

That doesn't look bad. You have to remove -n (nomodify) to get it to actually do the repair.

Link to comment
  • Solution

"Invalid partition layout" is not a filesystem problem, the disk lost/damaged some part of the MBR, looks like it mostly happens with WD disks, so possibly a firmware problem.

 

To fix you can rebuild the the disk, assuming parity is valid, you just unassign it, start the array, Unraid will recreate the partition correctly and emulated the disk, if all looks good you can then rebuild on top, alternatively you could mount the disk outside the array and copy the data back to it.

Link to comment
Posted (edited)

I've done the filesystem check without the -n switch but no luck, the disk is still in "invalid partition layout" state. Here's the result:

 

Phase 1 - find and verify superblock...
        - block cache size set to 148496 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 2270027 tail block 2270027
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - 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
Phase 5 - rebuild AG headers and trees...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...

        XFS_REPAIR Summary    Thu Aug  4 17:42:27 2022

Phase        Start        End        Duration
Phase 1:    08/04 17:42:04    08/04 17:42:13    9 seconds
Phase 2:    08/04 17:42:13    08/04 17:42:14    1 second
Phase 3:    08/04 17:42:14    08/04 17:42:18    4 seconds
Phase 4:    08/04 17:42:18    08/04 17:42:18
Phase 5:    08/04 17:42:18    08/04 17:42:26    8 seconds
Phase 6:    08/04 17:42:26    08/04 17:42:27    1 second
Phase 7:    08/04 17:42:27    08/04 17:42:27

Total run time: 23 seconds
done

 

 

So my last option is to rebuild my disk? Can someone confirm the steps please?

  1. stop the array
  2. unassign the disk
  3. start the array without the disk
  4. format the disk with the option that is shown "Format will create a file system in all Unmountable disks"
  5. stop the array
  6. reassign the disk
  7. start the array
  8. let the system rebuild my disk
Edited by skoub
Link to comment
2 hours ago, skoub said:

format the disk with the option that is shown "Format will create a file system in all Unmountable disks"

Absolutely NOT.

 

Format is a write operation. It writes an empty filesystem to the disk.

 

When you format a disk in the parity array, Unraid treats that write operation just like any other, by updating parity. Then rebuild can only result in an empty filesystem.

 

NEVER format a disk unless you don't care about any data it might have.

Link to comment
On 8/3/2022 at 4:32 AM, JorgeB said:

unassign it, start the array, Unraid will recreate the partition correctly and emulated the disk, if all looks good

 

Take this in 2 parts

 

1st part:

  

2 hours ago, skoub said:
  1. stop the array
  2. unassign the disk
  3. start the array without the disk

 

Do not proceed beyond starting the array with the disk unassigned.

 

See if the emulated disk is mountable and has your data.

 

Let us know how that 1st part goes and we can go on to the next part.

Link to comment

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.