Last week I ran updates on the Solus 4.4 system: there were over 360 items to update and the system ended up with a black screen. I has to do a hard power off. When I tried to power up, the Solus entry in grub shows kernel 6.5.3-256 but when I select it, it immediately that it cant find the boot sector. I can go in recovery mode and select the 6.4.11-251 kernel and it all works fine. I even ran updates and all completed normally however it did not try to update the kernel.

Out of curiosity, I read the grub.cfg file and there is no entry for kernel 6.5.3-256 however there is an entry for kernel 6.5.9-262 that is not showing in the grub menu. Is this recoverable without destroying the grub menu that also contains a Linux Mint entry?

hello, try sudo eopkg it --reinstall linux-current to reinstall the current version of the kernel, then try sudo clr-boot-manager update reboot and check again.

    (sorry I answer a wrong topic, and I can't delete this message)

      WetGeek
      As far as I know we cannot edit or delete our own posts once someone has read them.

          SOLUSfiddler As far as I know we cannot edit or delete our own posts once someone has read them.

          Indeed. I don't agree with the editing, as someone else may have accessed it even before we get a chance to notice a typo after we've posted it. That's happened to me. But I can understand it. The mods are afraid that someone will write something, then change it to say something entirely different, instead of just fixing a typo or improving a word choice. It's just hard for me to think of our forum as being that adversarial.

          But not being able to delete a post if we find it to be no longer relevant, or in the present case, accidentally posted to the wrong thread, seems a little harsh. We've all made innocent mistakes from time to time, and should be allowed to correct them.

              WetGeek all true. also would like to have back the handful of times I was helping a user troubleshoot and it was self-solved or another member solved it before I could hit 'post reply.

              WetGeek But not being able to delete a post if we find it to be no longer relevant, or in the present case, accidentally posted to the wrong thread, seems a little harsh. We've all made innocent mistakes from time to time, and should be allowed to correct them.

              yeah maybe a new method will shake out eventually. when the fubar stuff you mention ^^ happens and I'm helpless to clarify, I often have to create whole new reply backtracking and explaining myself. I try to limit the situations I put myself in but like you say it happens.

                  nolan
                  I tried both commands and while it shows that a new current kernel is loaded, this version does not show in Grub.

                  _**Total size of package(s): 141.41 MB
                  Downloading 1 / 1
                  Package linux-current found in repository Solus
                  linux-current-6.5.11-263-1-x86_64.eopkg [cached]
                  Installing 1 / 1
                  linux-current-6.5.11-263-1-x86_64.eopkg [cached]
                  Installing linux-current, version 6.5.11, release 263
                  Extracting the files of linux-current
                  Installed linux-current
                  [✓] Syncing filesystems success
                  [✓] Updating clr-boot-manager success
                  [✓] Running depmod on kernel 6.5.11-263.current

                  sudo clr-boot-manager update
                  Generating grub configuration file ...
                  Found Linux Mint 21.2 Victoria (21.2) on /dev/sda5
                  done_

                    nolan
                    I must admit that it was a bit frustrating to see the posting switched to a different topic with no relevance to my problem. Replying to the post after that got nowhere.

                    However, I'm happy to report that the problem has disappeared seemingly on its own after a few updates under the old kernel. Your suggestions did not work immediately but could not have hurt the system and it's good knowledge for me in the future.