DISK 1 - Unmountable: Unsupported Partition Layout after moving drives to new machine

[Ryanagon]

Just looking for some advice here because I don't want to do anything wrong that I can't reverse.    I had some major hardware failure on my old machine so I moved unraid disks to a new machine.    It's been a bit of an ordeal but now I get the above message for my Disk 1 when starting the array.   All disks were formatted as XFS and this disk has data on it.   When I run a Check Disk I get xfs_repair: data size check failed and it is unable to repair.    The drive is 3TB (1 of 3 3TB drives - the others seem find), my Parity is 4TB (and I have another 4TB drive in the array).   They are all WD Red drives.

 

SMART check says everything is ok... do I format the drive and will that have parity rebuild it?   Do I replace the drive?    Sorry, I haven't run across anything like this before.

[ChatNoir]

56 minutes ago, Ryanagon said:

do I format the drive and will that have parity rebuild it?

No, Format is NEVER part of data recovery.

 

Please attach your diagnostics to your next post.

[Ryanagon]

Thanks, I have attached the diagnostic

server-diagnostics-20221007-0837.zip

[JorgeB]

Partition appears to be damaged, post the output of:

 

fdisk -l /dev/sdc

 

[Ryanagon]

Disk /dev/sdc: 119.24 GiB, 128035676160 bytes, 250069680 sectors

Disk model: KINGSTON SVP180S

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disklabel type: dos

Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type

/dev/sdc1 64 250069679 250069616 119.2G 83 Linux

 

 

This is the output from the same command on the drive that will not mount:

fdisk -l /dev/sde

Disk /dev/sde: 2.73 TiB, 3000591900160 bytes, 5860531055 sectors

Disk model: WDC WD30EFRX-68E

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: dos

Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type

/dev/sde1 1 4294967295 4294967295 2T ee GPT

Partition 1 does not start on physical sector boundary.

[JorgeB]

7 minutes ago, Ryanagon said:

This is the output from the same command on the drive that will not mount:

OK, devices changed since the diags you've posted, it was sdc:

Oct  7 00:12:30 STORMWATCH  emhttpd: WDC_WD30EFRX-68EUZN0_WD-WCC4N1PYS69N (sdc) 512 5860531055

It confirms that the partition is damaged, easiest option it to rebuild the disk since Unraid will recreate the partition, stop array, unassign that disk, start array, post new diags.

[Ryanagon]

Yes my apologies, I swapped a cable just to be sure it wasn't an issue.

stormwatch-diagnostics-20221007-1040.zip

[JorgeB]

Oct  7 10:39:37 STORMWATCH kernel: mount: attempt to access beyond end of device

There's a problem related to the device size in the emulated disk, see if the actual disk mounts with the UD plugin.

[Ryanagon]

I'm sorry, getting a little lost now.    This is the only option I see:

 

[JorgeB]

That means UD is also not detecting a valid partition, one way out of this might be replacing the disk with a larger one, though cannot be sure it's going to work.

[Ryanagon]

For some reason it is looking for the partition at sector 1 instead of 64 but I have no idea if there is a way to tell it to look at 64 instead.   

[JorgeB]

Try

gdisk /dev/sdX

and see if it gives the option to fix the partition.

[Ryanagon]

It did seem to fix a couple of the issues but i'm left with the following:  

 

Problem: partition 1 is too big for the disk.

Warning! Secondary partition table overlaps the last partition by

2113 blocks!

You will need to delete this partition or resize it in another utility.

Caution: Partition 1 doesn't end on a 64-sector boundary. This may

result in problems with some disk encryption tools.

Identified 3 problems!

 

Partition Information:

Command (? for help): i

Using 1

Partition GUID code: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem)

Partition unique GUID: 6BA205EA-9B41-4CE8-BB0A-62860EA02B71

First sector: 64 (at 32.0 KiB)

Last sector: 5860533134 (at 2.7 TiB)

Partition size: 5860533071 sectors (2.7 TiB)

Attribute flags: 0000000000000000

Partition name: ''

[JorgeB]

Sorry, I cannot help more, no experience with that, like mentioned rebuilding to a larger disk might work, other than that and if you have backups format the disk and restore from there.

[Ryanagon]

Thanks a lot for all your help.  I have ordered a larger disk and will try replacing and rebuilding to that.