[re-sending reply to the list.] On Fri, May 11, 2018 at 12:04 AM Pascal Hambourg <[email protected]> wrote:
> Le 10/05/2018 à 21:27, David Collier a écrit : > > >> fdisk -l > > > > $ sudo fdisk -l /dev/sdc > > This is not what I asked for. Please provide the complete output. > > vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv # fdisk -l Disk /dev/sda: 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: 209A9DF6-5725-474B-97D4-14C25166D289 Device Start End Sectors Size Type /dev/sda1 2048 1800366287 1800364240 858.5G Microsoft basic data Disk /dev/sdb: 167.7 GiB, 180045766656 bytes, 351651888 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: 0x0009f280 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 351651887 351649840 167.7G 83 Linux Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 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: AF6118F0-6BF8-460C-9622-F5BDA7EE3204 Device Start End Sectors Size Type /dev/sdc1 2048 1023999 1021952 499M Windows recovery environment /dev/sdc2 1024000 1226751 202752 99M Microsoft basic data /dev/sdc3 1226752 1259519 32768 16M Microsoft reserved /dev/sdc4 1259520 976773119 975513600 465.2G Microsoft basic data Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 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: gpt Disk identifier: 4EC67F98-819F-4573-9ED3-583ABCD2E641 Device Start End Sectors Size Type /dev/sdd1 34 262177 262144 128M Microsoft reserved /dev/sdd2 264192 3907028991 3906764800 1.8T Microsoft basic data Partition 1 does not start on physical sector boundary. Disk /dev/sde: 1.8 TiB, 2000398934016 bytes, 3907029168 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: gpt Disk identifier: B5FAA2AB-CE9B-422C-A0A3-2DD67CF87239 Device Start End Sectors Size Type /dev/sde1 2048 3828889599 3828887552 1.8T Microsoft basic data /dev/sde2 3828889600 3907028991 78139392 37.3G Linux swap # blkid /dev/sde2: UUID="0ff2d81f-26a7-4a95-a34f-2a6b98929398" TYPE="swap" PARTLABEL="lswap" PARTUUID="879aed61-93a4-44fd-accb-1a3e2c25fee9" /dev/sda1: UUID="cb18129b-aa83-4087-b545-fe6915780e2f" TYPE="ext4" PARTUUID="9b1218cb-83aa-8740-b545-fe6915780e2f" /dev/sdb1: UUID="833ad30f-22ca-4b34-bef2-c6315dd54f81" TYPE="ext4" PARTUUID="0009f280-01" /dev/sdc1: LABEL="Recovery" UUID="A61C89D91C89A541" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="a904221f-f5dc-4dc9-a6e2-ba1c18ae2221" /dev/sdc2: SEC_TYPE="msdos" UUID="A879-04E5" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="2987d536-85c4-4a68-ad8a-7c880054bda9" /dev/sdc4: UUID="E8AA9579AA9544CA" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="e8341881-83e9-4c6e-83c3-d9ceeab5589d" /dev/sdd2: LABEL="Second WD" UUID="72B88904B888C7D5" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="73719a02-e82b-4535-99dd-a48da5f5eeac" /dev/sde1: UUID="9b7e65fa-afd7-4611-95c3-ef5ac8db0d2b" TYPE="ext4" PARTUUID="8973b964-4d68-4d6f-a469-f42b402bdef0" /dev/sdc3: PARTLABEL="Microsoft reserved partition" PARTUUID="f2ddae9f-0952-49fe-9503-4162a0fddaef" /dev/sdd1: PARTLABEL="Microsoft reserved partition" PARTUUID="fe9f5b17-1bf7-4e60-8f38-d61b5084d68c" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [...] > This means that the system did not boot in EFI mode. It explains why > os-prober cannot detect Windows EFI boot loader. > Check what's in /boot and /boot/grub : I guess there is no /boot/efi > directory nor /boot/grub/x86_64-efi, but there is a /boot/grub/i386-pc > directory. > yes, these guesses are correct. So, is there a way to make grub include windows 10 option in this case? How come the BIOS/UEFI, (whatever my PC's firmware is that is :) can boot both, but grub can not? thank you again for looking into this, -dc _______________________________________________ > Help-grub mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/help-grub > _______________________________________________ Help-grub mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-grub
