On 19/03/2022 04:10, Marc MERLIN wrote:
If you find it needs more than the size of sdk1, as an emergency measure you
could wipe off the partition table and add the entire sdk as the array member.
Yeah, I thought of that, just don't really like it, and not sure if
mdadm -can looks for raw drives in addition to partitions
mdadm has absolutely no trouble with that at all. All it cares about is
if something is a block device - if it finds an mdadm signature at the
start of a block device it will use it.
The problem is the eejits out there who assume that all physical drives
must be partitioned. And we know from experience that there are eejits
out there who assume that any drive without an MBR or GPT just *must* be
unused and it's *perfectly* *okay* to write said MBR or GPT *without*
*asking*. Just trashing your mdadm (or lvm, or whatever yada ydad)
signature in the process.
It's not common, but we do get calls to recover arrays where the
signature has gone missing because the owner made the mistake of
upgrading their system (Windows, linux, whatever) and the upgrade
stomped all over the array.
Cheers,
Wol
