@scott: you're right, it's not fsck'ing after all—I left it running
overnight and saw no change. This is getting a bit worrying because the
old init=/bin/sh trick isn't working either, even with the oldest kernel
I have installed.
Pressing esc (amazing I hadn't tried this) gives me a legible text
console. It says:
{{{
fsck from util-linux-ng 2.17.2
/dev/sda3 contains a file systetm with errors, check forced.
/dev/sda3: Inodes that were part of a corrupted orphan linked list found.
/dev/sda3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
mountall: fsck / [382] terminated with status 4
mountall: Filesystem has errors: /
udevd[392]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/isight.rules:1
}}}
I guess the udev warning is about the webcam config.
So it did try to fsck, but fsck punted to the user and the user didn't
get to see the message. I'll have to bake a boot CD using my other
machine and boot from that for a manual fsck. (To make matters worse,
this other machine is having network trouble and after a Karmic upgrade
also went into read-only just now :-/ )
--
Boot stuck somewhere before starting X server
https://bugs.launchpad.net/bugs/553374
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
