On 21/11/17 19:13, Lew Wolfgang wrote:
On 11/21/2017 09:19 AM, Per Jessen wrote:
Sorry, I don't think I made myself clear. If the old disk was swapped out and copied, then the old disk is "clean". If this disk gets back into the same machine as the raid array, and the machine is rebooted, mdadm IS GOING TO GET CONFUSED. Yes, but Andrei is using an HP Smart Array Controller, not software raid.
I've also been bitten by hidden RAID metadata on individual disks. I've been using a very simple/dumb script to make sure all the metadata is gone. It blasts the MBR, partition table, and any other cruft at the start of the disk too. Call with the /dev/sdx as the argument. Use at your own risk!
#!/bin/bash dd if=/dev/zero of=$1 bs=512 count=2018 dd if=/dev/zero of=$1 bs=512 seek=$(( $(blockdev --getsz $1) - 1024 )) count=1024 exit
Does the second line wipe the END of the disk? Note that your backup GPT is located at the end of the disk, and a v0.9 or v1.0 raid superblock is also located at the end of the partition/disk. Not knowing where everything is stored, that's why my preference is simply to wipe the entire disk. Snag, of course, is that it takes a LLOOOONNGGG time on today's huge disks.
BTW, I've also seen software raid (mdadm) get confused by disks out of a hardware raid controller.
What's the betting the firmware in said contoller is a cut-down linux/mdadm combo? :-)
Regards, Lew
"When in doubt, zero it out!"
Spot on! Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org