Lionel Le Folgoc wrote: >> because all grub entries are 'patched' to point to (hd0,0) and >> > /dev/hda1 > > Did you replace manually all occurences of hd(0,0), or did you change > the commented value (such as groot=, kopt=), and then run 'sudo update- > grub' ? > > Thank you for your hints.
I'm using linux from 1993 but normally I'm using RedHat like distros. We have choose Ubuntu, because it is easier to use for unexperienced users, and generally hassle free. There are, of course, some differences between Debian / Fedora system files structure and tools. For Example on Fedora Core 1 there is no update-grub tool nor groot or kopt entries in menu.lst. My customers have systems with Ubuntu up and running for couple of month and there was kernel updates in past, that doesn't trigger this behavior. Anyway, when customer machine was blocked because of wrong grub entries, I have replaced manually all occurrences of hd(0,0) with hd(0,1) and all occurrences of /dev/hda1 with /dev/sda2. Needless to say, it lasts only 2 days till next kernel update and machine reboot ... I will check, groot or kopt values in menu.lst file and try update-grub to see, what happen and let you know. > If you installed ubuntu on the first partition, and then you moved it, > and edited manually hd(0,0), that is not a bug, this part is overriden > at each call of 'sudo update-grub'. > > -- Jan Vachun Spintec s.r.l. C.so Torino 89/A Ferriera di Buttigliera Alta (TO), 10090 tel: +39 011 9348228 fax: +39 011 9348861 -- GRUB's menu.lst modified in wrong way -> Error 15 File not found on next reboot https://launchpad.net/bugs/61108 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
