On Fri, 13 Apr 2012, mwesten wrote:
Alright, I looked at the pics you posted and it appears that you have
reproduced this anaconda crash during the bootloader installation:
https://bugzilla.redhat.com/show_bug.cgi?id=796472
I was looking at the included exception report and it seems this person
was installing F16 on the second of two drives with the bootloader going
on the first.
Is that what you were doing as well?
Yes.
So I tried again.
I use grub's setup to put the bootloader on sdb and point it at sdb1.
I updated BIOS settings to use sdb.
Again anaconda labeled sdb partitons storage and sda partitions install.
It had sda marked for the bootloader.
It offered me the choice of sda or sdb19 for the bootloader.
I picked sdb19.
It choked the same way again.
The next time, I made /boot sda2 and picked sda for the bootloader.
This time I got an install, but I'm not sure how to boot to it.
I'd rather not have to play with the BIOS
every time I want to boot a different install.
Is there a way to chainload to sda?
I'd have tried configfile,
but I don't think that works from old grub to grub2.
The grub2 directory has nearly 200 files in it.
Wow.
Also, I truly hate UUIDs.
For desktop systems, they are large, unintelligible overkill.
Labels are quite sufficient.
--
Michael hennebry@xxxxxxxxxxxxxxxxxxxxx
"On Monday, I'm gonna have to tell my kindergarten class,
whom I teach not to run with scissors,
that my fiance ran me through with a broadsword." -- Lily
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
