[Bug 928990] [NEW] fsck / dirty filesystem on instance is death

Scott Moser smoser at ubuntu.com
Wed Feb 8 17:03:44 UTC 2012

Public bug reported:

As we saw in bug 898373, if a filesystem needs manual intervention for
an fsck, then boot completely stops.  mountall will wait indefinitely on
someone attending to this broken filesystem, and in a cloud (at least in
EC2) with no console access, that means the system will never boot.

I discussed this in #ubuntu-devel with slangasek at

He suggested to mark disk 'noauto' or 'nobootwait', but that is not
really what someone would want to do.

The ideal fix in some sense would be to start an ssh daemon, and force
the user into a screen session where they could fix it.

To that, slangasek said:
  smoser: sure, either fixing /etc/init/mountall-shell.conf to support this, or diverting it in a cloud-specific job, seems reasonable there

Related bugs:
 * bug 898373 : fsck.ext3: Device or resource busy while trying to open /dev/xvda2

** Affects: cloud-init (Ubuntu)
     Importance: High
         Status: Triaged

** Tags: cloud-images ec2-images

You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.

  fsck / dirty filesystem on instance is death

To manage notifications about this bug go to:

More information about the Ubuntu-server-bugs mailing list