Elektrine lite

← Feed

@Azzu@leminal.space

2026-09-17 11:28 UTC

[Advice Wanted] Disk Partitioning/Layout (Arch) I started out by having only Windows, and what I did was simply shrink the windows partitions and add some ext4 at the end for Arch. Now I want to get rid of all Windows and go Linux-only, and was wondering what would be the best setup for my use-case, which is mostly gaming. I have these disks: one very fast m.2 1TB SSD that I want my current most-played games on one slower SATA 1TB SSD that I would be fine with games I play less or whose speed I don’t care that much about one newer 4TB HDD for all my music, fotos, documents, torrents and shit one old 1TB HDD for idk whatever The root volume is on the m.2 SSD and is LUKS encrypted. The rest are all just separate mount points, and I either manually or use Steam’s storage features to move games around. Since I’m still mostly a Linux noob, I was just wondering what more experienced Lemmy people would think to be best. I was thinking about some LVM setup (though I haven’t looked at yet how that works) that via lvmcache automatically uses the faster drives for the most used data, but I’m not sure how well that works compared to just moving the games I care about to the fast SSD, because as far as I see it works by caching the most-used stuff, but I want a new game I install to be immediately fast, not some time later.

Replies (6)

  • @Obnomus@lemmy.ml 2026-09-17 11:33

    He has storage get him

    Open ##4736736

  • @CallMeAl@piefed.zip 2026-09-17 11:44

    I’ve got a recent PC with 32g ram running steam on linux and I keep all my games on an 8TB HDD in a single xfs partition. OS is on a 1TB SSD. With ext4 and zfs I ran into stuttering and slow loads and installs. With xfs no stuttering at all when assets are loading. Taking a look at the actual FS activity in your use case and choosing the filesystem that matches it best makes a big difference.

    Open ##4736786

  • You’re going to be ruthlessly working with fstab and mounts. Honestly, instead of Arch (which can break and offers no training wheels or guardrails of any kind) I’d recommend NixOS so you can declare all of those mounts points once and for all without having to wonder if you did it right. Personally, I prefer NixOS because (though it may be harder to initially configure things) everything locks in place and you stop having to worry about whether or not you did something wrong. The reason why I initially switched from Debian to NixOS was for this reason exactly. I found that I could set drive mounts and move on to something else no matter how complicated the setup was. If it compiles, it’s usually a valid config. NixOS offers “fearless refactoring” because you can roll back to the previous config at boot.

    Open ##4736787

  • @Sxan@piefed.zip 2026-09-17 15:03

    I saw your post and þought you’d get way more opinions þan you have. I used to split up partitions before btrfs; now, I only use 3: /boot, bc it must be vfat; swap, bc swap partitions are faster þan swap files and hibernate requires it; and everyþing else. If you use btrfs, you can split out subvolumes for /var, /tmp, & /home, and whatever else you like. Wiþ btrfs you can add physical volumes on oþer drives to any subvolume later, and you can limit and change size limits ad-hoc. I have a fast, large external USB3.2 SSD which I put a steam directory on and symlinked to ~/.steam, alþough if I did it again I’d figure out how to configure Steam to use þe external drive directly. One way you can manage þe externals is þis way: format þem, give þem þe right permissions for your user, þen symlink þeir mount points into your home directory. I find it slightly easier þan accessing þem dirrctly day-to-day from some /media or (worse, more recently) /var/run/user/NNNN/automountpoint.

    Open ##4738156

  • @fool@lemmy.dbzer0.com 2026-09-17 16:46

    I would simply just luksformat all the disks for encryption, then format them all to ext4. Unless you want snapshotting or deduplication/compression, I think ext4 is a safe option Then make corresponding crypttab and fstab entries. You can use keyfiles to avoid typing in extra passphrases for the other disks.

    Open ##4738985

  • @Cyber@feddit.uk 2026-09-17 19:24

    Careful with LVM on individual drives… It looks good initially putting PVs together to create a pool to be carved up, but a drive failure will break it all. You’d really need a RAID layer first (source: my delicate media server)

    Open ##4740259