On Wed, Jan 3, 2024 at 2:24 PM Richard Rosner <rich...@rosner-online.de> wrote:
> So, since for whatever reason Grub seems to be broken beyond repair, > I am not sure what you mean by "broken beyond repair." I have no issues with Grub on Debian 12 on AMD64. I had no issues with Grub on Debian 11 or Debian 10 on AMD64 either. I also had no issues upgrading from Debian 11 to Debian 12. Is it possible that you simply have a corrupted hard drive and simply need to reinstall from scratch? You can download a Debian LiveCD for AMD64 from here: https://cdimage.debian.org/debian-cd/current-live/amd64/bt-hybrid/ you can then boot with it and mount your drive and copy your home directory to a USB portable drive. When you reinstall I would create a separate partition for /home. That way in the future you can always reinstall and just tell the system to mount the existing /home partition. > I today tried to just replace it with rEFInd. Installation succeeded > without any trouble. But when I start my system, rEFInd just asks me if I > want to boot with fwupd or with the still very broken Grub. Am I missing > something? Is rEFInd really just something to select between different OSs > (and not just different distributions like Grub can very well do) and then > gives the rest over to their bootloaders or am I missing something so > rEFInd will take over all of Grubs jobs? > On 01.01.24 21:45, Richard Rosner wrote: > > > On 01.01.24 21:20, Richard Rosner wrote: > > > On 01.01.24 20:30, David Wright wrote: > > On Mon 01 Jan 2024 at 19:04:20 (+0100), Richard Rosner wrote: > > On 01.01.24 18:13, David Wright wrote: > I can boot by hand, but since this is all archived anyways and it's > uneccessarily difficult to find some sort of guide how to even do > this, it might as well be a documentation for users having such > troubles in the future. > > Also, besides the way that I have no clue how it would have to look > like to set up a paragraph in the grub.cfg, I simply don't see > anything wrong with it anyways. So I can't even look at the grub > settings files grub.cfg is being generated from to check where the > error lies. > > You append the commands that you used to boot manually with into > /etc/grub.d/40_custom, observing the comments there, and also into > grub.cfg itself at the appropriate place (near the bottom). The > former is so that Grub includes it in any new grub.cfg that you > create. > > Good to know. > > Edit:, never mind. Tried that, it still booted straight to the UEFI BIOS > menu after entering my password. At this point, I'm seriously considering > slapping rEFInd on it and pray that it picks up on everything automatically > and fix the situation. But so should Grub have, besides the fact that I > can't even be entirely sure Grub is to blame and not something else. > > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
