[FATAL] cbm (../src/bootman/bootman.c:L518): Cannot determine boot device
I am pretty new. I dont know whats wrong..

I did:
sudo mount /dev/sda1 /boot

which kind of did fix it, but i am not sure if what i did is optimal

Normal way is acording to the faq

Sudo su
mkdir /mike

mount /dev/SolusSystem/Root /mike
mount --types proc /proc /mike/proc
mount --rbind /dev /mike/dev
mount --rbind /sys /mike/sys
mount --make-rslave /mike/dev
mount --make-rslave /mike/sys
chroot /mike

mike is the name of my choice.

    MikeK61 so what do i do next, i did this on live cd but still am not able to update clr-boot-manager

      Do you still get the same error ?
      More informations would help maybe.

      Make sure you are running the live USB with same boot config as your installation.
      I once booted in efi mode while my install is legacy and i got the same error.

        MikeK61 Yeah, it still has the same error. my device is efi. But i am not sure, how i can change the boot method. The efi partition is set up on my install though

          Do you have any files in /etc/kernel?

            pomon after tinkering a bit my device stopped booting so I transferred to endeavor os. I think its a problem with my device not being accepted by the installation. There were some files on the kernel directory, do you think it might be fixed? Ill be happy to reinstall if it works.

              I'm not clear about what you're trying to accomplish. In my experience, most problems like what you're describing involve new users trying to create a dual-boot situation that involves Solus and Windows. That can be done, but it's tricky to do right and easy to get wrong. Is that your intention, or is it something else?

              A simple installation of Solus using the Calamares installer on the Solus 4.5 .ISO files is very straightfoward, and really hard to get wrong. If you're trying to do something else, anyone trying to help you will need to know what that something else is. This thread doesn't include that information (yet).

              Echoing what wetgeek said, what are you trying to accomplish? Why are you trying to "update" clr-boot-manager? We need to know what the goal is before anyone can give you any useful advice.