Just a few comments: fsck died with exit status 8 - this means "Operational error" and not file system error. It seems like it tries to check a device that doesn't exist. All the text below "CONTROL-D" is due to another bug (bug #121992), where the bashrc depends on stuff not in the path, and the command-not-found handle is tried to be run.
The error appears in /etc/rcS.d/S30checkfs.sh which checks all filesystems except the root fs. If you run fsck -V -R -A echo $? in the "maintenance shell", do you still get the error and a "8" ? If you run it in the "recovery mode" boot? Or just on the command line after umount'ing all file systems except root? -- Boot interrupted after feisty upgrade--gives a command prompt for no apparent reason https://bugs.launchpad.net/bugs/106565 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
