From: robin_listas@invalid.es   
      
   On 2016-11-27 02:18, Carlos E.R. wrote:   
   > On 2016-11-27 01:16, Heinz Julmy wrote:   
   >   
   >>   
   >> I managed to install it. Don't ask how ... here what I got:   
   >>   
   >> Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 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: DF04D177-16CF-4EA3-A16E-B7D518694CB9   
   >>   
   >> Device         Start       End   Sectors   Size Type   
   >> /dev/sda1       2048    718847    716800   350M EFI System   
   >> /dev/sda2     718848 252749823 252030976 120.2G Microsoft basic data   
   >> /dev/sda3  252749824 252766207     16384     8M BIOS boot   
   >> /dev/sda4  252766208 256974847   4208640     2G Microsoft basic data   
   >> /dev/sda5  256974848 340867071  83892224    40G Microsoft basic data   
   >> /dev/sda6  340867072 500117503 159250432    76G Microsoft basic data   
   >>   
   >>   
   >> gparted show the following though:   
   >>   
   >> /dev/sda1 		ntfs   
   >> /dev/sda2		ntfs   
   >> /dev/sda3 		unknown   
   >> /dev/sda4 		linux-swap   
   >> /dev/sda5		btrfs	/   
   >> /dev/sda6		xfs	/home   
   >>   
   >> So this looks good, right?   
   >   
   > Yes, it does look good.:-)   
   >   
   >> Althought I'm still not able to boot with   
   >> windows 10 as an option ... but I can live with that as Leap 42.2 seems   
   >> to be pretty stable.   
   >   
   > Another day I'll try to help you boot Windows from there, but today I   
   > can't, too busy. Ping me here if I forget in two days.   
   >   
      
   You have to edit /grub2/custom.cfg and add entries similar to these:   
      
   Watch out for line wrap: I can't send long lines on usenet.   
      
   menuentry 'gpt five' {   
       insmod part_gpt   
       insmod ext2   
       set root='hd0,gpt5'   
       if search --no-floppy --fs-uuid --set=root   
   e99d9dcb-869d-4a24-94cf-cba32f169b8d ; then   
           chainloader +1   
       else   
           echo Could not find this OS instance, will not boot (gpt5)   
           sleep 1   
       fi   
   }   
      
      
   menuentry 'msdos one'  {   
       insmod part_gpt   
       insmod ext2   
       set root='hd1,msdos1'   
       if search --no-floppy --fs-uuid --set=root   
   7cb39bb9-10da-4add-8eec-38306ce5e05f ; then   
           chainloader +1   
       else   
           echo Could not find this OS instance, will not boot (msdos1)   
           sleep 1   
       fi   
   }   
      
   The first one is for a gpt partitioned disk, the second is for an msdos   
   partitioned disk.   
   It is important to write the correct uuid for the partition you want to   
   boot. Check:   
      
   cer@Telcontar:~> l /dev/disk/by-uuid/ | grep   
   e99d9dcb-869d-4a24-94cf-cba32f169b8d   
   lrwxrwxrwx 1 root root  10 Nov  7 10:47   
   e99d9dcb-869d-4a24-94cf-cba32f169b8d -> ../../sdb5   
   cer@Telcontar:~>   
      
   lrwxrwxrwx 1 root root  10 Nov  7 10:47   
   7cb39bb9-10da-4add-8eec-38306ce5e05f -> ../../sdc1   
      
      
   On the other hand, the "set root='hd0,gpt5'" is not definitive, but like   
   a hint for the search that comes next.   
      
      
      
   You have to try to boot /dev/sda2 on a gpt disk. So it will be   
   'hd0,gpt2'. The UUID you have to find out, it is easy.   
      
   My entries above are intended to boot a Linux partition containing   
   another grub, so the "insmod ext2" entry will have to be "insmod ntfs"   
   in your case.   
      
   So, your entry should be like this, except for the UUID that you have to   
   add:   
      
   menuentry 'Windows' {   
       insmod part_gpt   
       insmod ntfs   
       set root='hd0,gpt2'   
       if search --no-floppy --fs-uuid --set=root Your_UUID ; then   
           chainloader +1   
       else   
           echo Could not find this OS instance, will not boot (Windows)   
           sleep 1   
       fi   
   }   
      
      
   After doing that edit you have to run:   
      
   grub2-mkconfig -o /boot/grub2/grub.cfg   
      
      
   Then try to boot Windows. If it fails, take a notice of the exact error   
   message and post it.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)