Looks like the dm-crypt part is working as expected, so basically it's
not a dmcrypt issue but a filesystem issue (ext3). I suggest to copy
your partition to a save location and then try fsck.ext3
/dev/mapper/tomb0 (but i'm afraid you will suffer data loss, always
make backups!)
regards, evert
James B Robinson wrote on 2006-10-17 20:32:
My linux desktop wedged this morning with an I/O error. I forced a reboot and now cannot mount one of my two encrypted filesystems:
losetup /dev/loop1 /tomb1
cryptsetup luksOpen /dev/loop1 tomb1
(password dialog)
mount /dev/mapper/tomb1 /home/tomb1
works as expected and shows:
mount
/dev/mapper/tomb1 on /home/tomb1 type jfs (rw)
losetup /dev/loop0 /tomb0
cryptsetup luksOpen /dev/loop0 tomb0
(password dialog)
mount /dev/mapper/tomb0 /home/tomb0
mount: wrong fs type, bad option, bad superblock on /dev/mapper/tomb0,
missing codepage or other error
cryptsetup status tomb0
/dev/mapper/tomb0 is active:
cipher: aes-cbc-essiv:sha256
keysize: 128 bits
device: /dev/loop0
offset: 1032 sectors
size: 8387576 sectors
mode: read/write
How fragile are these filesystems? Is that data now gone?
Thanks
---------------------------------------------------------------------
dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx
