changes UUID to non-existent on kernel upgrade 2.6.31-17
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: update-manager
# lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10
amd64
# apt-cache policy update-manager
update-manager:
Installed: 1:0.126.9
Candidate: 1:0.126.9
Version table:
*** 1:0.126.9 0
500 http://
100 /var/lib/
1:0.126.6 0
500 cdrom://Ubuntu 9.10 _Karmic Koala_ - Release amd64 (20091027) karmic/main Packages
500 http://
--
Expected:
Updated using update-manager (see below)
Selected the option to write the maintainer's menu.lst version.
Ubuntu to boot normally with new kernel
--
Actual:
Updated using update-manager (see below)
Rebooted, ununtu failed to boot, reported disk with UUID=3ad2f993-
--
There is no disk with UUID=3ad2f993-
The correct UUID is 6a98b6c0-
affects: | update-manager (Ubuntu) → apt (Ubuntu) |
affects: | apt (Ubuntu) → update-manager-core (Ubuntu) |
Commit Log for Thu Jan 7 07:55:11 2010
Upgraded the following packages: chrome- unstable (4.0.266.0-r33992) to 4.0.288.1-r35555 generic (2.6.31.16.29) to 2.6.31.17.30
google-
linux-generic (2.6.31.16.29) to 2.6.31.17.30
linux-headers-
linux-image-generic (2.6.31.16.29) to 2.6.31.17.30
linux-libc-dev (2.6.31-16.53) to 2.6.31-17.54
Installed the following packages: 2.6.31- 17 (2.6.31-17.54) 2.6.31- 17-generic (2.6.31-17.54) 2.6.31- 17-generic (2.6.31-17.54)
linux-headers-
linux-headers-
linux-image-