this post was submitted on 28 Feb 2024
276 points (97.3% liked)
linuxmemes
21304 readers
1123 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Okay but jokes aside, how many users actually have issues with that? So far it never broke anything for me, even when it apparently should have, according to a forum post I only read several weeks late, after finally noticing the intervention required tag
The intervention last year was only required if the grub package was updated and generated a config the older bootloader didn't understand. You would have been fine either way as long as you didn't generate a new config. I ignore grub updates now because I was caught with my setup.
Happened to me at least once
Perhaps this is on me, but I've had issues with Windows monkeying with GRUB on dual-boot the first year or so I transitioned to Linux. Finally moved to systemd-boot and haven't looked back since.
Happened once around two years ago, s botched update from mainstream or something like that. Made me learn systemd boot which is simple and never EVER use grub again
It's happened to me 2x in 20 years of Linux usage. First time was my fault.
I've been using Arch for like 10 years and I never really have any issues. My biggest issue is with the ZFS module, but I solved that by using the LTS kernel.
The faulty GRUB patch was a widespread issue. Syu -> reboot -> fail to boot. It was especially annoyng since you couldn't just rollback like with any other faulty arch update.
Besides that, during the 2-3 years I mained it, I've had Arch often fail to boot after updating it for the first time in a few weeks. And on endeavour the update script gave up one day, and so I had to remember to manually mkinitcpio or it would fail to boot.
Yes, I've been affected by the grub crap several times.
Been using arch and endeavour for about 5 years now, only ever had boot issues caused by Nvidia drivers. Outside of grub that is.
My backup pc had the most issues with updates, and it doesn't have a dedicated GPU. I wouldn't update it for a few weeks or a month+, update, fail to boot, rollback, try again in a few weeks and it would work.
The final straw was when I was working abroad with bad internet, and had to weigh whether -S or -Syu is more likely to cause a failure.
Interesting. How long ago was this? I use arch daily as my main driver, but also run it on a vps, a laptop, and a raspberry pi (arm distro). Other than grub, I can't recall the last time upgrading caused an issue.
The last time was 6+ months ago because I stopped using Arch. It happened from time to time on both of my machines, but it had a lot higher chance to happen on that particular pc than on my ThinkPad. I'm guessing it was more frequent because the main one was getting updated multiple times a week.
There was one good warning sign though: if I needed to -Syyu, something was most likely going to go wrong with the update.
I've switched from Arch to Fedora about a decade ago, never had this issue with either. Actually I probably never had this issue with GRUB at all, maybe with LILO...
It happened twice for me and now i don't have the time to backup everything and reinstall the os, so i moved to a debian base
You don't have to reinstall the os just because grub broke 😕
The first time that this happened i spend a good chunk of time to learn how to fix the problem without reinstalling, the secound time i just moced everything to another driver, reinstalled and moved everything back, it took a feel hours but most of the time i was just waiting for the files to move, so i was able to do something else instead, i don't use brtfs because it corrupted mi ssd once (i have no idea why), but i'm fine on mint, now i don't have much time at home, and when i do i need to be sure that nothing will broke because i have a lot of work to do from my job and college, i really like arch but i really need something stable right now
BTRFS or ZFS and then you can just rollback to an earlier snapshot.
Except if you upgrade ZFS pools to a newer version that's not yet supported by Grub.
Oops :)
1 year on current Arch install and have yet to have a issue
Yeah the only issues I've had with Arch, were due to me being a dumbass.
I have installed arch on my work laptop two years ago now and I have never had a problem with it booting, logging in or functioning. Never as in not once. I do update it periodically and every time it just fucking works.
I used debian at a desktop at another work and the desktop had an nvidia card in it. Every time apt said “nvidia” the computer booted in single user mode or kernel panic.