DANGER!!! Problems with 10.04 installer (RAID devices *will* get corrupted)
clifford_ilkay at dinamis.com
Fri Apr 23 17:37:21 UTC 2010
On 04/23/2010 01:35 PM, Nikolai K. Bochev wrote:
> ----- Original Message -----
>>> I've been following this thread and I think I'm the only person
>>> who made a reference to Fedora. What I experienced in Fedora was
>>> NOT a problem. I think it was prudent behaviour. In short, I
>>> could not do a kickstart installation and tell the installer to
>>> remove all partitions if a drive had previously been part of a
>>> RAID set. I tried to find a reference to this in the Fedora
>>> mailing lists but ended up finding something else that was
>>> similar to the original poster's problem. See:
>>> <<https://bugzilla.redhat.com/show_bug.cgi?id=543749> in the Red
>>> Hat bug tracker. That looks like a udev problem and someone
>>> posted a workaround.
>>> If Slackware also uses udev and this is a udev problem,
>>> Slackware would also be similarly affected while "doing something
>>> this simple".
> In most cases mdadm --zero-superblock solves that ( being unable to
> get rid of a previous raid setup for the disks ).
Which is exactly what I did. What I was pointing out was that Fedora's
behaviour is *good*. In a hands-off scripted installation, like with
kickstart, you don't get the chance to confirm your choices so it would
be all too easy to destroy data. That it just ignores the "clear all
partitions" directive in kickstart on devices with a RAID superblock
1419-3266 Yonge St.
Canada M4N 3P6
More information about the ubuntu-users