>From next week I won't have access to the laptop. So I am not sure how
much help I can provide.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1633828
Title:
Mounting
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="WINR
ping. ping. This bug should be looked upon. Does not make sense to mark
it as expired and moving on.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1633828
Title:
Mount
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.
** Attachment added: "fstab"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/163382
I am able to mount efi partition manually.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1633828
Title:
Mounting /boot/efi fails always after updating to 16.10
Status
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" wrote:
> So what happens when you don't comment it out? What happens if you
> manually try to mount it?
>
>
> ** Change
Booted into Windows 8 once and came back. Now audio and wifi starts
automatically. Don't know if it is a coincidence.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1633825
Public bug reported:
System was booting normally with 16.04. Upgraded to 16.10, system goes
to emergency console on every boot. This happened due to timeout in
mounting /boot/efi. Commented out /boot/efi entry in /etc/fstab. System
boots after that. But wifi, bluetooth and sound does not start
aut
Public bug reported:
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: mou
9 matches
Mail list logo