There are a few posts that deal with this (though no idea why not just use USB.......):

because the last time I used a liveUSB ( kubuntu ), it messed up by system. I have Lenovo ideapad 330-15ARR with UEFI support, and I once created USB using Baleno Etcher, it did not get detected on the reboot, hence I changed the settings in F12, then reboot Kubuntu booted but it got stuck in between - then I rebooted my installed bootloader gone !

I had to use a rescue USB to reload the bootloader entries, costed me 3 days to trial - error various rescue ISOs. Since my laptop is an everyday work machine - I dont want to take up risks using the LiveUSB. The boot from HDD seems safe method for me 😉

However, thank you for the swift reply. I have asked this same question in Fedora( to install fedora) forum and one week no reply, same to openSuse they asked me to try live USB - seems like KaOS community is more alive same as Manjaro. (thumbs up) 😀

I will check the links you provided and try it out tomorrow and update back.

thanks again

demm

thank you, I am using MXLinux as the host OS now. I will try to install this in MXLinux and burn the LiveUSB and try

    Hello,

    here is my first entry to /etc/grub.d/40_custom

    menuentry "KaOS iso" {
    set isoname="kaos-2020.05-x86_64.iso"
    set isofile="/boot/images/kaos-2020.05-x86_64.iso"
    search --no-floppy -f --set=root $isofile
    probe -u $root --set=abc
    set pqr="/dev/disk/167f9d81-e889-44c6-bd68-9f1c19c759d0/$abc"
    loopback loop (hd0,2)$isofile
    probe -l (loop) --set=klabel
    linux (loop)/kdeos/boot/x86_64/kdeosiso img_dev=$pqr img_loop=$isofile kdeosisobasedir=kdeos kdeosisolabel=$klabel verbose
    initrd (loop)/kdeos/boot/x86_64/kdeosiso.img
    }
    now I got the below error ( pls refer screenshot ) https://i.imgur.com/Ap2sIRO.jpg
    https://i.imgur.com/Ap2sIRO.jpg

    so I changed the boot entry below again
    `menuentry "KaOS ISO from HDD" {

    set isofile="/boot/images/kaos-2020.05-x86_64.iso"

    loopback loop (hd0,2)$isofile

    linux (loop)/kdeos/boot/x86_64/kdeosiso kdeosisolabel=KaOS-2020 img_dev=/dev/sda2 img_loop=$isofile

    initrd (loop)/kdeos/boot/x86_64/kdeosiso.img
    }
    `

    then I got the below error
    https://i.imgur.com/vEDboaZ.jpg
    https://i.imgur.com/vEDboaZ.jpg

    I am not sure what to do next - I will try to install ISOwriter in my host linux ( MXLinux)

    I assume your isofile is in (hd0,2)/boot/images/
    You are not using the correct parameters.
    You used, for example,
    loopback loop (hd0,2)$isofile
    not loopback loop $isofile

    And your isofile name "kaos-2020.05-x86_64.iso"
    Are you sure it is not "KaOS-2020.05-x86_64.iso" ??

    You cannot be slipshod and expect it will auto-correct for you.

    You cannot be slipshod and expect it will auto-correct for you.
    Yes, I figured out that I made a mistake there. I corrected and tried again but it did not get well. The booting fell into a shell after waiting 30 seconds as its mentioned here

    then I tried the steps mentioned there

     mkdir /mnt

mkdir /iso

mount /dev/sda2 /mnt

mount -o loop /mnt/boot/images /KaOS-2020.05-x86_64.iso /iso

exit

    now it worked, I could boot into the live system and I installed the KaOS. kool but some things I like to mention, that once I rebooted the machine, my other grub menu entries are gone !

    I have MXLinux installed in my sda2 now I have no option to boot there. Any idea how to ?

    NOTE:

    And your isofile name "kaos-2020.05-x86_64.iso"
    Are you sure it is not "KaOS-2020.05-x86_64.iso" ??

    I actually renamed the ISO file into all smaller cases then only I used it on my menu entry but yes It did not work anyway, so I reverted all back.

    now, please help me to how do I get my other OS boot entry back

    You installed in UEFI or legacy BIOS mode? In case of the former, you have an extra bootloader in your UEFI menu, as mentioned before KaOS uses systemd-boot for UEFI, not grub.
    So to get your grub loader, go to your systems UEFI settings and set a different bootloader or use boot key (usually F12 or F11, check your motherbaord for correct key) and select the bootloader.

      demm You installed in UEFI or legacy BIOS mode? I

      [root@jeevan-81d2 jeevan]# [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS
UEFI

      I guess I installed KaOS on UEFI mode ?

      demm So to get your grub loader, go to your systems UEFI settings and set a different bootloader or use boot key (usually F12 or F11, check your motherbaord for correct key) and select the bootloader.

      I am a bit confused here but I will try some thing with system settings now.

      • demm replied to this.

            codingtalkie I am a bit confused here but I will try some thing with system settings now.

            You need to enter your UEFI BIOS (nothing can be done for this in Plasma system settings, if that is what you refer to).

              What demm refers is the function key to use when we start the computer, not at the booted OS.
              For example, F2 usually takes us to the bios set up.
              There are other F keys that allow us to select the boot options, usually one of F8, F10, F11 or F12.
              If you don't see this option, it can be enabled at bios-setup (usually F2).
              Then you can select the boot option for PCLinuxOS.

              If you still have problems, when booted at KaOS, at its terminal, print out output of

              sudo parted -l
efibootmgr -v
sudo blkid
cat /etc/fstab

              parted -l --> small 'L', not 'one', output of all disks
              explain PClinux OS partitions

              Hello All,

              thanks for the replies to help me. I have solved issue but changing the boot order using efibootmgr
              so I booted to my other LINUX ( MX Linux) and installed grub-efi which recreated the boot entries including KaOS. Now I can boot into any OS I need to,

              Anyway, I am using KaOS as the new daily work distro, its really a kool distro 😃