System's bricked for 72 hrs after last update (boots into bios)

I guess, you guys don’t remember. A few months ago(maybe during spring), grub was breaking the boot process regularly for a lot of people, after updates. At some point I got fed up with not being able to boot, just because I ran an update.

Let’s say I install the grub from a distro that uses an older version, maybe I don’t even bother updating that distro for months. I boot eos with that. Would that be a problem?

Of course, not a good idea to ignore updates for most packages, but I don’t think grub needs to be updated regularly.

Maybe I’m wrong, but I still don’t know why, other than partial updates are wrong.

You are. I surely remember that. I’ve been here since. . . I dunno, 3-4 years? And it wasn’t broken, it required a reinstall, which they told everyone we would have to do (at least in arch).

I’ve been using grub since about 2014, and it’s broken
. . Once on me?

So the caveat there is most (maybe even all) non arch based distros will acknowledge endeavour anyways. Normally the rule is too use the Arch grub to be the one all others use. I’m which case you’re right back here where we’re at now trying to ignore updates to it.

You can rationalize it however you want to to make it seem ok. There’s a very good reason why partial updates are not recommended and whole heartedly not supported.

It’s like when you’re most of the way thru a bottle of tequila, and you feel great and decide more tequila is the answer to feeling even better. At some point you and up hanging onto the floor for dear life trying not to fall off of it and waking up the next morning you can’t remember why you were doing what you were doing, and you can’t stand up because it feels like someone hit you in the head abundantly with the bottle itself.

There was a pinned thread it told us to run two commands grub-install and grub-mkconfig with some parameters, that would have been okay if it only happened once. Even if you ran these commands, it kept happening, fairly regularly and not only for me.

Yes i remember an issue with changes that were made to a new version of grub in the not too distant past. But it didn’t break every week. It hit users at different times over a period until the issue was resolved and users were notified. As with other issues on Arch some things require manual intervention. It required reinstalling grub and updating grub. Partial updates can happen when users don’t update and install other packages before they have run an update. It can also happen some other ways .

Edit: This is one of the reasons why systemd-boot is the default now. Not because it breaks but more to do with if and when it does users don’t tend to understand how to fix the problem that may occur. Of course there are many other reasons too.

I still use grub and i have very few problems with booting and updating.

Yes. We knew it was coming. As noted, that’s part of things here. You are the master of your own computer.

For what it’s worth, I daily Fedora and I did absolutely nothing.

I’m on my phone so it’s hard to look, but I believe if you read up on grub they say you need to reinstall/update whatever after some updates, it’s considered a normal practice for grub.

Good for you guys, I remember it breaking for me at least 3 times and the only advice we had that we should run these commands after every grub update. That was a weird solution, so I decided to put it in ignore.

Anyway what does grub do other than it loads the kernel? Does it do something related to security or performance or system stability?

When ever there is a grub update you have to run the grub update command. Why because grub is a package that gets installed. You have to run the grub update command in order to update the grub configuration. The package that is installed creates the grub configuration when you run the command.


I believe that advice came from grub themselves which is why they didn’t consider it broken. It was just part of the update.

If you’re going to give the advice, just make sure you lead off with the caveat that it creates a partial update situation that leaves the user with a completely unsupported system hence forth. It doesn’t matter the job.

I wanted to make sure the OP knew the consequences of ignoring the package.

I update every 2 weeks or so, and there are 100+ packages and I just forget to check if there’s a grub update, most of the time it wasn’t a problem and it booted normally. But it’s really annoying when you want to turn the system on in the morning and you’re in a hurry and it just doesn’t boot, because you forgot to run some commands the night before.

Why? Is the bootloader that critical? I would never put systemd or the kernel or anything needed for the base system in the ignorePkg, but I just don’t know if grub does anything that contributes to system stability.