XPost: uk.comp.os.linux   
   From: nospam@needed.invalid   
      
   On 4/16/2024 9:46 AM, Java Jive wrote:   
   > On 16/04/2024 14:05, Carlos E.R. wrote:   
   >> On 2024-04-16 14:32, Java Jive wrote:   
   >>> On 16/04/2024 12:50, Carlos E.R. wrote:   
   >>>> On 2024-04-16 00:29, Paul wrote:   
   >>>>> Remember - these things have folders in ESP, a "Ubuntu" folder, a   
   "Windows" folder.   
   >>>>   
   >>>> I think he is booting in traditional model aka legacy, ie, no ESP.   
   >>>   
   >>> Correct.   
   >>>   
   >>> As indicated in another post, I have solved the problem, which was caused   
   by the two partitions having identical GUIDs, the W10 being an in-place   
   upgrade of the W7 one.  Changing the partition GUID of the W10 partition   
   resolved the problem.   
   >>   
   >> I should have noticed it:   
   >>   
   >>        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1   
   --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  C00A7FAA0A7F9BDA   
   >>   
   >>        search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos2   
   --hint-efi=hd0,msdos2 --hint-baremetal=ahci0,msdos2  C00A7FAA0A7F9BDA   
   >   
   > Arguably, so should I!  However, at the time of my OP I didn't know enough   
   about GRUB to realise those numbers were the GUIDs of the partitions.  It was   
   J.O.Aho's remark, on first reading apparently insignificant, that later came   
   back to me, causing    
   me to investigate further and so realise that they were the GUIDs of the   
   partitions involved.   
      
   And is that really a GUID ?   
      
   I've seen several lengths of disk identifier Linux uses   
   from Windows stuff, and it's not clear how it   
   parses or understands things like that. Or for that   
   matter, what generic term we should use for the identifier.   
      
   To me, it seems Linux does not get 128 bit numbers from Legacy Windows   
   for identifiers, the numbers tend to be 64 bit or 32 bit (DiskID).   
   At least I can understand the DiskID one, because I've seen it   
   in a hex editor.   
      
   With GPT, both the partition type and the partition identifier,   
   they could be 128 bit numbers (disktype can show you those, maybe   
   gparted as well). Then the formatting would look like a GUID.   
      
   Partition 3: 118.7 GiB (127481675776 bytes, 248987648 sectors from 239616)   
     Type Basic Data (GUID A2A0D0EB-E5B9-3344-87C0-68B6B72699C7)  <=== fixed   
   declaration   
     Partition Name "Basic data partition"   
     Partition GUID 6A16D60B-3608-4140-891C-792DF2C72ABD          <=== random   
   assignment of some sort   
     NTFS file system   
       Volume size 118.7 GiB (127481675264 bytes, 248987647 sectors)   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)