I’m sure this won’t be abused at allllll.

Because power interruptions introduce choas into systems which can cause curruption. Most times nothing will happen and we carry on as usual, but occasionally things will be effected in a way that prevents booting or borks some other item. Nature of the beast.

Fortunately removing/replacing fstab and running fsck fixed it. The pain in the ass part was needing to mount a temporary repair partition/shell so I could diagnose/run commands.

I have a UPS LMAO. Normally it prevents these types of issues but my computer was in standby when the power loss happened and did not like it.

As someone who spent the better part of my afternoon dealing with this nonsense thanks to an unexpected power outage:

I’m not crying, you’re crying.

In all my years this might be the most dumb block list I have ever seen. A sample:

Yeah but I like that stuff. It gives me options so I have a more space to work around unruly printers. I can’t tell you how many times an outdated generic driver from the dark ages was the fix I needed. Especially helpful when working with clients using proprietary software that doesn’t play well with others.

Eh I never minded. I preferred printer problems. Fixing the default printing source made me cool. Downloading a driver or pointing a user to the right network printer made me a hero. Replacing a roller or a fuser so the printer stopped jamming elevated me to legendary. Much more relaxing then fixing someone’s janky SQL “formula” because their “excel is broken.”

At least it wasn’t old tires this time.