linux guy wrote:
I can't say for certain about the USB method, I just burn it to a CD, and after I am done with the CD I put it into a tool kit/cd wallet I use so I haven't tried that option. It should boot to a menu system with the fix action options there, since you are getting just the grub prompt I would venture a guess the USB key is wrongI downloaded the supergrub iso and installed it onto my usb drive. When I boot from it, it gives me the grub> command line. Is that a sign I don't have the USB installation right or is that the tool that I am supposed to use to fix my non booting drive ? Thanks On 7/16/09, linux guy <linuxguy123@xxxxxxxxx> wrote:Here is my grub file. The boot partition is /dev/sda1. That should be hd0,0, right ? The root partition is sda2. That should be hd0,1, right ? Does anyone see anything wrong with my grub setup ? I don't understand how installing an f12 kernel and then uninstalling it could still result in a machine that won't boot. Does f12 assume an ext4 filesystem or something ? df thinks my file systems are all ext3. Thanks default=0 timeout=15 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.29.5-191.fc11.i586) root (hd0,0) kernel /vmlinuz-2.6.29.5-191.fc11.i586 ro root=UUID=f543d554-9344-4cad-a7da-47de47cd2665 rhgb quiet initrd /initrd-2.6.29.5-191.fc11.i586.img title Fedora (2.6.29.4-167.fc11.i586) root (hd0,0) kernel /vmlinuz-2.6.29.4-167.fc11.i586 ro root=UUID=f543d554-9344-4cad-a7da-47de47cd2665 rhgb quiet initrd /initrd-2.6.29.4-167.fc11.i586.img On 7/16/09, Rich Mahn <rich@xxxxxxx> wrote:I did that, twice, first off, before I ever posted to the group. The f12 kernel installed to default 0 and then I had 2 f11 2.6.29 kernels in positions 1 and 2. I changed the default to both of them and neither would boot.I have had this problem often when I've been moving disks around or when I am testing out new operating systems. It has always been one of two things: 1. the BIOS has reordered disks and you aren't booting from the disk you want, or 2. (similar to above), the disk identified in grub is the wrong one and needs to be dhanged. Where you see something like root (hd0,0), you may need to change it to root(hd1,0). This can sometimes be caused by a USB device being present (or not). If you loaded your OS with a USB drive, it may have shifted all the hd's when creating the grub.conf file. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
~Seann
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
