Apologies for this: I assumed mdadm has this problem too, but that's a mistake. mdadm can handle hdd's when they have identical WWN's. The message "device or resource busy" is caused by something else.
So it's clearly a subiquity bug.
Apologies for this:
I assumed mdadm has this problem too, but that's a mistake.
mdadm can handle hdd's when they have identical WWN's.
The message "device or resource busy" is caused by something else.
So it's clearly a subiquity bug.