Am 18.05.21 um 19:47 schrieb Phil Turmel:
On 5/17/21 9:19 AM, Roman Mamedov wrote:
On Mon, 17 May 2021 05:36:42 -0500
Roger Heflin <rogerheflin@xxxxxxxxx> wrote:
When I look at my 1.2 block, the mdraid header appears to start at
4k, and
the gpt partition table starts at 0x0000 and ends before 4k.
He may be able to simply delete the partition and have it work.
Christopher wrote that he tried:
chris@ursula:~$ sudo /sbin/mdadm --verbose --assemble /dev/md0
/dev/sdb /dev/sdc /dev/sdd
mdadm: looking for devices for /dev/md0
mdadm: Cannot assemble mbr metadata on /dev/sdb
mdadm: /dev/sdb has no superblock - assembly aborted
I would have expected mdadm when passed entire devices (not
partitions) to not
even look if there are any partitions, and directly proceed to
checking if
there's a superblock at its supposed location. But maybe indeed, from the
messages it looks like it bails before that, on seeing "mbr metadata",
i.e.
the enclosing MBR partition table of GPT.
The Microsoft system partition starts on top of the location for v1.2
metadata.
Just another reason to *never* use bare drives
the most important is that you have no guarantee that a replacement
drive years later is 100% identical in size
leave some margin and padding around the used space solves that problem
entirely and i still need to hear a single valid reason for using
unpartitioned drives in a RAID
