[Bug 1329794] Re: Btrfs boot partition does not have an UUID

[KDEUSER56]

** Description changed:

  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/sdb1       /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 a entry in the resulting
+ 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/sdb1", but nothing is returned and "sudo blkid" does
  not list /dev/sdb1 anywhere.
  
  This issue is annoying and often leads to the /boot partition not being
  mounted on the target system. For example suppose you install your
  system on a external harddrive using qemu. Then the external drive will
  be something like /dev/sda in qemu, but when you boot on real hardware
  it will be something like /dev/sdb and wont mount /boot.
  
  This issue is reproducible for Ubuntu 14.04 and 14.10, I have not tried
  earlier versions.
  
  I always took an empty external disk to reproduce this issue. Originally
  the issue became apparent, when my preseeded install conducted in qemu
  did not mount mount /boot on the real hardware, because /dev/sda1 needed
  to be exchanged with /dev/sdb1. This issue is not due to preseeding, I
  could reproduce it manually by creating a btrfs /boot and a btrfs /
  partition on an empty usb. The root partition had an UUID as expected,
  /boot did not.

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

Title:
  Btrfs boot partition does not have an UUID

Status in “ubiquity” package in Ubuntu:
  New

Bug description:
  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/sdb1       /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/sdb1", but nothing is returned and "sudo blkid" does
  not list /dev/sdb1 anywhere.

  This issue is annoying and often leads to the /boot partition not
  being mounted on the target system. For example suppose you install
  your system on a external harddrive using qemu. Then the external
  drive will be something like /dev/sda in qemu, but when you boot on
  real hardware it will be something like /dev/sdb and wont mount /boot.

  This issue is reproducible for Ubuntu 14.04 and 14.10, I have not
  tried earlier versions.

  I always took an empty external disk to reproduce this issue.
  Originally the issue became apparent, when my preseeded install
  conducted in qemu did not mount mount /boot on the real hardware,
  because /dev/sda1 needed to be exchanged with /dev/sdb1. This issue is
  not due to preseeding, I could reproduce it manually by creating a
  btrfs /boot and a btrfs / partition on an empty usb. The root
  partition had an UUID as expected, /boot did not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1329794/+subscriptions