On Tue, 19 Mar 2002, Karl Bowden wrote: > I had my redhat machine crash on me last nite. And now when I boot it tells > me that fsck.ext3 has exited with and error level of 7. I can run fsck.ext3, > fsck.ext2, and e2fsck, and the all give me the message "Bus Error". I then > popped in the redhat 7.2 cd and booted the rescue image. In the rescue image > it fsck'd all the partitions with no prob, but upon reboot it still gives > the same message. > > What's wrong?
Somehow, possibly due to a hard failure at some stage the journal file's probably been corrupted. Find the partitions giving the problem and see if they can be mounted from a rescue disk as ext2 filesystems. If that appears ok, edit /etc/fstab to reflect this then try booting up normally. Once you've got your system up you should probably backup anything critical (if you haven't already) then remove the .journal file from the root of the filesystem. Next bootup in single user mode and run e2fsck -f <partition device> and at some point it'll say something to the effect of "hey the journal seems shit, want me to re-create it?" to which you answer yes. Then you can work backwards from here and mount them as ext3 again. -- ---<GRiP>--- Web: www.arcadia.au.com/gripz Answering Machine/fax: 02 4950 1194 (wait 5 mins if no answer) Mobile: 0408 686 201 -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
