Howto solve LVM journal

Kasus : ente punya mesin linux (centos) filesystem ext3 journal (tipe partisi LVM)
pas loading ga mau lanjut

have an error like this?

JDB: failed to read block at offset 8797
EXT3-fs: error loading journal

Kiamat deh bos server ente, hehee
tp gpp cb kita repair.

coba cabut HD, trus tempel di linux lain

liat HD kita kedetect ga?
#fdisk -l

kl ad, msh ada harapan!
#ls /etc | grep -i Vol

ga ada? lanjut
#pvscan (phisycal)
#vgscan (volgroup)
#lvscan (logical)no



#init 6

#mount /dev/Vollgroup00/LogVol00 /mount/bla

congrat! 😀

Another way :
Do you have a live CD or, perhaps, your install DVD? Can you boot into rescue mode?

If you can, what’s happened is that your journal file was corrupted when your power was lost, and you need to convert your ext3 file system to an ext2 version, run fsck on the ext2 system, and then add the journel file back in to make it an ext3 file system.

What I’d suggest is this:

1) Boot linux rescue from your installation media
2) That should (try to) mount your root file system as /mnt/sysroot (You should see a message suggesting that you chroot if the mount was successful.) If it did mount it successfully, use the umount /dev/mapper/VolGroup00-LogVol00 command to unmount it. Note: The device name used here is the one Fedora uses by default. If you’ve change it, or if you’re not using logical volumes, use the correct device name here and below.
3) Now, see if fsck /dev/mapper/VolGroup00-LogVol00 e2fsck can fix the problem. If it succeeds, you’re “home free.”
4) If fsck barfs on the file system, use the command
tune2fs -O ^has_journal /dev/mapper/VolGroup00-LogVol00 to remove the journal file.
5) Run fsck /dev/mapper/ragain to fix any problems.
6) Run tune2fs -j /dev/mapper/VolGroup00-LogVol00 to recreate the journal file.

Leave a Comment

Your email address will not be published. Required fields are marked *