Skip Navigation

HDD or SSD for a home server?

I'm new to this stuff so go easy on me.

So I want to get into selfhosting, and I've decided to get a Raspberry Pi 5. I plan to attach drives to it, from about 500GB-1TB. I'm on a budget, preferably under $100.

I want to host these things:

  • A personal lemmy instance
  • A samba server, to store files and backups
  • A mail server
  • A few other light docker containers

I was wondering whether I should get an SSD or an HDD for these. Lemmy would probably like an SSD because it uses Postgres, but an HDD would be better for storage since I get more GB per dollar.

What should I go with?

32 comments
  • While I run my own Lemmy instance, I can say with 100% certainty - do not host a Lemmy instance on your own hardware.

    It's tempting, and I did, but don't. The reason? CSAM. Your hosting stuff for other people, and if someone uploads something horrible to another instance, that is federated with you. That means now you are hosting that content.

    The feds then have full rights to kick down your door and seize your hardware. On the cloud however, they'll seize your VM , but your home stuff is okay.

    Hosting Lemmy is great - but it's something you really have to think about. Hosting your content is awesome, fun, and rewarding. I've learned hosting other people's content is.... Not as fun.

    • Didn't the Lemmy teams sort of fix that CSAM thing ages ago?

      I remember a wave of lockdowns and hush hush related to that, soon followed by an update to Pictrs with a bunch of new docker compose settings.

      My server got pooched in the update and it took me almost a month to fix partly because I had little free time.

      • There were some automod things built by 3rd larties, and they help, but it's still a worry. There's also image proxying now, so at least I'm not directly hosting it, but I'm not 100% that the feds will see it that way immediately

    • Is this really still true about images federating in Lemmy? In any case, I think the problem can be avoided by disabling pict-rs.

  • For any computer today, server or no, I'd probably default to SSD today unless I expected to be making use of a large store of files that I expected to access in serial, like a large movie collection or maybe a backup server that can play well with rotational drives.

    The only thing there that looks like it could be doing that is the Samba server, depending upon what the remote clients are doing with it (could be a movie server).

    In general, if you can fit your stuff on an SSD today, I'd get an SSD.

    You also can also add a rotational drive down the line if you run low on space and need inexpensive space for something that you're going to access in serial, and use both; just move the bulk stuff to the rotational drive then.

  • Highly recommend SSD if just for Lemmy. Man, the syncing can take a while. I have HDD with a m.2 cache and it can still take a while. Personally, I'd go for something a little more powerful, but it's all fun and educational.

  • I’m running a Raspberry Pi 4 with an array of hard disks. Essentially the entire OS is on a small SSD but because I have so much data I’ve got two traditional HDD drives with XFS and LUKS disk encryption.

    I’d say overall it works fantastically, over 802.11ax and Samba I’m pushing about 600-700 Mbps while transferring to the HDD drives.

32 comments