Probe #7ca76c0d32 of Alienware m16 R1 AMD
Log: fdisk
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: PC SN810 NVMe WDC 1024GB
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: --
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 411647 409600 200M EFI System
/dev/nvme0n1p2 411648 673791 262144 128M Microsoft reserved
/dev/nvme0n1p3 673792 272334847 271661056 129.5G Microsoft basic data
/dev/nvme0n1p4 1957644288 1959921663 2277376 1.1G Windows recovery environment
/dev/nvme0n1p5 1959921664 1997322239 37400576 17.8G Windows recovery environment
/dev/nvme0n1p6 1997324288 2000408575 3084288 1.5G Windows recovery environment
/dev/nvme0n1p7 272334848 1953449983 1681115136 801.6G Linux filesystem
/dev/nvme0n1p8 1953449984 1957644287 4194304 2G Linux swap
Partition table entries are not in disk order.
Disk /dev/sdb: 931.51 GiB, 1000204885504 bytes, 1953525167 sectors
Disk model: Expansion HDD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: --
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 1953523711 1953521664 931.5G 83 Linux
GPT PMBR size mismatch (9624191 != 30322687) will be corrected by write.
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
The backup GPT table is not on the end of the device.
Disk /dev/sda: 14.46 GiB, 15525216256 bytes, 30322688 sectors
Disk model: USB DISK 2.0
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: --
Device Start End Sectors Size Type
/dev/sda1 64 9613459 9613396 4.6G Microsoft basic data
/dev/sda2 9613460 9623527 10068 4.9M EFI System
/dev/sda3 9623528 9624127 600 300K Microsoft basic data