Using the "skip=" option on dd does not help. It seems to take just as
much time as writing zeros to the whole disk. It must skip by reading
them, as opposed to issueing an appropriate command to the device.
Instead I have started using the rev 1.2 SuperBlock for mdadm. This
places the superblo
** Changed in: debian-installer (Ubuntu)
Status: New => Confirmed
--
re-install with md(raid) in same place uses old raid data
https://bugs.launchpad.net/bugs/137171
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Maybe a simple
mdadm --zero-superblocks /dev/md
could be inserted in the installer to solve the problem?
--
re-install with md(raid) in same place uses old raid data
https://bugs.launchpad.net/bugs/137171
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Solved, obviously, with a simple dd to both disks. I haven't yet tried to erase
all the superblocks instead on dd all the disk (it should run).
I think the installer, at the time to erase the partition table of a disk,
should also erase all the superblocks in which linux holds the metadevice inf
Same thing happens in the Hardy alternate install disk.
--
re-install with md(raid) in same place uses old raid data
https://bugs.launchpad.net/bugs/137171
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
I completely agree with you.. 've been wondering about that for a while
now...and i *really* hope someone can fix this.
--
re-install with md(raid) in same place uses old raid data
https://bugs.launchpad.net/bugs/137171
You received this bug notification because you are a member of Ubuntu
Bugs, w
