bugGNU GRUB - Bugs: bug #31964, Configuration error produced when...


You are not allowed to post comments on this tracker with your current authentication level.

bug #31964: Configuration error produced when running "sudo grub-mkconfig -o /boot/grub/grub.cfg"

Submitted by:  Frank Golden <fjgold>
Submitted on:  Fri 24 Dec 2010 12:26:59 AM UTC
Category:  Configuration Severity:  Major
Priority:  5 - Normal Item Group:  None
Status:  Invalid Privacy:  Public
Assigned to:  None Originator Name:  Frank Golden
Open/Closed:  Closed Release: 
Release:  * 1.98 Reproducibility:  Every Time
Planned Release:  None
* Mandatory Fields

Add a New Comment (Rich Markup)

Comment Type & Canned Response:


Sat 25 Dec 2010 12:51:05 PM UTC, comment #1: 

initrd line is taken from linux-boot-prober which already removes (..) from kernel line but doesn't do the same for initrd line. So I suggest contacting debian-boot folks who maintain linux-boot-prober.

Vladimir Serbinenko <phcoder>
Project Administrator
Fri 24 Dec 2010 12:26:59 AM UTC, original submission:  

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

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.

Frank Golden <fjgold>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by phcoder (Posted a comment)
  • -email is unavailable- added by fjgold (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.





    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-12-25 phcoder StatusNone => Invalid
        Open/ClosedOpen => Closed

    Back to the top

    Powered by Savane 3.9