[Bug 377006] Re: Invalid root UUID during server upgrade from 8.10 -> 9.04

[Launchpad Bug Tracker]

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

** Changed in: update-manager (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/377006

Title:
  Invalid root UUID during server upgrade from 8.10 -> 9.04

Status in “update-manager” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: update-manager-core

  Culprit package: update-manager-core
  Culprit command: do-release-upgrade
  Breaks package: grub
  Impact: System not bootable / complete system failure upon reboot

  Summary:
  When performing the upgrade from Ubuntu Server 8.10 to 9.04 the generated menu.lst is invalid with regards to the root UUID kernel parameter.

  Context:
  My system is an Intel Mac Mini with an internal SATA disk and an external USB disk connected.
  I've got the three traditional partitions boot (ext3), root (ext3) and swap on the internal disk and one ext3 partition wrapped in a volume group on the external USB drive.

  My device to UUID mapping looks like the following before and after
  the upgrade

  UUID = ff929bbd-ec9b-4afc-b64a-0839fcb67be6    (sda1 => /boot)
  UUID = 9d9559fe-75e8-49ab-a684-5744d77984a4 (sda2 => /)
  UUID = 92cf9ba6-edcb-4f10-b017-6b5e7f9111ff     (sda3 => swap)

  Problem:
  During the execution of do-release-upgrade the value for the root property in the menu.lst entries get assigned the UUID value d476b48f-bb64-4fb5-a596-9eb7aa9c30af for some odd reason. I do not have such a device listed in /dev/disk/by-uuid/ and must conclude that there is a bug in the tool which causes it to generate this seemingly random number.

  Workaround:
  Before being asked to reboot, restore the original UUIDs to the root parameter by replacing the invalid ones generated.
  For me, the UUID for the boot partition was correctly identified by the update program which meant at least I didn't have to fix that piece in menu.lst. Others may not be so lucky so to make certain, also check the boot partition UUID.

  The easiest way is to delete menu.lst file generated by the upgrade
  program and then run update-grub to generate a new menu.lst file. This
  generated file *has correct UUIDs* !.

  A variant for those who have customized their grub files is naturally
  to do a copy-paste excercise of the new list entry for the updated
  kernel into their old file and then to fix the root UUID by making
  sure its the same as the corresponding value in their Ubuntu 8.10
  version of the menu.lst.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/377006/+subscriptions