[Bug 234720] Re: wrong UUID in menu.lst after upgrade to hardy
Hi Marcel, Yes, you are correct; if after a kernel upgrade in hardy you have the wrong UUID in your boot config, then two things must be true here: - the wrong UUID is present in the kopt line in menu.lst - the user must have overidden the default choice when prompted during the upgrade, and chosen to use the config autogenerated by the system instead of the one preserving the local changes to the boot options As you noted, both of these applied in your case, and I believe this also applies in the case of the original submitter. Ideally, it would be great if we could magically detect when the wrong UUID is used and automatically fix everything up, but that's simply not feasible here; so I'm closing this bug as 'wontfix'. ** Changed in: grub (Ubuntu) Status: New => Won't Fix -- wrong UUID in menu.lst after upgrade to hardy https://bugs.launchpad.net/bugs/234720 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
[Bug 234720] Re: wrong UUID in menu.lst after upgrade to hardy
I had the problem re-occur with todays upgrade to 2.4.16.18. despite the fact /etc/blkid.tab had the correct entries. This led me to investigate the matter in more detail. I think I SOLVED it as a non-bug. Here is what I found I noticed that the "kopt" and "groot" options in my /boot/grub/menu.lst still had the invalid "hd" and "UUID" options. (The fact that a "#" appears at the beginning does not mean that these are commented out. Apparently you need a "##" for comments) relevant diff: < # kopt=root=UUID=11364fdf-db87-4d3c-a385-0d710cba8a8f ro //correct --- > # kopt=root=UUID=824f1f6c-3d18-4cac-84b3-12d3a5867e4c ro // incorrect 74c74 < # groot=(hd0,0) //correct --- > # groot=(hd0,7) // incorrect Simply deleting menu.lst and running update-grub will generate a new menu.lst with the correct "kopt" and "groot" options. Please note that you probably will want to edit the new menu.lst. An pre-existing menu.lst with the INCORRECT kopt and kgroot options will trigger the reported problems. and a menu.lst with CORRECT options behaves as expected. In my case, I should have modified/deleted menu.lst after transferring the system from one HD to the other. I therefore think this is NOT A BUG and suggest closing this bug report. -- wrong UUID in menu.lst after upgrade to hardy https://bugs.launchpad.net/bugs/234720 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
[Bug 234720] Re: wrong UUID in menu.lst after upgrade to hardy
I had the same problem with an additional twist. My /etc/blkid.tab also contained the old UUID's so I either a) deleted it and it got regenerated, or b) edited it to contain correct ones (don't actually remember). But it is not important, important is that I now just updated to 2.6.24-18 and installed package maintainers menu.lst and there are still wrong UUID's there. I don't know from where does it get those.. they are nowhere to be found in /etc any more so it is a mystery to me. Hm.. and I also migrated 7.10 to a new disk without reinstalling and then upgraded to 8.04 before all this happened. -- wrong UUID in menu.lst after upgrade to hardy https://bugs.launchpad.net/bugs/234720 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
