touch-packages team mailing list archive

[dreamcat4 <1471430@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Right.
Well this bug is something I stumbled into today. It turns out that:

"Whenever I have invalid /etc/fstab entries, the system fails to start
with systemd".

This can be seen in the debian bug tracker as bug #765586:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765586

I stongly believe it to be the same bug. For more infos go there. It is
basically that the error code is always reported back to the user
incorrectly. Due to a genuine bug in the affected systemd component(s).
The component is responsible for auto-finding and auto-mounting GPT
partitions at boot time. In absense of a valid fstab file (because
mounting fstab failed). Most times there is no real I/O error.

The error message is extremely non-intuitive and alarming + confusing
for users. They may un-knowningly try to take more drastic actions such
as replacing their HDD etc. Which are not necessary.


In my case it was that:

* It was the result of removing or failed HDD physical (permanment) device.
* Which had an entry in fstab.

Now what should happen, and has historically happened with upstart, up
to and including 14.10 is this message should appear during boot time
(when the fstab fails to find the disk to mount):

http://imgur.com/a2NoohQ

http://www.gooditdad.com/ubuntu-press-s-to-skip-mount-or-m-for-manual-
recovery/

This is a common situation that many users may find themselves in. When
their fstab file is not valid in respect to the currently attached
system disks. Including USB removable storage etc.

2 work-arounds:

* In Grub --> Ubuntu Advanced Boot Menu --> upstart mode
* Edit /etc/fstab file and try to find / comment out / disable the offending entries

2 solutions:

* Look to get this but fixed upstream in debian / systemd / wherever
* Don't use systemd

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: boot-failure fstab systemd

-- 
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/1471430

Title:
  systemd-gpt-auto-generator[$pid]: Failed to determine partition table
  type of /dev/sda: Input/output error

Status in systemd package in Ubuntu:
  New

Bug description:
  Right.
  Well this bug is something I stumbled into today. It turns out that:

  "Whenever I have invalid /etc/fstab entries, the system fails to start
  with systemd".

  This can be seen in the debian bug tracker as bug #765586:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765586

  I stongly believe it to be the same bug. For more infos go there. It
  is basically that the error code is always reported back to the user
  incorrectly. Due to a genuine bug in the affected systemd
  component(s). The component is responsible for auto-finding and auto-
  mounting GPT partitions at boot time. In absense of a valid fstab file
  (because mounting fstab failed). Most times there is no real I/O
  error.

  The error message is extremely non-intuitive and alarming + confusing
  for users. They may un-knowningly try to take more drastic actions
  such as replacing their HDD etc. Which are not necessary.


  In my case it was that:

  * It was the result of removing or failed HDD physical (permanment) device.
  * Which had an entry in fstab.

  Now what should happen, and has historically happened with upstart, up
  to and including 14.10 is this message should appear during boot time
  (when the fstab fails to find the disk to mount):

  http://imgur.com/a2NoohQ

  http://www.gooditdad.com/ubuntu-press-s-to-skip-mount-or-m-for-manual-
  recovery/

  This is a common situation that many users may find themselves in.
  When their fstab file is not valid in respect to the currently
  attached system disks. Including USB removable storage etc.

  2 work-arounds:

  * In Grub --> Ubuntu Advanced Boot Menu --> upstart mode
  * Edit /etc/fstab file and try to find / comment out / disable the offending entries

  2 solutions:

  * Look to get this but fixed upstream in debian / systemd / wherever
  * Don't use systemd

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