Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.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 remove France.
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
1 year on current Arch install and have yet to have a issue
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.
Yeah the only issues I've had with Arch, were due to me being a dumbass.
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.
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 :)
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...
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
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.
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.
It's happened to me 2x in 20 years of Linux usage. First time was my fault.
Why is anyone still using grub? This is on you at this point
Because it's the one that supports the most setups, like LUKS and LVM (on the root partition)
which bootloader can't do this? EFISTUB, systemd-boot and rEFInd can
Gotcha
What if I like grubbing around? What if I like when updates give me hell?
why is anyone (who uses a bootloader) still not using grub?
Because rEFInd exists
Good to know, I'll change when the dists start replacing grub with rEFInd, last time I changed bootloader was lilo -> grub from what I can find it was around 2013 Debian switched.
you guys use GRUB lol
Doesn't everyone just boot by entering machine code with the switch panel in the front?
For real, systemd-boot is superior in every way.
NixOS superiority.
About to make the move I think, and just loaded up a thumb-drive this morning before wandering in here. Wish me luck!
Good luck, and make sure to use version control!
Lauths in timeshift and rEFInd.
Indeed. UKIs are the way.
Tumbleweed and Mint offer Snapper Rollback configured by default, available from the Grub menu. And that's friggin' noΓ―ce.
I'm more of a First World Anarchist myself, I only ever rescue my os-breaking, Arch-is-botched mistakes with a Live Ubuntu thumbdrive.
This has never happened to me, well at least not yet. The only thing that's ballsed up recently is Nvidia drivers....
Latest kernel update restarted my session (closing all programs, including my terminal) before mkinitcpio, easy fix, but yeah, did require live boot media.
I can see how that would be problematic. Hopefully that'll never happen to me....
Would not have happened with systemd-boot
This is why people who want to be product use Debian π
People who want to be a product use microsoft windows
Canβt argue with that π however itβs funny to see someone else also saying that.
rEFInd autodetects bootable images. Doesn't help if mkinitcpio suddenly fails to find hooks, tho.