[Bug 1079185] Re: Wrong bootarg for disk with label

[Robie Basak]

** Description changed:

+ [Impact]
+ 
+ Installation fails on a Pandaboard on Quantal for users who previously
+ had a volume label on an existing partition.
+ 
+ [Test Case]
+ 
+ Create and label an existing partition (eg. using e2label). Then run the
+ installer. On first reboot, if the bug still exists, the system will
+ fail to mount the root filesystem.
+ 
+ [Regression Potential]
+ 
+ We're changing calls to blkid only by being specific that we want the
+ UUID instead of assuming that the UUID is on the first line. This has
+ been tested in d-i on Quantal. I can only see this regression if blkid
+ doesn't work as expected in this specific mode in some obscure case that
+ we haven't considered.
+ 
+ [Original Description]
+ 
  I just installed Ubuntu 12.10 on a pandaboard.
  
  At the installation, I selected an empty partition named "ubuntu2" et
  checked the box for formating.
  
  After the installation process, at the first boot, rootfs couldn't be
  mounted : the bootarg was "root=UUID=ubuntu2"
  
  So I changed the preEnv.txt on my computer to "root=LABEL=ubuntu2" but
  sill couldn't boot, as the label was erased during format process.
  
  I fixed it thanks to busybox by putting back label "ubuntu2" to my
  /dev/sda2 partition.

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

Title:
  Wrong bootarg for disk with label

Status in “flash-kernel” package in Ubuntu:
  Fix Released
Status in “flash-kernel” source package in Quantal:
  New
Status in “flash-kernel” source package in Raring:
  Fix Released

Bug description:
  [Impact]

  Installation fails on a Pandaboard on Quantal for users who previously
  had a volume label on an existing partition.

  [Test Case]

  Create and label an existing partition (eg. using e2label). Then run
  the installer. On first reboot, if the bug still exists, the system
  will fail to mount the root filesystem.

  [Regression Potential]

  We're changing calls to blkid only by being specific that we want the
  UUID instead of assuming that the UUID is on the first line. This has
  been tested in d-i on Quantal. I can only see this regression if blkid
  doesn't work as expected in this specific mode in some obscure case
  that we haven't considered.

  [Original Description]

  I just installed Ubuntu 12.10 on a pandaboard.

  At the installation, I selected an empty partition named "ubuntu2" et
  checked the box for formating.

  After the installation process, at the first boot, rootfs couldn't be
  mounted : the bootarg was "root=UUID=ubuntu2"

  So I changed the preEnv.txt on my computer to "root=LABEL=ubuntu2" but
  sill couldn't boot, as the label was erased during format process.

  I fixed it thanks to busybox by putting back label "ubuntu2" to my
  /dev/sda2 partition.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1079185/+subscriptions