Andrea Righi wrote: > wtautz wrote: > >> The answer is /boot/grub/menu.lst is not update corrected by update-grub >> if menu.1st has a line of the form: >> IF # kopt=root=UUID=d401f1eb-681d-41f8-bf63-62d8da629044 ro >> >> In my case the UUID was from the golden client which is different from >> the client I installed >> to. Only after I edited the line to say root=/dev/hda6 and rerun >> update-grub did the >> correct UUID get substituted. Of course this behaviour is incorrect >> since humans are >> suppose to edit this line and not have it be overwritten (and this seems >> to hold depending >> one what one puts in the line). I guess I'll report this as a bug. >> > > Which filesystem are you using on /dev/hda6? AFAIK the UUIDs should work fine > with systemimager 3.8.2 (but I suppose only for ext2/ext3)... >
Andrea, The problem isn't with UUID. It's a problem with the update-grub program that comes from debian. Basically there is a line in '/boot/grum/menu.1st that # kopt=root=UUID=xxxxxxxx ro which apparently does NOT get updated when update-grub runs. I fixed the goldenclient and now I have no problems getting the other client to boot, i.e., Systemimager works. Here is the bug report in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/62195 Walter ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
