After some tries, can I maybe describe the situation better.
My thy:
Disconnect disk with Ubuntu and reconnect disk with Win8
Ones started Win8 and replace again the (Win8 750 GiG HDD) disk with Kubuntu disk (128 GiG SD) have I the same result
as just after the installation with USB-Stick in persistenz-modus.
Practically, no Kubuntu-entry in UEFI-BIOS any-more.
In the EFI/ESP-partition of the disk is the folder Kubuntu with grubx64.efi but (as said) no possibility to start Ubuntu/Kubuntu anymore.
To solve the problem, I made following:
- Chroot the installed system
- Install "efibootmgr" if not yet done &
- Setup manually an entry in UEFI-BIOS.
I cannot say what cause the missing set up of U-Kubuntu-entry in the U-EFI-BIOS...
Is it Uneetbootin or Ubiquity or USB-Creator?
Fact is that after an installation with USB-Stick-Live (with permanence) is no entry in UEFI-BIOS (NVRAM)
The result is a not bootable system
chrooting + installing of efibootmger + manual insert of entry solve the problem
Do someone (else) test (re-encounter) this behavior?
After some tries, can I maybe describe the situation better.
My thy:
Disconnect disk with Ubuntu and reconnect disk with Win8
Ones started Win8 and replace again the (Win8 750 GiG HDD) disk with Kubuntu disk (128 GiG SD) have I the same result
as just after the installation with USB-Stick in persistenz-modus.
Practically, no Kubuntu-entry in UEFI-BIOS any-more.
In the EFI/ESP-partition of the disk is the folder Kubuntu with grubx64.efi but (as said) no possibility to start Ubuntu/Kubuntu anymore.
To solve the problem, I made following:
- Chroot the installed system
- Install "efibootmgr" if not yet done &
- Setup manually an entry in UEFI-BIOS.
I cannot say what cause the missing set up of U-Kubuntu-entry in the U-EFI-BIOS...
Is it Uneetbootin or Ubiquity or USB-Creator?
Fact is that after an installation with USB-Stick-Live (with permanence) is no entry in UEFI-BIOS (NVRAM)
The result is a not bootable system
chrooting + installing of efibootmger + manual insert of entry solve the problem
Do someone (else) test (re-encounter) this behavior?
Thanks for your attention.