This is the partition table of hddimg, which seems to be derived from the build host. The image boots OK when deployed to a NUC target, but we'll need to figure out if this is something that can cause issues in the future. fdisk -l core-image-minimal-intel-corei7-64-20161207173434.hddimg Disk core-image-minimal-intel-corei7-64-20161207173434.hddimg: 28.9 MiB, 30308352 bytes, 59196 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: dos Disk identifier: 0x20ac7dda Device Boot Start End Sectors Size Id Type core-image-minimal-intel-corei7-64-20161207173434.hddimg1 ? 3224498923 3657370039 432871117 206.4G 7 HPFS/NTF core-image-minimal-intel-corei7-64-20161207173434.hddimg2 ? 3272020941 5225480974 1953460034 931.5G 16 Hidden F core-image-minimal-intel-corei7-64-20161207173434.hddimg3 ? 0 0 0 0B 6f unknown core-image-minimal-intel-corei7-64-20161207173434.hddimg4 50200576 974536369 924335794 440.8G 0 Empty
Does hddimg have partition table at all?
Here is the output of fdisk -l for qemux86-64 machine: $ /sbin/fdisk -l ./tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-2016120223*.hddimg Disk ./tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20161202233134.hddimg: 25.7 MiB, 26892288 bytes, 52524 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: dos Disk identifier: 0x00000000
JFYI: There is a proposal and ongoing activity of getting rid of hddimg: http://lists.openembedded.org/pipermail/openembedded-architecture/2016-December/000359.html
hddimg images infer their partition table from the partition table of the host on which they are generated. Closing this as we are removing hddimg.