when trying to mount decrypted devices, this appears in the logs:
May 3 11:47:04 debian kernel: ReiserFS: dm-3: found reiserfs format "3.6" with standard journal
May 3 11:47:04 debian kernel: ReiserFS: dm-3: using ordered data mode
May 3 11:47:04 debian kernel: attempt to access beyond end of device
May 3 11:47:04 debian kernel: dm-3: rw=0, want=3191529648, limit=976960845
May 3 11:47:04 debian kernel: ReiserFS: dm-3: warning: sh-459: unable to read journal header
May 3 11:47:04 debian kernel: ReiserFS: dm-3: warning: sh-2022: reiserfs_fill_super: unable to initialize journal space
The same symptoms occur with all devices that are encrypted, 6 in total.
Let me explain chronologically what happened:
- encryption of harddisks with data already on it via cryptsetup && dd
- mounting of the resulted encrypted devices give no problem
- server is shutdown to enter a new disk, when booting it was reported that CTRL+D had to be pressed to continue after some 'maintenance'
- after bootup, when decrypting the devices and trying to mount, aforementioned messages appear in the logs
After makeing a backup of one of the devices, I checked with reiserfsck which says the superblock has to be rebuilt, after doing so it complains that the tree has to be rebuilt. After rebuilding (with the extra -S flag even) only one file is found and put in lost+found.
When placing the backup back and using testdisk on it, millions of partitions are found when doing a quick search for partitions, all reporting sizes far over the limit (most > 13TB).
I'm worried that the 'maintenance' modified the encrypted devices (I had forgotten to remove them out of fstab), as a single bit changed may corrupt the whole block device?
I have only tried rebuilding and recovering on the smallest backed up device so I don't know if the others yield more results.
Is all data lost or are there other methods to try, ...?