changes UUID to non-existent on kernel upgrade 2.6.31-17

Bug #504336 reported by keepitsimpleengr
8
This bug affects 1 person
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://mirrors.us.kernel.org karmic-updates/main Packages
        100 /var/lib/dpkg/status
     1:0.126.6 0
        500 cdrom://Ubuntu 9.10 _Karmic Koala_ - Release amd64 (20091027) karmic/main Packages
        500 http://mirrors.us.kernel.org karmic/main Packages
--
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-cd06-4982-a4e0-1db8f3fc4a26 could not be found
--
There is no disk with UUID=3ad2f993-cd06-4982-a4e0-1db8f3fc4a26 on system
The correct UUID is 6a98b6c0-9ccf-477b-b197-d73c4162f581 for the disk with the root on it.

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :
Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :
Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :
Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

Commit Log for Thu Jan 7 07:55:11 2010

Upgraded the following packages:
google-chrome-unstable (4.0.266.0-r33992) to 4.0.288.1-r35555
linux-generic (2.6.31.16.29) to 2.6.31.17.30
linux-headers-generic (2.6.31.16.29) to 2.6.31.17.30
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:
linux-headers-2.6.31-17 (2.6.31-17.54)
linux-headers-2.6.31-17-generic (2.6.31-17.54)
linux-image-2.6.31-17-generic (2.6.31-17.54)

Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

$ blkid
/dev/sda1: UUID="30D8EF5AD8EF1CBA" LABEL="C_WINXP" TYPE="ntfs"
/dev/sda2: UUID="502E5E672E5E45DE" LABEL="KISE-005.250GB.P2.NTFS" TYPE="ntfs"
/dev/sdb1: LABEL="150.1.P1.UB.EXT3" UUID="6a98b6c0-9ccf-477b-b197-d73c4162f581" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb2: LABEL="WIN-SWAP" UUID="045D-3460" TYPE="vfat"
/dev/sdc1: UUID="D602FFF702FFDB07" LABEL="C_VISTA" TYPE="ntfs"
/dev/sdc2: UUID="7458404f-4c17-4edd-aef1-e4a4d34215d0" TYPE="swap"
/dev/sdd1: TYPE="swap"
/dev/sdd2: LABEL="500.1.P1.TEST" UUID="ed06315c-ea99-cae4-8921-45c95943258f" SEC_TYPE="ext2" TYPE="ext3"
/dev/sde1: TYPE="swap"
/dev/sde2: LABEL="LINUX_SCRATCH" UUID="0c7b55ec-65b9-e162-e045-c84ed9dd0a15" TYPE="ext2"
/dev/sdf1: LABEL="WIN_SWAP_2" UUID="C3BD-D2D8" TYPE="vfat"
/dev/sdf2: UUID="6A5CE632D344ED0E" LABEL="WIN_SCRATCH" TYPE="ntfs"

affects: update-manager (Ubuntu) → apt (Ubuntu)
affects: apt (Ubuntu) → update-manager-core (Ubuntu)
Revision history for this message
keepitsimpleengr (keepitsimpleengineer) wrote :

Workaround:
1] Boot from CD; ubuntu live, knoppix ⋯, or similar.
2] Open terminal, logon as superuser
3] Verify UUID with blkid command
4] Mount partition with /boot
5] Edit /boot/grub/menu.lst replacing specious UUID with correct UUID
6] Shutdown and remove boot CD
6] Reboot system

Revision history for this message
Sam_ (and-sam) wrote :
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

Sorry that the issue got unattended at the time of report. Please feel free to reopen by marking the status as "new" if you see this in current versions of update-manager.

Changed in update-manager-core (Ubuntu):
status: New → Incomplete
affects: update-manager-core (Ubuntu) → update-manager (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in update-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.