Am Mittwoch, den 11.11.2009, 03:06 +0000 schrieb Steve Langasek: > 3) Karmic 64 emergency system (a cp -a of my system on a different partition) > > > For a reason I can't understand, the menuentry 3) is : > > search --no-floppy --fs-uuid --set > 20592abf-12bf-4a78-a11b-e3af3bf1b29f (CORRECT UUID) > linux /boot/vmlinuz-2.6.31-14-generic > root=UUID=69f429f9-dc0a-4422-af1f-8eb4796e0294 ro single (INCORRECT UUID, > UUID OF OS 1) > initrd /boot/initrd.img-2.6.31-14-generic
What does sudo os-prober and then sudo linux-boot-prober /dev/sda1 tell? Replace sda1 with the device which os-prober tells you for your rescue Karmic. os-prober gets the root= kernel option out of the bootloader config (i.e. lilo.conf/menu.lst/grub.cfg) from the other system. So please check that your rescue karmic bootloader configuration has the right root= value set. > As far a I can't manually edit grub.cfg, I can't correct the menuentry, and > can't add "set quiet=1"; > > The grub2 system is definitely too rigid and window$ style (plug & pray) > > I tried to chattr -i /boot/grub/grub.cfg but no results We don't set immutable flag, but use normal chmod to make the file readonly. If you use an editor which can't overwrite this then use chmod +w grub.cfg But note the warning at the top. You can disable os-prober with GRUB_DISABLE_OS_PROBER=true in /etc/default/grub and then place the menu entries just like you want to have them written as inside /etc/grub.d/40_custom and then run sudo update-grub -- Felix Zielcke Proud Debian Maintainer and GNU GRUB developer -- update-grub doesn't write a correct grub.cfg in Karmic https://bugs.launchpad.net/bugs/479962 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
