On 08/26/2012 08:07 PM, sean darcy wrote:
On 08/26/2012 05:55 PM, sean darcy wrote:
On 08/26/2012 04:45 PM, Heinz Diehl wrote:
On 26.08.2012, sean darcy wrote:
[liveuser@localhost ~]$ blkid /dev/sda2
/dev/sda2: LABEL="root" UUID="89afb6ff-4fb2-4602-94b5-99dbf022b100"
TYPE="ext4"
I can't find something wrong in your grub.cfg. What do you see when
you try to boot, are there any errors / is there any related output on
the screen when it fails?
Have you looked into device.map, if your devices are listed correct?
If you want to boot from absolute device, write "root=/dev/sda2" into
your grub.cfg.
If this is not working either and nobody has a clue what's going on, I
would try to reinstall grub2 via grub2-install, after booting from an
external media. You can avoid chrooting by using the --root-device
parameter. Mount your root-partition on /mnt:
grub2-install --root-directory=/mnt /dev/sda
I'm not quite shure it is a problem with dracut, but without any
further information it will be impossible to be more precise.
Trying to do grub2-install from the F17 Live CD. I think I need to mount
both / and /boot. Then I'd use --boot-directory to point to /boot. But
I'm puzzled about how to specify /root. --root-directory is now
deprecated in favor of --efi-directory. But that's specific for UEFI,
whatever that is.
sean
Used the net.iso disk to chroot into the install. Then tried
grub2-install. That completed successfully. Then rebooted. Same problem.
Really odd.
Do I replace the uuid with /dev/sda2 everyplace it appears in grub.cfg?
sean
Can you boot from an older kernel?
If yes, then
yum -y re-install kernel-....... (i.e. the one you are unable to boot up).
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
