Today I got an issue where after server reboot one of ext3 file system was not getting mounted on RHEL 5.10. It was not the root file system.
Below was the error which I was getting while mounted that file system.
[root@Node2 ~]# mount -t ext3 /dev/vg1/lv1 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/mapper/vg1-lv1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog – try
dmesg | tail or so
When I skip the type of file system “-t ext3” option I was able to mount the file system. Before doing that I tried fsck as well but that didn’t work.
[root@Node2 ~]# mount /dev/vg1/lv1 /mnt
I issued mount command to see the type of file system. Found that its in ext2 type.
[root@Node2 ~]# mount | grep -w ‘/mnt’
/dev/mapper/vg1-lv1 on /mnt type ext2 (rw)
I used the tune2fs utility to convert it into ext3 file system. Note : Strongly recommended to keep the backup of file system to avoid any unforeseen issue.
[root@Node2 ~]# tune2fs -j /dev/vg1/lv1
tune2fs 1.41.12 (17-May-2010)
Creating journal inode: done
This filesystem will be automatically checked every 22 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
After that I was able to mount the file system as ext3 🙂 Luckily in this case my data was intact 🙂
[root@Node2 ~]# mount -t ext3 /dev/vg1/lv1 /mnt
[root@Node2 ~]# mount | grep /mnt
/dev/mapper/vg1-lv1 on /mnt type ext3 (rw)
UnixGeek 