November 29, 2008
Ubuntu Tip: Fixing ext3 "No Journal On Filesystem" Error

I rebuilt my main desktop PC tonight.  I’m running LVM on top of RAID1.  The problem is, the second time I booted the machine my main 250GB data partition went belly-up.  The boot-time error advised me to run fsck, which I did.  Everything looked good, but I still couldn’t mount the volume.  sudo mount -a gave me this error:

mount: wrong fs type, bad option, bad superblock on /dev/mapper/vgdata-lvdata, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so

So I ran dmesg | tail and got this:


[ 2357.033305] ext3: No journal on filesystem on dm-4

PCFascist over at the Ubuntu Forums has the fix:

tune2fs -j /dev/yourpartitionid

This command will write a new journal to your partition. You will then be able to mount it normally.