this post was submitted on 07 Aug 2023
221 points (99.1% liked)

linuxmemes

23488 readers
921 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
  • 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 sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    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.

    founded 2 years ago
    MODERATORS
     
    top 50 comments
    sorted by: hot top controversial new old
    [–] Rooty@lemmy.world 35 points 2 years ago (2 children)

    I know that making networks out of duct tape and bubblegum is a point of pride in the Linux community, but if you have to store vital data, wouldn't a nice hardware NAS and a RAID array be a better solution?

    [–] DoomBot5@lemmy.world 16 points 2 years ago* (last edited 2 years ago) (2 children)

    How about an external HDD plugged into the Pi? Even a usb stick is better than writing it to the microsd card.

    [–] avidamoeba@lemmy.ca 14 points 2 years ago (1 children)

    My brain didn't even register that the meme was about NAS data residing on the SD card. I automatically assumed it's on attached disks and was about to snark-reply about keeping a cloned SD card taped to the Pi case for such occasions.

    [–] MaKraMc@feddit.de 4 points 2 years ago
    [–] Rooty@lemmy.world 4 points 2 years ago (1 children)

    Either go big or go home. RAID or bust.

    [–] spaceape@lemmy.nrsk.no 1 points 2 years ago (1 children)

    Remote mount datacenter storage pools or go home. If you have physical room for your disks in your house, you need to go bigger.

    [–] Rooty@lemmy.world 2 points 2 years ago (1 children)

    Going from NAS to SAN - nice, but playing Amazon/MS for keeping my data is a bit much, unless i have literal pentabytes that have to be high accsses.

    [–] spaceape@lemmy.nrsk.no 1 points 2 years ago

    I've grandfathered an unlimited account at an independent company with no storage or speed cap with physical storage in a country highly rated for privacy. Even considering Amazon/MS as a potential hosting provider is... Something I wouldn't do.

    [–] constantokra@lemmy.one 2 points 2 years ago

    Funny. My WD nas runs linux and the support ended so i've had to upgrade myself with entware... and it's old, so the fan was sized for cooler hard drives, so I cut a hole in the top and screwed on another fan... and WD removed NFS support years ago, so I just mount my shares oversshfs... and i'm currently upping my local security so it's only accessible over wireguard... honestly, I have no idea what it's doing with the hardware raid and the way it mounts drives so i'm tempted to switch over to mergerfs and snapraid...

    Basically my legit consumer hardware raid nas is more duct tape and bubblegum than my home built linux nas. Then again, it's easily a decade past its anticipated useful life too.

    I guess it is a point of pride.

    [–] nothacking@discuss.tchncs.de 33 points 2 years ago (3 children)

    Backups people backups. You don't realize how much you want them until it's too late to make them.

    [–] metaStatic@kbin.social 16 points 2 years ago (3 children)

    don't worry I have raid, that's a backup right?

    [–] pjhenry1216@kbin.social 20 points 2 years ago (1 children)

    Raid 0 right? I heard the number stands for how much risk there is of losing data.

    [–] bdonvr@thelemmy.club 10 points 2 years ago (1 children)

    Add more disks for more reliability

    [–] spaceape@lemmy.nrsk.no 5 points 2 years ago

    Due to the green economy I only buy second or third hand disks for my RAID0 setup

    No, the backup goes after the raid when something goes wrong.

    Wait, I thought you're talking about that SWAT team outside your house.

    [–] bdonvr@thelemmy.club 3 points 2 years ago

    If 3-2-1 is a good backup strategy, RAID (non-zero) is like 0.5 at best. Maybe 0.6 if your config can handle 2 simultaneous drive failures

    [–] purplemonkeymad@lemmy.world 3 points 2 years ago (1 children)

    Also remember to backup before things break. I once diligently backed up a system image before an upgrade. But I backed up a already failed SD card.

    [–] bdonvr@thelemmy.club 1 points 2 years ago

    Also remember to test your backup system.

    Setting up an intricate backup process is great, until an actual emergency happens and it turns out you can't put Humpty-Dumpty back together

    [–] Zaros@lemmy.world 2 points 2 years ago (1 children)

    and if possible, keep some backups in a separate physical location. House fires or break-ins aren't all that uncommon.

    [–] spaceape@lemmy.nrsk.no 3 points 2 years ago

    A good advice, but most regular people don't seem to bother with rotating physical off-site storage mediums so I advocate automated (and encrypted) backups to a cloud or something as well.

    [–] errer@lemmy.world 19 points 2 years ago

    If you must use an SD card: use log2ram. Greatly reduces the number of IO operations to the card and prolongs its life.

    [–] chtk@feddit.nl 14 points 2 years ago

    LPT: pies since at least the 3b can boot from USB.

    [–] sirico@feddit.uk 5 points 2 years ago (7 children)
    load more comments (7 replies)
    [–] Zagorath@aussie.zone 4 points 2 years ago (1 children)

    Not quite the same, but I made the mistake of using my RPi to run my home server and NAS off of an external USB non-NAS (i.e., not intended to be running 24/7) drive...with no backup or redundancy. The drive actually lasted a good long while, but it did die, and very suddenly, a couple of months ago. And now I've lost all my stuff that was on it. Still holding out hope I can figure out a way to recover the drive, but yeah.

    Back up your shit, yo.

    [–] original_ish_name@lemm.ee 1 points 2 years ago (1 children)

    Is it an HDD? Those are quite easy to recover, just put the disk into a working HDD

    [–] Zagorath@aussie.zone 1 points 2 years ago (1 children)

    Sorry I'm not sure what you mean. Yes it's an HDD. A USB plug-in one in a non-user-serviceable enclosure. I can't (without completely destroying it) get the HDD itself out. And I'm not sure what it would even mean to put it into a working HDD. The broken HDD itself is the problem, I think.

    [–] original_ish_name@lemm.ee 2 points 2 years ago (1 children)
    [–] Zagorath@aussie.zone 1 points 2 years ago (2 children)

    I can't recall the exact model, but it's some form of Seagate Expansion Desktop, sort of like the ones shown here. Mine was 1.5 TB, IIRC.

    Thanks for that link. Wish there was a bot to translate links back into normal YouTube videos like there's one to send you off to that other site, but it's easy enough to manually change the URL I suppose. Anyway, doing that is way beyond my skills, and I'm not sure the data would be worth paying a professional to do that either. I can't imagine that comes cheap.

    [–] lud@lemm.ee 2 points 2 years ago

    Opening a HDD on your own is usually a terrible idea.

    HDDs need a completely dust free environment so that no dust enter the harddrive.

    load more comments (1 replies)
    [–] chinpokomon@lemmy.world 4 points 2 years ago (3 children)

    This has happened several times to my Pi-Hole. Even with backups, trying to get my network back online still takes too long. I haven't found a good solution for resilience yet.

    [–] DilipaEli@lemmy.world 5 points 2 years ago (1 children)

    Try to use overlayfs under raspi-config, I've been running some raspberry pis for years with that (mostly on offsite locations where fixing dead sd cards is not possible)

    Updating the pis is a little more work but in some use cases it's worth it

    [–] chinpokomon@lemmy.world 2 points 2 years ago (1 children)

    I think something like BTRFS might be a better solution as overlayfs seems to freeze the system image state. Something which is copy on write (COW) seems like it would be more resilient and still provide an RW file system. To do it right would probably be a combination of the two with the data partition BTRFS and the system image partition overlayfs.

    [–] DilipaEli@lemmy.world 2 points 2 years ago

    Yeah that sounds like a good solution. I think arch based pikvm does something similar. (no reboot necessary to enable rw)

    For those pis that need to write stuff, I usually mount a network drive and use that while having the overlayfs enabled. So far haven't had any issues, only one pi died after 3 years due to faulty power supply.

    [–] muhyb@programming.dev 4 points 2 years ago

    I use an old netbook as Pi-hole. It has a battery so powerouts are not a problem.

    [–] karlthemailman@sh.itjust.works 4 points 2 years ago (1 children)

    Honestly something that critical probably shouldn't run on a rpi. There are plenty of cheap used thin clients you can buy on eBay that have better performance and reliability. I probably like the thinkcentre micros, but feel and hp have good options too

    [–] avidamoeba@lemmy.ca 2 points 2 years ago* (last edited 2 years ago)

    Pis can be supremely reliable when used correctly for the purpose. E.g. use high quality SD cards and don't write to them much, or a good quality SSD if you have to do significant writes, use an official or better PSU, etc. My oldest 4 is from 2019 and it's been in continuous use since then. It used to be a NAS running a 2-disk mirror exported over NFS. These days it's a gigabit OpenWrt router with SQM. It's still in the original SD card.

    [–] PancakeLegend@kbin.social 4 points 2 years ago

    Full redundant JBOD backup. It's unfancy and safe.

    [–] bdonvr@thelemmy.club 3 points 2 years ago

    Pfft, mine boots from a USB SSD, and since my services are all containerized I just gzip the directory with all my docker-compose files and volumes and chuck it into B2 every 6 hours

    [–] ANIMATEK@lemmy.world 3 points 2 years ago

    https://raspibackup.linux-tips-and-tricks.de/en/home/

    Regular unattended backups in seconds using hardlinks. Honestly, it doesn’t get any better.

    load more comments
    view more: next β€Ί