This bug was fixed in the package linux - 4.8.0-15.16

linux (4.8.0-15.16) yakkety; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
    - LP: #1626239

  * image won't boot after upgrading to yakkety's 4.8 kernel because efi
    (LP: #1626158)
    - [Config] CONFIG_FAT_DEFAULT_IOCHARSET=iso8859-1
    - [Config] CONFIG_NLS_CODEPAGE_437=y
    - [Config] CONFIG_VFAT_FS=y

  * Miscellaneous Ubuntu changes
    - SAUCE: seccomp: log actions even when audit is disabled

 -- Tim Gardner <>  Wed, 21 Sep 2016 06:41:03

** Changed in: linux (Ubuntu)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  image won't boot after upgrading to yakkety's 4.8 kernel because efi

Status in cloud-images:
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:

Bug description:
  If I use a relatively recent yakkety daily with uvt-kvm, 20160918

  and upgrade the kernel to the latest kernel (which happens to be 4.8),
  my VM won't boot any more. kern.log has:

  and systemd complains that,

  [FAILED] Failed to mount /boot/efi
  See 'systemctl status boot-efi.mount' for details.

  and dumps me to a recovery console. Of course, I don't have EFI since
  I'm booting this thing on KVM. The problem here (I think) is that
  /boot/efi is in /etc/fstab, and systemd fails to boot when anything in
  /etc/fstab doesn't work.

  If I comment /boot/efi out of /etc/fstab, it boots just fine.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to