Re: [fedora-list] How do a fix a non working kernel installation ?
> 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@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [fedora-list] How do a fix a non working kernel installation ?
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 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@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [fedora-list] How do a fix a non working kernel installation ?
I 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 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 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@redhat.com >> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list >> Guidelines: >> http://fedoraproject.org/wiki/Communicate/MailingListGuidelines >> > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [fedora-list] How do a fix a non working kernel installation ?
linux guy wrote: I 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 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 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@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines 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 wrong ~Seann smime.p7s Description: S/MIME Cryptographic Signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [fedora-list] How do a fix a non working kernel installation ?
On Thu, Jul 16, 2009 at 14:58:00 -0400, linux guy wrote: > > 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 I also like to comment out hiddenmenu, and take rhgb and quiet off the kernel lines so that I have a chance to notice odd things during the boot process. But what you have should work. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [fedora-list] How do a fix a non working kernel installation ?
On Thu, Jul 16, 2009 at 14:59:58 -0400, linux guy wrote: > I 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 ? If you got there you probably could have booted from that grub instance by setting the correct initrd and kernel settings before giving a boot command. If the hard drives were named correctly, but the grub install on the mbr was hosed, the configfile command might be easier. Grub has built in minimal help. You can use tab to see what the options are for commands or parameters. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [fedora-list] How do a fix a non working kernel installation ?
> I 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 ? I dont know supergrub but my advice is to restore grub to your mbr of your internal hdisk presumably that is where you had it originally, not on mbr of usb. preferably with your usb turned off, from a live cd with grub on it, knoppix eg: grub> root (hd0,0) setup (hd0) quit that should do it Jack -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: [fedora-list] How do a fix a non working kernel installation ?
--- On Thu, 7/16/09, linux guy 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 ? > Check your /boot/grub/device.map file, grub-install will change it. Make sure that it matches grub.conf and /etc/fstab. I have had to change mine several times after removing/adding drives. [m...@localhost ~]$ cat /boot/grub/device.map # this device map was generated by anaconda (hd0) /dev/sda (hd1) /dev/sdb Mick M. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
