*** journal has been re-created - filesystem is now ext3 again *** /dev/loop7: ***** FILE SYSTEM WAS MODIFIED ***** 11 inodes used (0.00%, out of 655360) 0 non-contiguous files (0.0%) 0 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 2 79663 blocks used (3.04%, out of 2621440) 0 bad blocks 1 large file 0 regular files 2 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets ------------ 2 files root@falalala:/disaster/rec# ls data metadata root@falalala:/disaster/rec# mount -t ext4 -s -o ro /dev/loop7 /tmp/lemount root@falalala:/disaster/rec# ls -l /tmp/lemount/ total 16 drwx------ 2 root root 16384 Feb 21 2015 lost+found root@falalala:/disaster/rec# ls -l /tmp/lemount/lost+found/ total 0 root@falalala:/disaster/rec# umount /tmp/lemount root@falalala:/disaster/rec# mount -t ext3 -s -o ro /dev/loop7 /tmp/lemount mount: wrong fs type, bad option, bad superblock on /dev/loop7, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so root@falalala:/disaster/rec# dmesg | tail [1214211.387124] storvsc: Add. Sense: Invalid command operation code [1403991.956286] JBD2: no valid journal superblock found [1403991.956294] EXT4-fs (loop7): error loading journal [1404183.320656] JBD2: no valid journal superblock found [1404183.320662] EXT4-fs (loop7): error loading journal [1405029.817496] EXT4-fs (loop7): mounted filesystem without journal. Opts: noload [1405113.307686] JBD2: no valid journal superblock found [1405113.307692] EXT4-fs (loop7): error loading journal [1406141.885425] EXT4-fs (loop7): mounted filesystem with ordered data mode. Opts: (null) [1406169.554797] EXT4-fs (loop7): couldn't mount as ext3 due to feature incompatibilities