Upgrade to UEFI dualboot LEAP & W10

This is my main box, so I’d like to get this right at first try.

Current system:
Dual boot oS 13.2 & W7 msdos system disk (SSD)
Two gpt data disks, one msdos data disk (HDDs)

Backups to do:
a) Full (?) system SSD imaging to NTFS external drive with Macrium Reflect winPE live disk.
b) Same to EXT4 data disk with Clonezilla live disk.
c) copy /home to one of the data disks.

Upgrade to LEAP & W10 x64 retail on same SSD:

  1. Wipe SSD and create gpt partition table. Don’t touch data disks, one of which has a NTFS D: partition (steam games, yeah!)

  2. Recreate partitions as before, increasing root (sda6) to 30 GB (10 GB taken from windows sdb) for btrfs. Current partitioning:

# fdisk -l /dev/sda

Disco /dev/sda: 232,9 GiB, 250059350016 bytes, 488397168 setores
Unidades: setor de 1 * 512 = 512 bytes
Tamanho de setor (lógico/físico): 512 bytes / 512 bytes
Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes
Tipo de rótulo do disco: dos
Identificador do disco: 0x1f794da2

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1            2048    206847    204800   100M  7 HPFS/NTFS/exFAT
/dev/sda2          206848 141754367 141547520  67,5G  7 HPFS/NTFS/exFAT
/dev/sda4  *    188950528 488396799 299446272 142,8G  5 Extended
/dev/sda5       188952576 193146879   4194304     2G 82 Linux swap / Solaris
/dev/sda6       193148928 235091967  41943040    20G 83 Linux
/dev/sda7       235094016 486752255 251658240   120G 83 Linux

Note boot flag on /sd4.
New partitioning, taken from a similar setup, with changes in bold:

# fdisk -l /dev/sda
Disco /dev/sda: 232,9 GiB, 250059350016 bytes, 488397168 setores                                                                                             
Unidades: setor de 1 * 512 = 512 bytes
Tamanho de setor (lógico/físico): 512 bytes / 512 bytes
Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes
Tipo de rótulo do disco: **gpt**
Identificador do disco: (same or new one)

Dispositivo    Início       Fim   Setores Tamanho Tipo
/dev/sda1        2048    923647    921600    450M Windows recovery <-- new
/dev/sda2      923648   1126399    202752     99M Sistema EFI <--changed
/dev/sda3     1126400   1159167     32768     16M Microsoft reservado <-- new
/dev/sda4     1159168 210874367 209715200     **75G** Microsoft dados básico
/dev/sda5   210874368 227651583  16777216      **8G** Linux swap
/dev/sda6   227651584 301051903  73400320     **30G** Linux sistema de arquivos <-- root
/dev/sda7   301051904 488396799 187344896    120G Linux sistema de arquivos <-- /home

Note there’s no boot flag in this setup.

  1. Set boot to UEFI first in UEFI BIOS, enable secureboot. (question: do I have to enable legacy to access the msdos data disk?)

  2. Install W10 on predefined partitions (advanced install, I think it’s called). If W10 takes all SDD, then shrink C: (sda4) and repartition again, as above, and boot in W10 to see if shrink didn’t create any problems

  3. Disable W10 fast boot, or whatever is the name.

  4. Install LEAP to the correspondent partitions, leaving the bootloader options as default, which I suppose will not set any boot flag due to gpt/UEFI.

Do you see any problems with this setup?


Re 6) The nvram contains the default ‘boot’ order, so after the install it should put openSUSE first in the order… eg;

/dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi

efibootmgr -v
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,3002,0001,0000,2001,2002,2004
Boot0000* openSUSE    HD(1,GPT,4940529e-67c8-4438-a9b1-8c270332f3e3,0x800,0x82000)/File(\EFI\opensuse\grubx64.efi)RC
Boot0001* Windows Boot Manager    HD(1,GPT,4940529e-67c8-4438-a9b1-8c270332f3e3,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.}...e................
Boot0002* opensuse-secureboot    HD(1,GPT,4940529e-67c8-4438-a9b1-8c270332f3e3,0x800,0x82000)/File(\EFI\opensuse\shim.efi)
Boot2001* EFI USB Device    RC
Boot3001* Internal Hard Disk or Solid State Disk    RC
Boot3002* Internal Hard Disk or Solid State Disk    RC

sda      8:0    0  29.1G  0 disk 
├─sda1   8:1    0   260M  0 part /boot/efi
├─sda2   8:2    0    16M  0 part 
├─sda3   8:3    0  20.9G  0 part 
└─sda4   8:4    0     8G  0 part [SWAP]
sdb      8:16   0 111.8G  0 disk 
├─sdb1   8:17   0    40G  0 part /
└─sdb2   8:18   0  71.8G  0 part /data

du -sh /boot/efi/
29M    /boot/efi/

The above system has a 32GB eMMC, I just stuck an SSD in as well, will replace with one SSD at some point. With 100M fro the efi partition should be fine, I set mine to 260M incase i want to move to multiboot.

Hi, malcolm,

The “new” partitioning is just like my secondary (backup) work machine. I installed W10 in it and then LEAP and grub2 worked as expected. There was no need edit bootloaders - which are kind of cryptic to me. So I’m expecting it to go the same way.

Do you see any other possible issue with my plan as outlined in my original post? Thanks!

For reference: if someone want to use Macrium for backup, note that although if purportedly support EXT files systems, it only writes the image to NTFS - a consequence of them dropping the linux liveCD. Obviously this is irrelevant when cloning disk-to-disk. FWIW, I found Macrium quite easy to use, and Clonezilla harder but it gives you more control.

Also, MR image is a single 63.5 GB, while Clonezila’s is a folder structure with 3.8 GB split files, totaling 57.9 GB. Probably due to higher default compression.

The 250GB imaged SSD is about 94 GB full, in case anyone is interested in statistics.

But they have different mobos (Gygabyte and Asus), an consequently different UEFI BIOS that may complicate things. I’ve better write down the updated box BIOS configuration and see if there is anything different related do UEFI/Secureboot/Legacy before installing.

Maybe look at 40GB for / rather than 30? Snapper is off by default, so 30GB would be fine. Aside from that you should be fine.

I only installed WinX on the eMMC because I could :wink: I might use it to run Nascar raceview, but that would be the only thing.