anaconda-11.1.0.60-1.i386.rpme: I have a RHEL 4 install currently: /dev/hda1 /boot ext3 /dev/hda2 / ext3 <large chunk of free space> I choose 'custom'. I create a new 2G primary partition /dev/hda3 for '/', format as ext3. I choose /dev/hda1 as /boot, choose 'do not format'. When it comes time to format filesystems, I get: "An error occured trying to format /dev/hda3". If I look at the drive, /dev/hda3 was never added to the partition table.
Any kernel messages about being unable to write it? nothing here has really changed...
Nope. From a brief look over tty2-4, it almost appears that it didn't even try. What steps is it supposed to write?
The partition table should get saved in the turnOnFilesystems step -- the only reason it wouldn't is if parted failed to write it out for some reason (or the kernel failed to notice the write)
tty3 is... moving (1) to step confirminstall moving (1) to step install moving (1) to step enablefilesystems formatting / as ext3 Format command: ['/usr/sbin/mke2fs', '/tmp/hda3', '-i', '4096', '-j' ] tty5 is... mke2fs: No such device or address while trying to determine filesystem size There is a lockdep warning about anaconda attempting to acquire (&bdev->bd_mutex) while already holding the lock. No other useful information, really.
I blame the kernel ;-) What are you doing using regular IDE anyway? :P
Because the other testbox is ahci/ata_piix, which works even worse at the moment? :P
Actually, after more investigation, this is Peter's fault ;-) The mpath startup code was calling into refreshDevices which then resets everything to its "on-disk" state. I've stopped it from doing that for now which hopefully won't break mpath/dmraid