Wrong bootarg for disk with label
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
flash-kernel (Ubuntu) |
Fix Released
|
High
|
Oliver Grawert | ||
Quantal |
Fix Released
|
High
|
Adam Conrad | ||
Raring |
Fix Released
|
High
|
Oliver Grawert |
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=
I fixed it thanks to busybox by putting back label "ubuntu2" to my /dev/sda2 partition.
Changed in flash-kernel (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Oliver Grawert (ogra) |
description: | updated |
Changed in flash-kernel (Ubuntu Quantal): | |
assignee: | nobody → Adam Conrad (adconrad) |
importance: | Undecided → High |
hmm, i cant see any issues in the logs, flash-kernel- installer is supposed to use:
blkid -o value $(mount | grep "on /${1%/} " | tail -n1 | cut -d' ' -f1) | head -1
for setting root= at the very end of the install, this should actually return the proper UUID instead of a label.