On 2016-02-02 17:25, Hans de Faber wrote:
Read in the link "GPT and protective MBR". http://www.system-rescue-cd.org/Sysresccd-Partitioning-EN-The-new-GPT-disk-l...
Thanks! That explains the situation. And using "parted" as the article does gives an important bit of information that fdisk doesn't: the "Flags" column. One partition has "legacy_boot". linux-leap421-r:~ # parted /dev/sda print Model: ATA VMware Virtual S (scsi) Disk /dev/sda: 2000GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 2 1049kB 15.7GB 15.7GB ext4 legacy_boot 1 15.7GB 31.5GB 15.7GB linux-swap(v1) 3 31.5GB 83.9GB 52.4GB reiserfs 4 83.9GB 83.9GB 10.5MB primary bios_grub 5 83.9GB 136GB 52.4GB reiserfs linux-leap421-r:~ # fdisk -l /dev/sda Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 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: 4C81D390-4C41-... Device Start End Sectors Size Type /dev/sda1 30722048 61442047 30720000 14.7G Linux swap /dev/sda2 2048 30722047 30720000 14.7G Microsoft basic data /dev/sda3 61442048 163842047 102400000 48.8G Microsoft basic data /dev/sda4 163842048 163862527 20480 10M BIOS boot /dev/sda5 163862528 266262527 102400000 48.8G Microsoft basic data Partition table entries are not in disk order. linux-leap421-r:~ # -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)