| 2014-06-13 14:17:09 |
KDEUSER56 |
bug |
|
|
added bug |
| 2014-06-13 14:18:01 |
KDEUSER56 |
bug |
|
|
added subscriber Dimitri John Ledkov |
| 2014-06-13 14:20:54 |
KDEUSER56 |
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 a entry in the resulting fstab looks like expected:
UUID=144c1ce2-1933-4c8d-b97d-fac26d44b571 /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. |
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 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. |
|
| 2014-06-13 14:52:02 |
KDEUSER56 |
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 a 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. |
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. |
|
| 2014-06-13 15:04:43 |
Dimitri John Ledkov |
ubiquity (Ubuntu): status |
New |
Incomplete |
|
| 2014-06-13 15:23:48 |
KDEUSER56 |
marked as duplicate |
|
1329810 |
|
