I got no response on this and want to take a shot before going the
backup way.
Assuming (hda1 and hdb1 in raid1 md0) Will the following work?
1. Fail and remove hdb1
2. Create new RAID1 md1 with hdb1 and missing
3. dd md0 onto md1
4. Make both bootable. (I suppose I need to change UUID of md1
partitions. I suppose that is easy)
5. Boot both and double check
6. Now upgrade md0 without fear.
7. Boot and test the new system for a couple of days to make sure
everything is fine.
8. If that fails, delete md0, and add hda1 to md1. If not delete md1
and add hdb1 to md0
Regards
Ramesh
On 1/30/20 1:27 AM, Wols Lists wrote:
On 30/01/20 06:30, Reindl Harald wrote:
Thanks. I thought of this, but both disk in question are nvme ssd with
manually added heat sink. It will be a hassle to remove and reinstall. I
think I will go with the back up rather than remove disk physically.
why would you remove it phyiscally to remove it rom the array? seriously?
Because if you physically remove it, BOTH disks will think they are the
surviving copy. You could "assemble" either disk on its own and recover
the array.
But if you remove a disk with --fail --remove, does that tamper with the
superblock? Would that prevent that disk being re-assembled on its own?
Seriously. I don't know. And were I in the OP's shoes I would be asking
the same question.
This is where you want something COW in the stack. Lvm. Btrfs. Where you
can just take a snapshot, upgrade the system, and if it all goes
pear-shaped you throw the snapshot away.
Cheers,
Wol
