I have searched for a couple of file names in the meantime, but I couldn't find a single filename in my home directories :-(.
I'll search for revdep-rebuild and try photorec - I guess that's all I can do :cry:
Maybe I'm lucky and get at least some of my files back.

If you get any other ideas of ...

Unbelievable how often "lost+found" is contained inside of scripts .... (obviously I left those out)
After a lot of searching I finally found a few non-script-occurrences, but none that had other directory-names nearby :-(

Offsets all start with 62:

60A1E51C 20 D0 BF D1 80 D0 B8 D0 B7 D0 B2 D0 B5 ...

searching finished - it hasn't found any other occurrences

Since I installed those other distributions with an installer, that's what might have happened .

Here are the offsets of SWAPSPACE2 I found so far:
61E181C0C8
61E181C3B8
61E181C6A8
61E181C998
61E181CC88
61E181CF89
61E181D3E0
61E181D848
61E181DCB0
61E181E118

They all look wrong

I just noticed hexedit cuts of the position after 8 digits . But it had 10 digits, it searched for quite some time.
I'll search for it again and look for an occurrence that's aligned.

Btw the only place that could have had a different swappartition/-file could be a virtualbox-image. A while ago I ...

I found the swapspace-string (inside of censored-crypt):

E181BDB4 00 00 00 00 00 00 20 00 3D 0A 05 00 00 00 00 00 F6 7F 00 00 00 00 00 00 51 00 00 00 00 00 00 00 00 00 00 00 53 57 41 50 2D 53 50 41 ...... .=...............Q...........SWAP-SPA
E181BDE0 43 45 00 00 00 00 00 00 00 00 00 00 00 00 00 ...

I'll omit all the outputs from my for-loop since they are all the same.
mount: /mnt/gentoo: wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error.
I ran:
for i in 131072 393216 655360 917504 1179648 3276800 3538944 6422528 10616832 16384000 ...

Same problem:
livecd ~ # for i in 131072 393216 655360 917504 1179648 3276800 3538944 6422528 10616832 16384000 31850496 44957696 81920000 95551488 286654464 314703872 409600000 859963392; do echo $i; mount -o ro,sb=$i -v /dev/mapper/censored--encrypted-root_fs /mnt/gentoo/ && break; done
131072 ...

I tried all those superblocks:
for i in 131072 393216 655360 917504 1179648 3276800 3538944 6422528 10616832 16384000 31850496 44957696 81920000 95551488 286654464 314703872 409600000 859963392; do mount -o ro,offset=40112578560,sb=$i /dev/mapper/censored-crypt /mnt/gentoo/ && break; done
mount ...

NeddySeagoon,

I have ordered an external drive (for backups! - finally), but it will probably arrive the day after tomorrow, so right now I don't have a drive which can hold 1TB .
I guess I have to wait for my saviors ssd to finish it's internal operations .

Btw thanks for all that help!

NeddySeagoon,

the math looks right to me.

So I ran hexedit on the root-fs. I don't have much of an idea what I actually did, but at least I found a block of a lot of zeroes! (not at the beginning though) Maybe you can tell me what to do with those results:


0249A060 73 69 6E 68 5F 73 69 6E 68 2E ...

NeddySeagoon,

sadly no luck either:
livecd ~ # mount -o ro,offset=40112578560 /dev/mapper/censored-crypt /mnt/gentoo/
mount: /mnt/gentoo: wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error.
livecd ~ # mount -o ro,offset=40112578560,sb=131072 ...

NeddySeagoon,

you gave me hope. But then my system destroyed it again:
livecd ~ # mount -o ro,offset=40649449472 /dev/nvme0n1 /mnt/gentoo/
mount: /mnt/gentoo: wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error.


But then also nvme0n1 is ...

Manu311,

The entire /dev/nvme0n1.

We know the filesystem start from the end of the drive but offset= is a count of bytes from the start of the drive.
Alright, so here's the fdisk-part from nvme0n1:
Disk /dev/nvme0n1: 953.89 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: Samsung SSD ...

So, this?
Disk /dev/mapper/censored-crypt: 953.38 GiB, 1023672320000 bytes, 1999360000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/censored--encrypted-swap_fs: 37.37 GiB ...

NeddySeagoon,

my understand is that the --encrypted_root-fs is just the partition within LVM. While the PV the lvm is on (/dev/mapper/censored-crypt) should also be decrypted. The crypted device should be /dev/nvme0n1p2

I'll download the admin-cd, so I got more tools.

I guess there's also no use ...

The idea is to locate the start of the filesystem, so it can be mounted.
Interesting - the gentoo minimal image apparently doesn't have "strings" on it. And since there's no emerge either, I figured the idea should still work if I just use grep on it (but it will probably take longer), so that's ...

Manu311,

Either your filesystem has been destroyed or /dev/mapper/censored--encrypted-root_fs does not point to the start of it, that would explain why the alternate superblock mount failed too.

The LVM recovery process only writes PV and LV metadata. filesystems are not harmed.
You also have ...

Manu311,

Try dumpe2fs /dev/mapper/censored--encrypted-root_fs
Does that look like ext4?

Then there is mount -o ro,sb=131072 /dev/mapper/censored--encrypted-root_fs /mnt/gentoo/
Then there is the offset=<Bytes> option, where Bytes is the offset to the start of the filesystem. That's difficult to ...

But did you try to mount the root lvm from the livecd?
Is it mountable?
Like this?:

livecd ~ # mount /dev/mapper/censored--encrypted-root_fs /mnt/gentoo/
mount: /mnt/gentoo: wrong fs type, bad option, bad superblock on /dev/mapper/censored--encrypted-root_fs, missing codepage or helper program ...

I would advice you if your root partition can be mounted to backit up somewhere using rsync and then delete and recreate your pv vg and lvs...
I would love to do that, but my root partition is the only data-partition inside of that lvm, so I can't back it up unless I can fix my problem at least ...

Try from a live cd.
Are the lvm partitions visible from livecd?
Please run lsblk
If the partitions are visible maybe your problem is just reinstalling grub.
Can you mount the root partition from a livecd?
Lvm partitions dont just disappear...
After a couple of minutes, I switched to a "livecd" (it ...

Hello,

I have a pretty bad problem with my Luks/Lvm setup and lost access to my system. Hopefully someone can help me get back my data.

I'll start with my setup:
I needed to have my Gentoo on an (almost) fully encrypted harddrive with as much security as possible, so I went with luks (aes-xts ...

Still no working, more recent kernel :-(

But funnily enough, with the 4.14.61 kernel (in contrast to 4.14.52) I now get this:
https://imgur.com/fyeLfxI
So I assume the system might actually now boot (it reacts to ctrl-alt-del), but some wrong framebuffer-/display-driver gets loaded.
However I wasn ...

I don't think /etc/kernels actually does anything. From my experience it's just a place where your config get's copied, and I started collecting different ones there on my server now.
Kernel sources are indeed at /usr/src, but they don't really help me here. And I don't remember any kernel compiling ...