Jump to content

"Unmountable: Unsupported partition layout" after power cut


AlphaXL
Go to solution Solved by JorgeB,

Recommended Posts

Disk /dev/sdh: 12.73 TiB, 14000519643136 bytes, 27344764928 sectors
Disk model: ST14000NM001G-2K
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: 0D5DAF02-CD7C-4F29-9321-2594F511604D

Device     Start         End     Sectors  Size Type
/dev/sdh1     64 27344764894 27344764831 12.7T Linux filesystem

Link to comment
  • Solution

Partition isn't corrupt, so something changed the disk MBR, usually the easiest way to recover is rebuild that disk on top, Unraid will recreate the partition with the correct MBR, you can test by unassigning the disk and starting the array, Unraid will emulate the missing disk and it should mount immediately, assuming parity is in sync, if it mounts and contents look correct just rebuild on top.

Link to comment

That drive is connected to: LSI/Avago/Broadcom SAS 9300-8i HBA PCIe 3.0

 

Just to add... Power cut happened while I was copying files from unassigned disk into the array. Maybe that's why it wasn't mountable after powering back up?

 

That's my server:

 

- Intel Core i5-9600K 9th Gen Coffee Lake
- Cooler Master Hyper H412R
- ASRock B365M Phantom Gaming 4
- Crucial 32GB DDR4 RAM 2666MHz PC4-21300 CL19
- LSI/Avago/Broadcom SAS 9300-8i HBA PCIe 3.0
- Kingston DataTraveler Kyson 32GB USB 3.2 Flash Drive (Unraid)
- 112TB HDD storage (data array)
- 2×18TB HDD (parity array)
- 2×Samsung 970 EVO Plus NVMe M.2 SSD 1TB (cache pool)
- Seasonic CORE GC 650W 80 PLUS Gold
- 3×120mm BeQuiet! Pure Wings 2 PWM [intake]
- 2×80mm BeQuiet! Pure Wings 2 PWM [exhaust]
- Logic Case SC-415A 4U rackmount

- CyberPower BRICs LCD Series UPS 1000VA 600W

svalbard-diagnostics-20220219-1137.zip

Edited by AlphaXL
Link to comment

OK, that controller is usually fine, firmware is also latest, for there to be an invalid partition layout error it means the MBR was changed, that's the very beginning of the disk, outside the partition to where data gets written to, so that should never happen just because of a power cut, but you're not the first, not sure what the problem is, disk or controller would be the main suspects.

Link to comment

I was running the same server/hardware on the latest Ubuntu Server the last 2 years (before switching over to Unraid) and had a few power cuts also during that time period and no issues with disks mounting after or anything like that. Of course I had no array or parity etc. Just separate disks and formatted in ext4 and full of data files.

 

I suspect that could it have been because I was copying files (writing into the array) when the power cut happened?

 

I will keep an eye on that disk and I will be swapping out smaller disks for bigger ones in the future anyway... So I might swap that one soon just to be on the safe side.

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.

×
×
  • Create New...