[Bug 1096307] Re: Boot process hang because 'mountall' fails

[Steve Langasek]

Please elaborate on what you mean when you say "mount a non-existing
device node".  Do you mean you've added an entry to /etc/fstab?  If so,
please show the exact fstab that triggers this issue.

A missing system filesystem caused by an incorrect entry in /etc/fstab,
or a failed disk, is indistinguishable from a device being slow to
appear.  It is therefore incorrect for mountall to silently ignore a
missing disk and boot without it, as this would cause services to fail
to start correctly; the only correct course of action is to halt the
boot, notify the user of the missing filesystem, and give them the
option to intervene.  This is exactly what mountall does, presenting
users via plymouth with the option to skip the disk.

So from your description, I don't think there's a bug here at all.

** Changed in: mountall (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1096307

Title:
    Boot process hang because 'mountall' fails

Status in “mountall” package in Ubuntu:
  Incomplete

Bug description:
  We suspect a bug in Ubuntu 12.04 where boot process is hanged because ‘mountall’ fails due to an HDD failure.
    The issue can be easily reproduced through either of the following scenario on Ubuntu 12.04

    1. Mount a non-existing disk device node. 
    2. Disk/partition error. You can simulate such error by corrupting a working partition using DD command.

    In either case, you will see system stuck at mount procedure and never reach the login prompt. 
    I have tried some option like “timeout=30”, “optional”, update mountall to v2.46. But none of them is working.

    Thanks

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