Can't reach my system on the encrypted disk

[JanK]

@j2mcgreg @Adrian

OK. I am trying to do what is adviced.

Code: Select all

$ sudo parted -l

output

Code: Select all

Model: CT500P1SSD8 (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

			Number  Start   End     Size    File system     Name                          Flags
 			1      17.4kB  16.8MB  16.8MB                  Microsoft reserved partition  msftres
 			7      16.8MB  2244MB  2227MB  ext4                                          legacy_boot
 			6      2244MB  8837MB  6593MB  linux-swap(v1)
 (THIS ONE)               4      8837MB  71.8GB  62.9GB  ext4     (THIS ONE - IT IS /HOME ENCRYPTED)
 			3      71.8GB  160GB   88.1GB
 			5      160GB   500GB   340GB   ntfs                                          msftdata
 			2      500GB   500GB   537MB   fat32                                         boot, esp

and then

Code: Select all

$ sudo mke2fs -n /dev/nvme0n1

output

Code: Select all

mke2fs 1.46.2 (28-Feb-2021)
Found a gpt partition table in /dev/nvme0n1
Proceed anyway? (y,N) y
/dev/nvme0n1 is apparently in use by the system; will not make a filesystem here!

I have made a full shutdown before and it is not mounted, so i don't understand how it can be "in use".

I tried to give the specific name of the partition, not the whole disk, but i don't know how to do it correctly with nvme, i gave it a number of partition in the end, but it is wrong.

Code: Select all

demo@mx1:~
$ sudo mke2fs -n /dev/nvme0n14
mke2fs 1.46.2 (28-Feb-2021)
The file /dev/nvme0n14 does not exist and no size was specified.

So, now i have to somehow make the system believe the disk is not in use. And i don't know if i should make mke2fs command for the whole disk or just for the partition. And i don't know how to give it the exact name.

UPD.

OK, it is /dev/nvme0n1p3

Also, i have found mdadm command for "stopping" the disk, but i am not quite sure yet how to use it here.

UPD2

$ sudo mke2fs -n /dev/nvme0n1p3
mke2fs 1.46.2 (28-Feb-2021)
/dev/nvme0n1p3 contains a crypto_LUKS file system
Proceed anyway? (y,N) y
Creating filesystem with 21504000 4k blocks and 5382144 inodes
Filesystem UUID: 1f12a752-da46-4906-8751-78e9fc6bfc48
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000

[JanK]

@j2mcgreg @Adrian

Sorry for the late reply. I have managed to complete the e2fsck command. And it gives me this error.

Code: Select all

demo@mx1:~
$ sudo e2fsck -b 20480000 /dev/nvme0n1p3
e2fsck 1.46.2 (28-Feb-2021)
e2fsck: Invalid argument while trying to open /dev/nvme0n1p3

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

And i tried different backup numbers...

All is lost or something else can be done?

UPD. Looks like when i try to run testdisk util the computer freezes even in LIVE-USB! Dual-boot Win10 works fine.