'EXT3-fs: error loading journal'
'EXT3-fs: error loading journal' error is really confusing one.But somehow I got away with it by doing fsck from live CD.Simple solution to this error is checking file system integrity.In my case the file system seems became ext2 where it should be ext3 and fsck brought it back it to original one.
*Boot from rescue CD or Live CD and type "e2fsck /dev/sdax" or "fsck /dev/sdax" where sdax is your Linux partition.It will then ask to replace or fix corrupted blocks and etc.Accept everything by typing 'Y'.
It worked for me twice and it's better than reinstalling the whole thing.I have checked this on Fedora 8 and I am sure it works for other distros as well.If anyone have better ideas please let me know.Thanks in advance.
1 comment:
hi,
i had a trouble with ubuntu. the boot part worked well. but when loading the system there were some errors. as if it couldn't read the linux partition. then it wrote "initramfs" and the ubuntu didn't start. i opened with live cd and and tried the code you gave above. the output was as follows:
hint: some parts of the output are in other language but i translated them into english
fsck 1.41.4 (27-Jan-2009)
e2fsck 1.41.4 (27-Jan-2009)
fsck.ext2: No sych file or directory - an error occured while opening /dev/sdax
super block can't be read or ext2 file system cannot be defined.
if the device is valid and if it really contains ext2 file system, (and if it is not a swap part or ufs), then it means that the super block is damaged (broken down). you should try e2fsck with another super block:
e2fsck -b 8193 device
Post a Comment