© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Attached is my menu.lst file. Here is what I did:
1. I installed a new disk in my computer alongside my old disk.
2. I partitioned the new disk and formatted the partitions.
3. I mounted the new disk's partitions and copied files into them.
4. I edited the fstab on the new disk's root partition so that the UUIDs as reported by vol_id were correct.
5. I edited the menu.lst on the new disk to use the new disk's UUIDs.
6. I edited device.map, ran grub-install, and then restored device.map (since grub won't install on the new disk otherwise).
7. I then powered off, removed my old disk and made my new disk the primary disk.
After doing all this, I booted and was able to work normally until a kernel upgrade came along a few days later. I had powered off and on several times during this period.
The structure of my menu.lst file has remained the same throughout the switch from my old disk to my new disk, as far as I am aware, but I obviously changed the UUIDs as described above. I don't understand why the kernel upgrade overwrote menu.lst with old UUIDs which were no longer in the file.
It's possible I did something wrong. If so, the right way of doing an upgrade like this should be documented. I used the "how to" document here (using discretion and prior experience where LILO was mentioned instead of grub):
http://