Hi Steve, - I manually change root instead of UUID Because 1) UUID was set for wrong partition (first partition with linux instead of right one) 2) boot partition UUID was right but it refused to buut with UUID set.
- I don`t know. Installer takes first ubuntu installed partition if finds and points all menu.lst options to that partition. why? I don`t know. To my experience on every kernel update, UUID is changed and reseted. (So since I need manually to ovveride it every time after update ,so that I can boot to my system, It is updated every time. As I said, I always set to /dev/* device after kernel update so I can even boot. Maybe I shoud keep it set to UUID but I would`n change to /dev/* in the first place if on first update, it would`n set UUID for all menu items to first partition it finds, e.g. /dev/sda2, where i always have newer system i suppose to be testing. I think that main bug here is that after recent update, I cannot start X at all with 2.6.24-23 , with same menu.lst settings I can boot to 2.6.24-22. There is no way for me to avoid to have wrong menu.lst on every Hardy kernel update if I have one more Ubuntu/Linux installed beside Hardy. Hardy updates sets all menu.lst items to UUID of the first installed partition and not required ones. So I do backups every time, and repair all items on menu.lst every time kernel updates, so I can even boot. -- Failed boot after update [hardy] amd64 -2.6.24-23 , fglrx https://bugs.launchpad.net/bugs/315338 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
