Comment 8 for bug 1871500

Revision history for this message
Michael J. Kidd (linuxkidd) wrote :

Hi Chris,
  Happy to try and help. I wiped the partitions and attempt another install to capture all the data. This was performed with the same installation media. Here's some additional notes:

---- Pre install data:
root@ubuntu:~# fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 953.89 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: SAMSUNG MZVLB1T0HALR-000H1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B5045520-C230-4E78-9C44-7C3E56C1B3C7

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 534527 532480 260M EFI System
/dev/nvme0n1p2 534528 567295 32768 16M Microsoft reserved
/dev/nvme0n1p3 567296 200648424 200081129 95.4G Microsoft basic data
/dev/nvme0n1p4 200648704 201891839 1243136 607M Windows recovery environment
/dev/nvme0n1p5 201893888 813043711 611149824 291.4G Microsoft basic data
/dev/nvme0n1p6 813043712 815140863 2097152 1G Linux filesystem
/dev/nvme0n1p7 815140864 1831622655 1016481792 484.7G Linux filesystem

Notes:
p6 == Original /boot partition from prior install, selecting to format ext4 and use as /boot
p7 == encrypted data partition from prior Fedora 31 installation, keeping for re-use.
  -- I'll add this to crypttab / fstab later

---- Post crash data:
root@ubuntu:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0 0 953.9G 0 disk
├─nvme0n1p9 259:1 0 15.3G 0 part
│ └─nvme0n1p9_crypt 253:1 0 15.2G 0 crypt [SWAP]
├─nvme0n1p1 259:9 0 260M 0 part
├─nvme0n1p2 259:10 0 16M 0 part
├─nvme0n1p3 259:11 0 95.4G 0 part
├─nvme0n1p4 259:12 0 607M 0 part
├─nvme0n1p5 259:13 0 291.4G 0 part
├─nvme0n1p6 259:14 0 1G 0 part
├─nvme0n1p7 259:15 0 484.7G 0 part
└─nvme0n1p8 259:16 0 65.2G 0 part
  └─nvme0n1p8_crypt 253:0 0 65.2G 0 crypt

root@ubuntu:/# mount /dev/mapper/nvme0n1p8_crypt /target/
NTFS signature is missing.
Failed to mount '/dev/mapper/nvme0n1p8_crypt': Invalid argument
The device '/dev/mapper/nvme0n1p8_crypt' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

root@ubuntu:/# mount -t ext4 /dev/mapper/nvme0n1p8_crypt /target/
mount: /target: wrong fs type, bad option, bad superblock on /dev/mapper/nvme0n1p8_crypt, missing codepage or helper program, or other error.