On Sun, Dec 27, 2015 at 12:48 AM, Antonio M
<antonio.montagnani(a)gmail.com> wrote:
/dev/sda1 2048 1fdisk -l
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
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: 0x8bb03702
Dispositivo Avvio Start Fine Settori Size Id Tipo
/dev/sda1 2048 16371711 16369664 7.8G b W95 FAT32
/dev/sda2 * 16371712 32741375 16369664 7.8G c W95 FAT32 (LBA)
/dev/sda3 32741376 976773167 944031792 450.2G 83 Linux
1. This is an MBR partitioned system.
2. It has a 3rd partition, the type code is 83 (linux), so something
created that. There is no free space.
3. Why do you think this is a UEFI system? If you boot the install
media, what results do you get for 'efibootmgr' ?
4. This is an unusual installation of Windows because the first two
partitions are identically sized, and are reported as FAT32 with type
codes 0B and 0C, rather than type code 07 NTFS. Also 7.8G is much
larger than a typical Windows system volume, and is also much smaller
than a typical Windows boot volume.
So this makes me wonder if sda3, 450G is actually Windows, and somehow
accidentally its type code got changed. You can use 'blkid' to find
out what the actual file system is on that partition. If it's NTFS,
then the type code is wrong and it needs to be changed to 07.
But the main issue here is whether the system really is UEFI. And if
Windows came pre-loaded or not. If it's UEFI, then the CSM-BIOS has
been enabled (presents a faux legacy BIOS to the OS) because the
Windows installer only uses MBR on systems with BIOS. It only uses GPT
on systems with UEFI. Therfore the fact this system has an MBR
partitioned disk means the firmware is presenting BIOS to the
installer environment.
--
Chris Murphy