this post was submitted on 26 Dec 2025
71 points (97.3% liked)

Selfhosted

59897 readers
659 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
71
Holiday Upgrade Disasters (feddit.uk)
submitted 5 months ago by Cyber@feddit.uk to c/selfhosted@lemmy.world
65 comments fedilink hide all child comments
 

So, just a light post, I upgraded my Pi4 last night and found the Linux firmware breaks a 32bit install.

I've been meaning to change to 64bit for months, but as it's my DMZ box for torrents, radicale, etc, then it's just finding the right time to convert an adhoc setup into my ansible scripts.

Luckily I had a SD backup from September to get it running again

So, what have you broken over the holidays?

you are viewing a single comment's thread
view the rest of the comments
[–] Onomatopoeia@lemmy.cafe 5 points 5 months ago* (last edited 5 months ago) (2 children)

I don't do upgrades (well, not in the sense most people think of them).

My approach is that upgrades are too risky, things always break. It's also why I don't permit auto updates on anything. I'd rather do manual updates than dedicated time. Keeping things working is more important, and I have backups.

I run everything virtualized (as much as I can), so I can test upgrades by cloning a system and upgrading the clone. If that fails, I simply build a new system based on some templates I keep. Run in parallel, copy config and data as best I can, then migrate. Just migrated my Jellyfin setup this way.

This is a common methodology in enterprise, which virtualization makes a lot easier for us self hosters.

I haven't had a disruption from updates/upgrades in 5 years.

[–] Brkdncr@lemmy.world 6 points 5 months ago (3 children)

It’s not common in enterprise to not auto-update.

[–] frongt@lemmy.zip 4 points 5 months ago (1 children)

Depends on the company and the system. Some of them need to be done off-hours while people aren't using them. Some are HA and/or insignificant enough that you can do them any time without interruption.

[–] femtek@lemmy.blahaj.zone 1 points 5 months ago

I have not had any auto update in my entire career but i have always been on the infra side so it was never just my app. Though I do wish the update/outage process would be updated to reflect kubernetes and not just think of everything as monolithic servers.

[–] ExcessShiv@lemmy.dbzer0.com 3 points 5 months ago

It's extremely common...most production lines I've ever been to only do manual updates on equipment, if any at all.

[–] suzune@ani.social 1 points 5 months ago

It's also not uncommon in enterprises that things break needlessly.

[–] Cyber@feddit.uk 2 points 5 months ago

That's an interesting process... you could improve it with some ansible - if that's your thing... or use snapshots on the VM(s) and roll back?

That's kinda what I'm doing with this (physical obviously) Pi... take a full backup now and again... do upgrades... rollback when completely borked.