this post was submitted on 30 Jan 2024
16 points (94.4% liked)

Selfhosted

40183 readers
547 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 posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

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

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I have a pi4 running on an ssd over usb3 with a usb3 dock that has 2x2TB drives for storage.

At the moment I have mainly music on one and mainly video on the other, with important stuff on both and elsewhere.

Is it sensible to combine 2x2TB hdd's via usb3 dock into a 4TB filesystem/pool/volume/thing......and if so can I have tiered storage so if one drive fails the other will have a mirror of important stuff?

top 10 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 9 months ago (1 children)

Raid0 (combining both drives' capacities) is not really tiered storage. You would want Raid1 (each drive is a copy of the other drive ), but doing this isn't a backup. How will you be monitoring the drives so that you know if one of them actually fails?

I don't think the RPi has a new enough kernel, but with bcachefs you can do tiered storage. By combining the storage of the ssd + hardrives, into a single block device, then make the ssd the read/write cache, and give the whole pool replicas=2, so that that if one drive dies you still have the failover of the other drive. Do be aware this setup is still not a backup however.

[–] [email protected] 4 points 9 months ago (1 children)

Thanks,

bcachefs could be the answer but I don't really want my data on a fs I need this week's kernel to access properly. Maybe I should just hold off for a few months.

I'm not monitoring the drives, I have backups of important stuff...but would be nice to tag more important stuff amongst the mediocre stuff on the off chance both drives don't fail at the same time.

[–] [email protected] 2 points 9 months ago

Totally reasonable, something like LVM can at least get you to a raid1 setup, pretty easily.

[–] [email protected] 3 points 9 months ago* (last edited 9 months ago) (1 children)

What you're looking for is a backup. RAID is not a backup, as another poster said it's a tool for enduring high availability, and possibly higher throughput.

Buy a second pi and put it in another location in your house or even better at friends house then configure regular backups of your important data to it. There are also cloud services for doing backups which are great because having a location to do off-site backups to can be really hard to get as an individual.

[–] [email protected] 1 points 9 months ago

Thanks, I do have backups of important stuff.

I think bcachefs is what I'm looking for, but I'm gonna wait a bit until development calms down a little and keep on the way I am at the moment.

[–] [email protected] 3 points 9 months ago (1 children)

With two drives you can extend them into one big drive or you can mirror them, but you can't do both.

[–] [email protected] 1 points 9 months ago

doh

will just keep on keepin' on then

[–] [email protected] 2 points 9 months ago

RAID1 would be a stopgap against a certain type of failures but it's not a solution for accidental deletions or failures that affect both drives or the whole machine (fire, electrical, theft).

Redundancy is mostly a solution for continuous availability, which is not something most home-users care about that much (but if you have private self-hosted services that are super critical for you you may want to reconsider your approach).

You should start by taking inventory of your truly important files, figure out how much space they take overall, then start doing proper backups for them. That means taking regular snapshots on some different media. That media can be another HDD, or it can be optical discs (Blu Ray is better than DVD but it may be a matter of cost where you live). If you use a HDD there are specialized backup software like Borg Backup that will deal with deduplication, compression etc. for you. And you have to verify your backups regularly as well – Borg will allow you to do it easily, with optical discs you can use recovery parity checksums (with par2).

[–] [email protected] 1 points 9 months ago

A btrfs raid 1 array would make the most sense.

[–] [email protected] 0 points 9 months ago* (last edited 9 months ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
RAID Redundant Array of Independent Disks for mass storage
RPi Raspberry Pi brand of SBC
SBC Single-Board Computer

2 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.

[Thread #467 for this sub, first seen 30th Jan 2024, 11:45] [FAQ] [Full list] [Contact] [Source code]