Btrfs /boot partition has no UUID

[KDEUSER56]

Do the following to reproduce the problem: Using the installer create a /boot partition (primary) using btrfs as file system. When the install is finished and you boot up the system, the fstab entry for /boot looks like this:

/dev/sda1 /boot btrfs defaults 0 2

This does not happen if I repeat the exact same procedure using ext2/ext3/ext4 for the /boot partition, where an entry in the resulting fstab looks like expected:

UUID=13b5e56a-825c-4633-bd65-64174ecc3c7b /boot ext4 defaults 0 2

I tried to manually solve this issue by running

"sudo blkid /dev/sda1", but nothing is returned and "sudo blkid" does not list /dev/sda1 anywhere.

There is a reason partitions should be mounted by UUID and not by /dev/sdXY, because under certain circumstances the partition will not be found.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
Date: Fri Jun 13 17:15:46 2014
InstallCmdLine: file=/cdrom/preseed/install.seed boot=casper noninteractive noprompt initrd=/casper/initrd.lz quiet splash -- BOOT_IMAGE=/casper/vmlinuz.efi
InstallationDate: Installed on 2014-06-13 (0 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
SourcePackage: ubiquity
UbiquityDebug:
 Ubiquity 2.18.7
 locale.setlocale failed: unsupported locale setting (LANG=en_US)
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
DistroRelease: Ubuntu 14.04
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --
InstallationDate: Installed on 2014-06-15 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Tags: trusty ubiquity-2.18.7
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True

[KDEUSER56 (kdeuser56)]

Preseed file used for the installation the apport debug information is from.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that there is a problem with your installation media (CD/DVD). You can verify the integrity of the Ubuntu ISO files you downloaded by following the instructions at https://help.ubuntu.com/community/HowToMD5SUM. You might also retry your installation with new media. In the event that is is not in fact an error with your installation media please set the bug's status back to New. Thanks and good luck!

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[KDEUSER56 (kdeuser56)]

No, that is not a problem of my install media ... I knew why I did not attach the logs initially. The problem is clearly reproducible with an official media using manual install (no preseeding, no qemu for installing). The media I used for the install the log files come from was remastered (I modified the default boot options and placed a script in the squashfs image. Everything was remastered carefully and according to official documentation. However, as mentioned the problem exists even without changing anything.

This bug clearly applies to all current Ubuntu images.

[Chris Murphy (dr4-b5gpiyla-tff)]

Using ubuntu-14.04-desktop-amd64.iso installing with a custom layout to UEFI VM, partitions are EFI System partition (vfat), boot (btrfs), and root (btrfs), with no swap partition, each btrfs volume has a UUID and it's used in the fstab. So I can't reproduce this bug.

[KDEUSER56 (kdeuser56)]

Chris, thanks for having a look, but it is clearly reproducible, I have even recorded the whole setup process using virtualbox, to make sure it is not related to me:

https://drive.google.com/file/d/0B-ihXi2hkCPfdm5rSlk4dWxHLUE/edit?usp=sharing

I forget to demonstrate blkid at the end, though, I did that later, after the first screen cast was uploaded.

https://drive.google.com/file/d/0B-ihXi2hkCPfU3cweWotRnFzX0k/edit?usp=sharing

It is clearly demonstrated that the bug exists and you can reproduce it very easily.

[KDEUSER56 (kdeuser56)]

apport information

[KDEUSER56 (kdeuser56)]

apport information

[KDEUSER56 (kdeuser56)]

apport information

[KDEUSER56 (kdeuser56)]

apport information

[KDEUSER56 (kdeuser56)]

apport information

[KDEUSER56 (kdeuser56)]

Comments 8-12 are the information added from the virtualbox setup demonstrated in the screencast (see #7) and was automatically attached by apport-collect, hence the additional description here.

[KDEUSER56 (kdeuser56)]

I could not reproduce this bug anymore on the latest daily utopic iso, I am not absolutely sure yet, I have to do a final test to be sure this was really resolved.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Phillip Susi (psusi)]

It sounds like this was fixed a few years ago so I'm closing it. If you can still reproduce it on a current release, feel free to reopen it.