this post was submitted on 08 Aug 2024
46 points (96.0% liked)

Selfhosted

62993 readers
1280 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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
46
Best way to keep a hot spare SD card for a raspberry pi? (sh.itjust.works)
submitted 2 years ago by traches@sh.itjust.works to c/selfhosted@lemmy.world
55 comments fedilink hide all child comments
 

I have a load-bearing raspberry pi on my network - it runs a DNS server, zigbee2mqtt, unifi controller, and a restic rest server. This raspberry pi, as is tradition, boots from a microSD card. As we all know, microSD cards suck a little bit and die pretty often; I've personally had this happen not all that long ago.

I'd like to keep a reasonably up-to-date hot spare ready, so when it does give up the ghost I can just swap them out and move on with my life. I can think of a few ways to accomplish this, but I'm not really sure what's the best:

  • The simplest is probably cron + dd, but I'm worried about filesystem corruption from imaging a running system and could this also wear out the spare card?
  • recreate partition structure, create an fstab with new UUIDs, rsync everything else. Backups are incremental and we won't get filesystem corruption, but we still aren't taking a point-in-time backup which means data files could be inconsistent with each other. (honestly unlikely with the services I'm running.)
  • Migrate to BTRFS or ZFS, send/receive snapshots. This would be annoying to set up because I'd need to switch the rpi's filesystem, but once done I think this might be the best option? We get incremental updates, point-in-time backups, and even rollback on the original card if I want it.

I'm thinking out loud a little bit here, but do y'all have any thoughts? I think I'm leaning towards ZFS or BTRFS.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] avidamoeba@lemmy.ca 0 points 2 years ago* (last edited 2 years ago) (1 children)

Any failures of SanDisk Extreme Pro / Samsung Evo Plus?

I buy the redundancy argument. I'd still use ZFS for that if possible though. ๐Ÿ˜‚ All my machines use mdraid 1 for their system drives but now that I know enough about ZFS, I'd likely use it on root next time around.

[โ€“] Shadow@lemmy.ca 3 points 2 years ago (1 children)

Yes. I've always splurged on nice cards for my personal stuff. I think it's more about the write behavior of Linux than anything else, since I've never had a card die in my camera.

I refuse to use a pi with SD at this point. Saving $50 isn't worth my time to reinstall things.

[โ€“] avidamoeba@lemmy.ca 1 points 2 years ago* (last edited 2 years ago)

You're making me nervous.

But then again, all my Pis are OpenWrt now which barely writes, so I'm probably fine. ๐Ÿ˜