I’m agree with you.
I leave here an example of the command out in case someone have the same problem:
root@rigXXXXX:/# fdisk -l │····················
Disk /dev/nvme0n1: 953.9 GiB, 1024209543168 bytes, 2000409264 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 │····················
Disklabel type: gpt │····················
Disk identifier: XXXXXXX-B8F8-4D7F-XXXXXXXXXXXX │····················
│····················
Device Start End Sectors Size Type │····················
/dev/nvme0n1p1 2048 1085439 1083392 529M Windows recovery environment │····················
/dev/nvme0n1p2 1085440 1290239 204800 100M EFI System │····················
/dev/nvme0n1p3 1290240 1323007 32768 16M Microsoft reserved │····················
/dev/nvme0n1p4 1323008 2000408575 1999085568 953.2G Microsoft basic data │····················
│····················
│····················
Disk /dev/sda: 57.3 GiB, 61530439680 bytes, 120176640 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 │····················
Disklabel type: gpt │····················
Disk identifier: XXXXXXX-FEA6-4E82-8270-XXXXXX │····················
│····················
Device Start End Sectors Size Type │····················
/dev/sda1 2048 43007 40960 20M Microsoft basic data │····················
/dev/sda2 43008 45055 2048 1M BIOS boot │····················
/dev/sda3 45056 126975 81920 40M EFI System │····················
/dev/sda4 126976 120176606 120049631 57.2G Linux filesystem
Regards,