Stefan, I tried to reproduce what you did above, and the system did not come back up. Worse, there are no console messages after '[ 145.610072] Restarting system.' (this was on t1.micro). This happened 3 out of 3 times for me.
This is the first time I've looked at those logs in depth. In both cases, user space comes up and we get to a "mounted MOUNTPOINT=/" event. That can be seen by 'cloud-init' messages. Then, something goes awry and we kernel messages like: [ 8.923830] end_request: I/O error, dev sda1, sector 12853456 [ 8.923850] end_request: I/O error, dev sda1, sector 12853456 [ 8.924184] Aborting journal on device sda1-8. [ 8.926353] EXT4-fs error (device sda1): ext4_journal_start_sb:251: Detected aborted journal [ 8.926369] EXT4-fs (sda1): Remounting filesystem read-only [ 8.928419] EXT4-fs error (device sda1): ext4_journal_start_sb:251: Detected aborted journal -- natty kernel fails to mount root on ec2 https://bugs.launchpad.net/bugs/669496 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
