[Bug 623303] Re: If a drive in the fstab is missing at boot, the boot process hangs for user input

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 571444 ***
    https://bugs.launchpad.net/bugs/571444

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

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

Title:
  If a drive in the fstab is missing at boot, the boot process hangs for
  user input

Status in “mountall” package in Ubuntu:
  Confirmed

Bug description:
  STEPS TO REPRODUCE:

  1. List a removable drive in the fstab.
  2. Power off.
  3. Remove the drive.
  4. Power up.

  EXPECTED BEHAVIOR: The system boots as normal, obviously not booting
  the absent removable drive.

  ACTUAL BEHAVIOR: The boot process hangs with the message: "The disk
  drive for [mount point] is not ready yet or not present. Continue to
  wait; or press s to skip mounting or M for manual recovery."  This
  behavior is new in Ubuntu 10.04.  It is apparently not configurable.

  WHY THIS IS WRONG: Many people include drives in the fstab that are
  not necessarily present at launch.  I have a USB hard drive listed
  there.  In these situations it is not appropriate to pause for user
  input: the boot process does not critically depend on the documents on
  my thumb drive.  Pressing 's' every time you boot ranges from a minor
  annoyance to an extreme inconvenience (as in my case where I run
  Ubuntu as a server with no attached keyboard!).

  PROPOSED SOLUTION: either (a) go back to the pre-10.04 boot behavior,
  or (b) provide a way to list fstab drives as removable/non-critical.

  Note: There is an analogous bug in the server edition at
  [https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/571444],
  which is causing people extreme annoyance.

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