Hello all, I have a few ext3 file systems that are not being recognized. Here is the setup: MD software RAID 5 on 4 disks (md0), a LVM logical volume (/dev/volume_group/logical_volume) comprised of one physical device (/dev/md0), a encryption layer provided by the cryptoloop driver (losetup -e aes /dev/loop0 /dev/volume_group/logical_volume), then a EXT3 file system (mkfs.ext3 /dev/loop0). Recently the RAID device kicked out one of the disks during a large file transfer. After re-adding the disk to the array (smartctl didn't report anything wrong with it, I am not sure why this happened), authenticating against the cryptographic layer, then trying to mount the drive, I get the following error: [root@storage redhat]# mount -t ext3 /dev/loop1 /terrorbyte/1/ mount: wrong fs type, bad option, bad superblock on /dev/loop1, The message in /var/log/message is: VFS: Can't find ext3 filesystem on dev loop1. I then tried to e2fsck the /dev/loop1 partition with all of the different blocks that were reported from: mke2fs -n /dev/loop1 with no luck still. I am unsure of where the problem actually is, and how to go about debugging it. Any suggestions would be appreciated. Sincerely, Dennison Williams -- ***************************************************************** * To communicate with me securely, please email me and I will * * send you my public key. We can then verify each others * * fingerprints in person, or over the phone. * * * * I am open and willing to talk about setting up PGP, the * * security problems inherent with PGP, and alternatives to PGP * * for secure electronic communication. * ***************************************************************** _______________________________________________ Ext3-users mailing list Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
