Login
You're viewing the assemblag.es public feed.

Replies

  • torbjørntbp@digipres.club
    Sep 29, 2026, 1:20 PM

    @p3ter these look interesting. Is 2 bays max or is there some expansion modules or something?

    💬 1🔄 0⭐ 0
  • Peter B.p3ter@mastodon.social
    Sep 29, 2026, 6:19 PM

    @tbp you mean 2 bays = 2 SATA disks?

    AFAIK that's all.
    For more disks I'd also recommend "bigger" hardware 😉

    Miniservers like that may be useful to easily have redundant backup servers in institutions which would be happy to have "a handful of TBs".

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Peter B.p3ter@mastodon.social
    Sep 30, 2026, 6:57 PM

    @tbp would be interesting if the controller on the board would support that.

    If it did, wouldn't it be possible to make a hat-PCB for additional SATA ports?

    If the controller won't handle it anyway, you can relax and close that door on the zima 😄

    💬 1🔄 0⭐ 0
  • torbjørntbp@digipres.club
    Oct 1, 2026, 10:44 AM

    @p3ter i have a 4-hdd +2nvme synology that's filled to the brim, with backups going to an unraid box built out of leftover hardware and shucked external drives.

    at some point i'd like to drop the synology (due to their weird new hardware lockin stuff). the zima looks nice and lightweight! perhaps if drive sizes keep increasing i can drop down to 2 discs for parity at some point.

    At this point im more worried about the cost of replacing drives than the actual nas tho :|

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Jonathan Hartleytartley@fosstodon.org
    Oct 2, 2026, 4:05 PM

    @p3ter I have one for a more modest homelab, running ZimaOS, as a file server and Syncthing and Duplicati backups and low CPU media (eg. ebooks). I'm overhauling it today, while figuring out Incus to run containers for the beefier media server box. 🤞

    💬 1🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Jonathan Hartleytartley@fosstodon.org
    Oct 4, 2026, 7:23 PM

    @p3ter Yes! I'm not a containerization expert but I really like it. They are lightweight and fast to start / stop. Trade off is they use the host's kernel, so can't pin a kernel version on the container. But Incus hosts VMs too, with the same CLI and API, which don't have that restriction.

    💬 1🔄 0⭐ 0
  • Jonathan Hartleytartley@fosstodon.org
    Oct 4, 2026, 7:25 PM

    @p3ter When I was at Canonical we used LXD, from which it is forked, for everything, as an in-house project, but it may suffer from not having Docker's first mover advantage. Since then Canonical did a bit of a power grab over ownership, laid off the lead dev, so he forked it into Incus and the community mostly followed.

    💬 1🔄 0⭐ 0
  • Peter B.p3ter@mastodon.social
    Oct 4, 2026, 7:32 PM

    @tartley I didn't even know canonical had its own containerization thing LXD going. Thought it was a typo on LXC 😂

    💬 1🔄 0⭐ 0
  • Jonathan Hartleytartley@fosstodon.org
    Oct 4, 2026, 7:53 PM

    @p3ter oh, those are the same thing! Over the years both the project itself and the cli executable have been known as either LXC or LXD. It's open source, with a lot of contributions from Canonical.

    💬 0🔄 0⭐ 0