Homelab

422 readers

1 users here now

Rules

Be Civil.
Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
No memes or potato images.
We love detailed homelab builds, especially network diagrams!
Report any posts that you feel should be brought to our attention.
Please no shitposting or blogspam.
No Referral Linking.
Keep piracy discussion off of this community

founded 1 year ago

MODERATORS

[email protected]

What 3-drive configuration for a TrueNAS Scale server? (alien.top)

submitted 1 year ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

I have a Beelink EQ12 Pro where I can put a total of 2x2TB NVMe SSDs + 1x4TB SATA SSD (not sure if more is feasible according to Beelink's description but it is enough for me right now).

I'd like a configuration where I can lose and replace one drive without breaking anything, hotswap not needed. What would be an adapted strategy for that in terms of drive capacity, partitioning and ZFS pool? 3x2TB even if two are M.2 NVMe and one is SATA? 2x2TB + 1x4TB? Something else?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago (1 children)

Didn't think that way around but this can probably work pretty well :) What about the remaining space on the SSD then? May it be partitioned so I have 3x2TB with 2x2TB of NVMes and parity on the 2TB SATA SSD?

[–] [email protected] 1 points 1 year ago (1 children)

That’s something that I’ve never tried before.

I’m more so worried about performance loss having a SATA SSD mixed with an NVMe in parity. You’re talking a 500MB/s SATA SSD vs a 3000+ MB/s NVMe.

[–] [email protected] 1 points 1 year ago

Yeah you're right, that's why I was imagining putting only the parity bits on the SATA drive, so ZFS can do it's calculation after I'm done with my data operations on the NVMes. Guess I'll have to dig deeper in TrueNAS and ZFS config :)