Comment 11 for bug 1096307

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.