H0TF00T Posted August 22, 2023 Share Posted August 22, 2023 Hi Team, I tried migrating my Unraid server unsuccessfully to a different piece of tin and after wrestling with the new machine, decided to revert everything back to where it originally came from. Now I am faced with the dreaded Unmountable: Unsupported partition layout message with everything back in its original spot. Have no idea what to do from here as I dont want to format these drives as they have all my data on them. Is there anything I can do besides a complete rebuild and data recovery? I'm running - Version: 6.12.3 Quote Link to comment
JorgeB Posted August 22, 2023 Share Posted August 22, 2023 Please post the diagnostics. Quote Link to comment
H0TF00T Posted August 22, 2023 Author Share Posted August 22, 2023 tower-diagnostics-20230823-0024.zip Quote Link to comment
H0TF00T Posted August 23, 2023 Author Share Posted August 23, 2023 Also note this in the disk logs, same on each disk ... Aug 23 13:07:37 Tower kernel: ata1: SATA max UDMA/133 abar m2048@0x93300000 port 0x93300100 irq 30 Aug 23 13:07:37 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Aug 23 13:07:37 Tower kernel: ata1.00: ATA-10: WDC WD40EFPX-68C6CN0, 81.00A81, max UDMA/133 Aug 23 13:07:37 Tower kernel: ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA Aug 23 13:07:37 Tower kernel: ata1.00: Features: NCQ-prio Aug 23 13:07:37 Tower kernel: ata1.00: configured for UDMA/133 Aug 23 13:07:37 Tower kernel: sd 2:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Aug 23 13:07:37 Tower kernel: sd 2:0:0:0: [sdc] 4096-byte physical blocks Aug 23 13:07:37 Tower kernel: sd 2:0:0:0: [sdc] Write Protect is off Aug 23 13:07:37 Tower kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Aug 23 13:07:37 Tower kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 23 13:07:37 Tower kernel: sd 2:0:0:0: [sdc] Preferred minimum I/O size 4096 bytes Aug 23 13:07:37 Tower kernel: sd 2:0:0:0: [sdc] Attached SCSI disk Aug 23 13:08:18 Tower emhttpd: WDC_WD40EFPX-68C6CN0_WD-WX62D62EYNAP (sdc) 512 7814037168 Aug 23 13:08:18 Tower emhttpd: read SMART /dev/sdc Aug 23 13:08:38 Tower emhttpd: WDC_WD40EFPX-68C6CN0_WD-WX62D62EYNAP (sdc) 512 7814037168 Aug 23 13:08:38 Tower emhttpd: error: ckmbr, 2337: No such file or directory (2): open: /dev/sdc1 Aug 23 13:08:38 Tower kernel: mdcmd (2): import 1 sdc 64 3907018532 0 WDC_WD40EFPX-68C6CN0_WD-WX62D62EYNAP Aug 23 13:08:38 Tower kernel: md: import disk1: (sdc) WDC_WD40EFPX-68C6CN0_WD-WX62D62EYNAP size: 3907018532 Aug 23 13:08:38 Tower emhttpd: read SMART /dev/sdc Aug 23 13:08:48 Tower emhttpd: WDC_WD40EFPX-68C6CN0_WD-WX62D62EYNAP (sdc) 512 7814037168 Aug 23 13:08:48 Tower emhttpd: error: ckmbr, 2337: No such file or directory (2): open: /dev/sdc1 Aug 23 13:08:48 Tower kernel: mdcmd (2): import 1 sdc 64 3907018532 0 WDC_WD40EFPX-68C6CN0_WD-WX62D62EYNAP Aug 23 13:08:48 Tower kernel: md: import disk1: (sdc) WDC_WD40EFPX-68C6CN0_WD-WX62D62EYNAP size: 3907018532 Aug 23 13:08:48 Tower emhttpd: read SMART /dev/sdc Aug 23 13:08:54 Tower emhttpd: WDC_WD40EFPX-68C6CN0_WD-WX62D62EYNAP (sdc) 512 7814037168 Aug 23 13:08:54 Tower emhttpd: error: ckmbr, 2337: No such file or directory (2): open: /dev/sdc1 Aug 23 13:08:54 Tower kernel: mdcmd (2): import 1 sdc 64 3907018532 0 WDC_WD40EFPX-68C6CN0_WD-WX62D62EYNAP Aug 23 13:08:54 Tower kernel: md: import disk1: (sdc) WDC_WD40EFPX-68C6CN0_WD-WX62D62EYNAP size: 3907018532 Quote Link to comment
JorgeB Posted August 23, 2023 Share Posted August 23, 2023 MBR appears to be corrupt for all disks, did the other server use a RAID controller? Post the output of fdisk -l /dev/sdc Quote Link to comment
H0TF00T Posted August 23, 2023 Author Share Posted August 23, 2023 Hi Jorge, yes it did. You're spot on... The primary GPT table is corrupt, but the backup appears OK, so that will be used. Disk /dev/sdc: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD40EFPX-68C Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: A673DF6A-381F-4B65-9C6E-F1AC541AD757 Device Start End Sectors Size Type /dev/sdc1 64 7814037134 7814037071 3.6T Linux filesystem Will it be ok to run gdisk to repair the GPT table? Quote Link to comment
H0TF00T Posted August 23, 2023 Author Share Posted August 23, 2023 Have just found this post - Quote Link to comment
Solution H0TF00T Posted August 24, 2023 Author Solution Share Posted August 24, 2023 Now resolved - Steps Taken Stop array ran gsisk /dev/sdxx over all unmountable disks after confirming GPT was corrupted binitially checking with fdisk -l /dev/sdxx (Thank you JorgeB!) below process example for my /dev/sdf disk ... root@Tower:/dev# gdisk /dev/sdf GPT fdisk (gdisk) version 1.0.9.1 Caution: invalid main GPT header, but valid backup; regenerating main header from backup! Warning: Invalid CRC on main header data; loaded backup partition table. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables. Warning! Main partition table CRC mismatch! Loaded backup partition table instead of main partition table! Warning! One or more CRCs don't match. You should repair the disk! Main header: ERROR Backup header: OK Main partition table: ERROR Backup partition table: OK Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged **************************************************************************** Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. **************************************************************************** Command (? for help): ? b back up GPT data to a file c change a partition's name d delete a partition i show detailed information on a partition l list known partition types n add a new partition o create a new empty GUID partition table (GPT) p print the partition table q quit without saving changes r recovery and transformation options (experts only) s sort partitions t change a partition's type code v verify disk w write table to disk and exit x extra functionality (experts only) ? print this menu Command (? for help): b Enter backup filename to save: bupsdf.txt The operation has completed successfully. Command (? for help): r Recovery/transformation command (? for help): c Warning! This will probably do weird things if you've converted an MBR to GPT form and haven't yet saved the GPT! Proceed? (Y/N): y Recovery/transformation command (? for help): w Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed? (Y/N): y OK; writing new GUID partition table (GPT) to /dev/sdf. The operation has completed successfully. root@Tower:/dev# gdisk /dev/sdf GPT fdisk (gdisk) version 1.0.9.1 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Rebooted server and everything is happy - running a parity check. This issue arose from placing my disks in another server in attempt to migrate my Unraid setup. The new server had an Adaptec raid card and I couldn't get it to see my disks without going through the process of trashing the data on my disks. A new install with fresh disks would have been ok. As far as I could tell. So when I placed everything back into the original machine, the disks were unmountable because of whatever the raid card did while in the intended target server. Big thanks to JorgeB again! 1 Quote Link to comment
fjmalan Posted August 24, 2023 Share Posted August 24, 2023 Thanks so much @hotfoot and @JorgeB i had almost exactly the exact same experience (Also with a Adaptec 6805e moving to another case) One difference was that my Main header was OK : The primary GPT table is corrupt, but the backup appears OK, so that will be used. Disk /dev/sdj: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: WDC WD80EFZX-68U Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 17FE5483-ABCB-49BD-9E0D-A07F054DB25A Device Start End Sectors Size Type /dev/sdj1 64 15628053134 15628053071 7.3T Linux filesystem root@Diskbox:~# gdisk /dev/sdj GPT fdisk (gdisk) version 1.0.9.1 Caution! After loading partitions, the CRC doesn't check out! Warning! Main partition table CRC mismatch! Loaded backup partition table instead of main partition table! Warning! One or more CRCs don't match. You should repair the disk! Main header: OK Backup header: OK Main partition table: ERROR Backup partition table: OK Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged i was also able to fix it with gdisk -> r -> c (this happened to 3 of the 9 disks in the array) Once done i had to remove the device from the array and reassign it but everything is back to normal now. 1 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.