I applied the libs and other utilites from e2fsprogs by hand.
I ran fsck.ext3 on my secondary partition and it ran fine. The boot fsck
on / was complaining about something but I could not catch it.
I then went single user and ran fsck.ext3 on / while mounted.
Bad move. It ran and reported many errors which I chose to repair.
It screwed the partition up to the point where it paniced on boot.
I could still get it into single user but I found that lots of files were
missing which happened to be located in lost+found (inittab, rc.local, etc).
Anyone else have luck with this combination?
Excuse the stupid question, but with ext3, do I really require the
fsck.ext3?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/