Mounting /boot/efi fails always after updating to 16.10

[Prasanna Kumar]

System does not boot properly as mounting /boot/efi fails. Commented out /boot/efi entry in /etc/fstab to boot system normally. This started happening after update to 16.10. Everything was working fine in 15.10, 16.04.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: mount 2.28.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Sun Oct 16 15:23:19 2016
InstallationDate: Installed on 2015-11-20 (330 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: util-linux
UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago)

[Phillip Susi (psusi)]

So what happens when you don't comment it out? What happens if you manually try to mount it?

[Prasanna Kumar (prasannatsmkumar)]

System does not boot as mount times out and drops to a emergency shell.

Did not try mounting manually. Will get back with result soon.

On 29-Oct-2016 12:20 am, "Phillip Susi" <email address hidden> wrote:

> So what happens when you don't comment it out? What happens if you
> manually try to mount it?
>
>
> ** Changed in: util-linux (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633828
>
> Title:
> Mounting /boot/efi fails always after updating to 16.10
>
> Status in util-linux package in Ubuntu:
> Incomplete
>
> Bug description:
> System does not boot properly as mounting /boot/efi fails. Commented
> out /boot/efi entry in /etc/fstab to boot system normally. This
> started happening after update to 16.10. Everything was working fine
> in 15.10, 16.04.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.10
> Package: mount 2.28.2-1ubuntu1
> ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
> Uname: Linux 4.8.0-22-generic x86_64
> ApportVersion: 2.20.3-0ubuntu8
> Architecture: amd64
> Date: Sun Oct 16 15:23:19 2016
> InstallationDate: Installed on 2015-11-20 (330 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
> SourcePackage: util-linux
> UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/util-linux/+
> bug/1633828/+subscriptions
>

[Prasanna Kumar (prasannatsmkumar)]

I am able to mount efi partition manually.

[Phillip Susi (psusi)]

Can you show the exact command that you used to mount it, and the line from /etc/fstab?

[Prasanna Kumar (prasannatsmkumar)]

I copied the values from /etc/fstab while mounting. The command I used to mount is "sudo mount UUID=86E4-0AA9 /boot/efi".

Attached my /etc/fstab file. I have commented the line that mounts /boot/efi.

[Launchpad Janitor (janitor)]

[Expired for util-linux (Ubuntu) because there has been no activity for 60 days.]

[Prasanna Kumar (prasannatsmkumar)]

ping. ping. This bug should be looked upon. Does not make sense to mark it as expired and moving on.

[Phillip Susi (psusi)]

Sorry, I've gotten a few hundred messages behind in my bug mail folder... trying to catch up but it takes a while.

Just to confirm, when you uncomment this line:

# UUID=86E4-0AA9 /boot/efi vfat umask=0077 0 1

You get a time out looking for that drive? What does the output of sudo blkid show?

[Prasanna Kumar (prasannatsmkumar)]

Strangely, after uncommenting efi partition line in /etc/fstab, my system reboots fine. Till now it was commented out.

My blkid output:
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/sda1: LABEL="WINRE_DRV" UUID="B6F4E1E0F4E1A33B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="40d7cd20-c64b-4d6e-9ec6-2f9b7bc57985"
/dev/sda2: LABEL="SYSTEM_DRV" UUID="86E4-0AA9" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9fe5ac8b-82d1-4311-8ff5-d763ba29b588"
/dev/sda3: LABEL="LRS_ESP" UUID="00E6-80A2" TYPE="vfat" PARTLABEL="Basic data partition" PARTUUID="a9d68e36-9135-4d94-a3fe-2604cc1db8c2"
/dev/sda4: PARTLABEL="Microsoft reserved partition" PARTUUID="28d9cab0-1d72-4db4-a699-90a62634109e"
/dev/sda5: LABEL="Windows8_OS" UUID="86DAE939DAE925E1" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="f530366d-c780-4e6b-9404-90495e22f65f"
/dev/sda6: LABEL="LENOVO" UUID="E002B64A02B62586" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="21f550e9-70ed-4e79-8b18-fdd6c44edca5"
/dev/sda7: LABEL="PBR_DRV" UUID="DA22EBB022EB8FB5" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="825593db-4fc7-4fef-90d9-07c4e7fb6496"
/dev/sda8: UUID="5f90031d-96ee-455b-addc-7a833e0f42ce" TYPE="swap" PARTUUID="14abb1f1-e77d-4e16-9873-dbb2eda63c40"
/dev/sda9: UUID="e3865c00-93d9-4ed7-a9a4-35f9a0d1b16f" TYPE="ext4" PARTUUID="d2ed9481-51f8-4914-aee7-33a37ced5685"

[Phillip Susi (psusi)]

So the problem seems to have gone away eh? Well, if it comes back let us know.

[Prasanna Kumar (prasannatsmkumar)]

From next week I won't have access to the laptop. So I am not sure how much help I can provide.

[Launchpad Janitor (janitor)]

[Expired for util-linux (Ubuntu) because there has been no activity for 60 days.]