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

[Steve Langasek]

On Tue, Dec 10, 2013 at 09:26:47PM -0000, James Burns wrote:
> I'm having the same issue as Nathan. There should be a way to totally
> disable prompting in mountall if this is to be deployed in the cloud.

And do what instead of prompting?  The system blocks on mountall because
it's waiting for the filesystem to become available.  You have no console,
and you have a misconfigured /etc/fstab.  What are you expecting the system
to do here?  Try to bring up sshd when half of the filesystem may still be
missing?

If you deploy an image to the cloud with a wrong /etc/fstab, you get to keep
both pieces.

If you have a specific case where mountall is blocking the boot waiting for
some mount point that it *shouldn't* wait for, you'll need to provide more
specific information.

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

Title:
    Boot process hang because 'mountall' fails

Status in “plymouth” package in Ubuntu:
  Confirmed

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/plymouth/+bug/1096307/+subscriptions