bug-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #31964] Configuration error produced when running "sudo grub-mkconf


From: Frank Golden
Subject: [bug #31964] Configuration error produced when running "sudo grub-mkconfig -o /boot/grub/grub.cfg"
Date: Fri, 24 Dec 2010 00:26:59 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 GTB7.1

URL:
  <http://savannah.gnu.org/bugs/?31964>

                 Summary: Configuration error produced when running "sudo
grub-mkconfig -o /boot/grub/grub.cfg"
                 Project: GNU GRUB
            Submitted by: fjgold
            Submitted on: Fri 24 Dec 2010 12:26:59 AM GMT
                Category: Configuration
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Frank Golden
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: 1.98
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

I'm running GRUB2 on Ultimate Edition 2.8.
I recently installed Mandriva on a spare partition of my hard drive.

This is an ACER Aspire 5672 notebook with 500 GB HDD.

I installed Mandriva on sda8 and installed grub on the sda8 partition because
my intent was to run 

sudo grub-mkconfig -o /boot/grub/grub.cfg

in Ultimate Edition 2.8 to boot Mandriva from GRUB2 within Ultimate
Edition.

Running the command updated grub.conf to reflect the Mandriva install but
there is an error in the entry that causes a kernel panic when trying to boot
Mandriva.

If you look at the snippet of the file below you can clearly see the error.

menuentry "linux (on /dev/sda8)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos8)'
search --no-floppy --fs-uuid --set f35b3b6e-5afd-4cdf-a453-4022690fecaf
linux /boot/vmlinuz BOOT_IMAGE=linux
root=UUID=f35b3b6e-5afd-4cdf-a453-4022690fecaf
resume=UUID=17dce95a-3e0a-4a41-a41d-ff2dfbe373a6 splash=silent vga=788
initrd (hd0,7)/boot/initrd.img
}

The last line entry should be initrd (hd0,8)/boot/initrd.img
and not the pictured initrd (hd0,7)/boot/initrd.img.

This of course causes the following kernel panic error message.

Kernel Panic -Not syncing : VFS: Unable to mount root fs on unknown-block
(0,0)

Boot stops there.

I could not find any info on how to correct this error but I manually edited
the grub.conf file to correct this discrepancy.

This "fixed" the problem.

This is of course a workaround because updating GRUB2 from the repos in
Ultimate Edition or preforming a kernel update will
update grub, reproducing the error.

If anyone here knows of  method to repair the grub.conf file permanently I
would be grateful.

This issue also exists for PCLinuxOS.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?31964>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]