Grub doesn't boot. Partition confusion (solved)

Unintentional or not, your posting helped me to solve a problem i had with HP 6715b laptop. After adding "noapic nolapic" to grub i am finally able to boot with 64-Studio multimedia kernel. Great.

I had the same problem after clean install so i edited the menu before boot and changed root (hd0,1) to root (hd0,0) booted and edited my /boot/grub/menu.lst and changed all the lined in root (hd0,1) to root (hd0,0) and now its working great cheers!! www.wayneward.co.uk/blog/

Hi Pablo, I use Desktop pc's. This one is used for Testing. (nvidia FX 5200). googled:: lenny not using MMCONFIG :: 10 hits per page: ref: page 3 nvidia forum , page 6 debian forum. These are the results for 2.6.21-1-multimedia-486. "I don't have a lenny install". $ uname -r 2.6.21-1-multimedia-486 $ cat /boot/config-2.6.21-1-multimedia-486 > ~/Desktop/current_config.txt Creates a copy current_config.txt file on the desktop. $ cat ~/Desktop/current_config.txt | grep MMCONFIG # CONFIG_PCI_GOMMCONFIG is not set CONFIG_PCI_MMCONFIG=y $ cat ~/Desktop/current_config.txt | grep NVIDIA CONFIG_AGP_NVIDIA=m CONFIG_FB_NVIDIA=m CONFIG_FB_NVIDIA_I2C=y CONFIG_FB_NVIDIA_BACKLIGHT=y $ cat ~/Desktop/current_config.txt | grep FB_VESA CONFIG_FB_VESA=y $ cat ~/Desktop/current_config.txt | grep FB_NVIDIA CONFIG_FB_NVIDIA=m CONFIG_FB_NVIDIA_I2C=y CONFIG_FB_NVIDIA_BACKLIGHT=y $ cat ~/Desktop/current_config.txt | grep FB_RIVA # CONFIG_FB_RIVA is not set $ cat ~/Desktop/current_config.txt | grep X86_UP_APIC ### Xorg.0.log ### $ cat /var/log/Xorg.0.log | grep EE Current Operating System: 2.6.21-1-multimedia-486 (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (II) Loading extension MIT-SCREEN-SAVER $ cat /var/log/Xorg.0.log | grep WW (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) I am not going to start configuring my kernel. Just learning a bit more about my setup... Please don't mess with or break your system it it's working fine. The above workings are just me learning linux. In the not to distant future i'm going to get my first 64bit (64studio) computer built for me, something like this. http://eracks.com/products/Quiet%20Systems/config?sku=STUDIO Also my "first ever" laptop. Yours looks very nice! Asus P5B Motherboard... (Core 2 Duo/ Core Duo/ Pentium D/ Pentium 4/ Celeron, LGA775, P965, ATX, 8GB DDR2, 1066GHz FSB - MPN: P5B) Description: The P5B motherboard supports the most powerful and energy efficient Intel Core 2 processors. It features the Intel P965 chipset and supports DDR2 800MHz dual-channel memory architecture. With exclusive innovative tools AI NOS, AI Gear and AI Nap users can adjust operation speed according to their specific needs. The P5B is a cool and stable platform that delivers extreme performance, minimum noise and maximum power saving. Which one would you buy now? Any advice would be really appreciated. Thanks, dave http://kmuto.jp/debian/hcl/index.cgi

** Can you: Change your boot order in the bios so that the internal drive comes before the usb drive? ** Yes, I've disabled it in the BIOS. There was "external device" or similar as boot device number 1. I don't need it for the time being. ?? is it Asus P5B Motherboard? Yes, it is. When I first installed 64studio it was a nightmare. The GUI wouldn't start. I had a saphire X550 XTX graphics card. I tried a lot with the xorg.conf to no avail. I got a Nvidia GEforce 8400 GS. But the GUI wouldn't start either. I installed the propietary driver of nvidia and that's how I got it working. However, the lenny system has a 2.6.22 kernel, and when booting shows a message about a BIOS bug, and says it's not using MMCONFIG. 64studio (2.6.21-multimedia) doesn't say anything of the sort. Yes, I love live CD's. Thank you very much Dave. Pablo

Hi Pablo, Pablo> Maybe someone can explain why these kind of things come about. Never seen grub jump x2 but grub gets crazy sometimes. Probably wrong but here goes. hda hdb sda title 64studio,sda1 root (hd0,0) kernel /boot/vmlinuz-2.6.21-1-multimedia-486 root=/dev/sda1 ro vga=791 splash=silent noapic nolapic acpi=off initrd /boot/initrd title Lenny,sda4, root (hd0,4) kernel /boot/vmlinuz initrd /boot/initrd Pablo> Yesterday my housemate plugged an usb stick prior to boot. It didn't boot and I told her to remove the stick >>>>>> But then grub gave errors and failed to boot. title 64studio,sda1 root (hd2,0) kernel /boot/vmlinuz-2.6.21-1-multimedia-486 root=/dev/sda1 ro vga=791 splash=silent noapic nolapic acpi=off initrd /boot/initrd title Lenny,sda4, root (hd2,4) kernel /boot/vmlinuz initrd /boot/initrd example# fdisk -l Device Boot Start End Blocks Id System /dev/hda1 * 1 1218 9783553+ 7 HPFS/NTFS /dev/hda2 1219 1828 4899825 83 Linux /dev/hda3 1829 4865 24394702+ 5 Extended /dev/hda5 2986 3002 136521 82 Linux swap / Solaris /dev/hda6 3003 4164 9333733+ b W95 FAT32 /dev/hda7 4165 4865 5630751 83 Linux /dev/hda8 1829 2985 9293539+ 83 Linux Pablo# fdisk -l When the USB external hard drive is plugged in "hd0" becomes "hd1" and hd1 becomes hd2. That 'could' have screwed Grub! your three disks could have made it worse! You are "not" using UUID's in your /etc/fstab and grub's /boot/grub/menu.lst. ubuntu grub gets screwed by this. ** Can you: Change your boot order in the bios so that the internal drive comes before the usb drive? ** ?? was it one of these? Error 17 after boot menu "Error 17: Cannot mount selected partition" most probably, your device order has changed. For example, if you installed linux from CD and your IDE harddisk was device 0, it may now be device 1 after Booting from USB. In this case change root (hd1,1) to root (hd0,1) Please note that 1 is simply an example for a partition, it may also be any other number. Error 17 before boot menu "Error 17" most probably, your device order has changed and grub searches its menu (stage) on the wrong disk. You will have to do grub-install again. Waiting for /dev/sda to appear * After selecting the boot entry in the grub menu, you get some lines of messages then the boot process stops with the message Waiting for /dev/sda to appear your USB disk is recognized and supported by your BIOS, but your initrd's drivers do not recognize it. You will have to edit your initial ramdisk to contain the correct drivers, as discussed under initrd. Pablo> I think my mobo is very crappy. I've got a P5B. ?? is it Asus P5B Motherboard? Pablo> This is not very normal, is it? grub can sometimes get crazy. you gotta luv livecd's. Cheers, dave