On Tue, Apr 19, 2016 at 10:53 AM, <m.roth@xxxxxxxxx> wrote:
> Jerry Geis wrote:
>> Thanks...
>> I added the "insmod ntfs" re-ran config no boot...
>> I change the hd1 to hd3 re-ran config no boot...
>> This is what my partition table looks like.
>> # Start End Size Type Name
>> 1 2048 534527 260M EFI System EFI system
> partition 2 534528 567295 16M Microsoft reser
> Microsoft reserved
>> partition
>> 3 567296 525326335 250.2G Microsoft basic Basic data
> partition 4 998166528 1000214527 1000M Windows recover Basic data
> partition 5 525326336 525330431 2M BIOS boot parti
>> 6 525330432 965732351 210G Microsoft basic
>> 7 965732352 982509567 8G Linux swap
>> Thoughts?
>
> I haven't been following this, and perhaps I'm being dense... but I see
> BIOS boot partition, and I see 8G of Linux swap... where's the Linux /boot
> and / partitions?
>
> mark
CentOS 7 has inherited an old bug/bad design choice by parted
developers, where they decided to use the partition type GUID for
"basic data" that Microsoft came up with, rather than following the
UEFI spec and creating their own partition type GUID for Linux
filesystems. Presumably partition 3 is Windows on NTFS, and partition
6 is a conventional partition with combined /boot / and /home. Just a
guess.
It's not a bad idea to get gdisk on the system, and change the type
code for the linux partition to gdisk code 8300, which translates to
partition type GUID 0FC63DAF-8483-4772-8E79-3D69D8477DE4. Windows 10
will ignore this, where at least Windows 8 and older invited the user
to format anything with the "basic data" GUID that had a file system
it didn't recognize.
--
Chris Murphy
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
