Ymetro Posted April 7, 2021 Share Posted April 7, 2021 (edited) 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 April 7, 2021 by Ymetro added reason Quote Link to comment
Ymetro Posted April 7, 2021 Author Share Posted April 7, 2021 (edited) 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 April 7, 2021 by Ymetro put into codeblock Quote Link to comment
JorgeB Posted April 7, 2021 Share Posted April 7, 2021 Does it mount if you back to v6.8? Quote Link to comment
Ymetro Posted April 7, 2021 Author Share Posted April 7, 2021 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? Quote Link to comment
trurl Posted April 7, 2021 Share Posted April 7, 2021 Download 6.8.3 from DOWNLOADS page and replace all bz* files on flash with those from download. Quote Link to comment
Ymetro Posted April 8, 2021 Author Share Posted April 8, 2021 (edited) 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 April 8, 2021 by Ymetro added cache pool missing notice Quote Link to comment
JorgeB Posted April 8, 2021 Share Posted April 8, 2021 Please post output of: hexdump -C -n 512 /dev/sdX replace X with correct letter. Quote Link to comment
Ymetro Posted April 8, 2021 Author Share Posted April 8, 2021 (edited) 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 April 8, 2021 by Ymetro Quote Link to comment
JorgeB Posted April 8, 2021 Share Posted April 8, 2021 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. Quote Link to comment
Ymetro Posted April 8, 2021 Author Share Posted April 8, 2021 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. Quote Link to comment
JorgeB Posted April 8, 2021 Share Posted April 8, 2021 30 minutes ago, Ymetro said: I submitted the bug report, That is also OK but I meant creating a bug report here: https://forums.unraid.net/bug-reports/stable-releases/ Quote Link to comment
Recommended Posts
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.