Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unmountable: Unsupported partition layout after upgrading 6.8.? to 6.9.0

Featured Replies

Since I updated/upgraded the Unriad server to version 6.9.0 the Disk1 of the array says "Unmountable: Unsupported partition layout" and Partition format says "factory-erased", but that was not the case: it was formatted, running fine and filled to the brim with data when it was running under Unraid 6.8!

 

I did a maintenance mode check on it like it was recommended on this forum: 

But it didn't seem to fix the problem. 

😢Sadly I have no parity secured array to recover the disk with, because two of my disks have errors and where disabled by the system and I yet have to RMA them. 1 of them was the parity drive. 

🍀Luckily I still got warranty on both those drives. I got the impression both disks where from Amazon. And I am not so confident that Amazon handels these harddrives well enough. 🤔

 

🙏Hopefully only the Steam game library was on there and can be redownloaded. 

I like to know if there is anything that can be done to fix this before I throw in the towel and format the drive for the array.

Anyone got any idea if this can be fixed? 

Edited by Ymetro
added reason

  • Author

Disk check gave this:

 

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - 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 = 12
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        ...
        - agno = 12
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.

 

Edited by Ymetro
put into codeblock

  • Community Expert

Does it mount if you back to v6.8?

  • Author
6 hours ago, JorgeB said:

Does it mount if you back to v6.8?

Have already updated to 6.9.1 and according to the Tools section I can only rollback to 6.9.0.
Is there a way to rollback any further to 6.8? 

  • Community Expert

Download 6.8.3 from DOWNLOADS page and replace all bz* files on flash with those from download.

  • Author
12 hours ago, trurl said:

Download 6.8.3 from DOWNLOADS page and replace all bz* files on flash with those from download.

I did what you said and went ahead making a backup of the entire USB for: "just in case". 

 

Now my server is back up and running 6.8.3 AND it shows Disk1 agian!! Awesome! 👍🥳

 

I didn't knew changing versions was this easy. 😎

 

O: I only had to reactivate the cache pool - good that I made a screenshot earlier for the right order. 

 

Should I stay on 6.8.3 or try again with 6.9.2? 🤔

Edited by Ymetro
added cache pool missing notice

  • Community Expert

Please post output of:

 

hexdump -C -n 512 /dev/sdX

 

replace X with correct letter.

  • Author

It gives for Disk1:

 

00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001c0  02 00 00 ff ff ff 01 00  00 00 ff ff ff ff 00 00  |................|
000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200

 

What does this say about this disk?

Edited by Ymetro

  • Community Expert

IIRC disk has a different MBR signature and due to a bug Unraid doesn't consider it a valid partition, LT was suppose to fix this but guess it fell though the cracks, you should create  a bug report.

  • Author

I submitted the bug report, including above findings. 
I await their recommendations before any upgrading to 6.9.
Thank you @JorgeB and @trurl for helping me out! 🙏👍

I'll report back when this is fixed. 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.