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

[Nathan Groupp]

I have reproduced this on the Ubuntu 12.04 LTS AWS AMI. Resolving an
error is particularly nasty when using cloud services, as a second,
running instance is required to debug the cause of boot failures. On
AWS, this involves removing the EBS system volume from the instance then
mounting it temporarily on another. (Rackspace has a recovery mode that
does this automagically.) Any expectation of user input from the console
is just innappropriate for cloud environments. It would be useful, in
the event of mount failures of non-system-volumes to boot into some sort
of ILOM or recovery-mode with SSH running. This would allow the operator
to manually repair the instance.

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