• 0 Posts
  • 276 Comments
Joined 2 years ago
cake
Cake day: February 24th, 2024

help-circle
  • In my case, I setup a ZFS pool of my disks in my old desktop PC running Proxmox. Then I allocated some storage to an LXC container running Debian and Samba for file sharing.

    In your case, since the QNAP already runs Samba, it would be best to run it directly on the NAS.

    But if you want to do it for the learning experience, you can setup an NFS share on the QNAP and link it to the Proxmox. The Proxmox can then use the NAS for storage and you can have VMs or LXC contsiners use for virtual disks.


  • I am quite satisfied with the unifi ecosystem so far as networking and CCTV systems go. They are cloud enabled without being cloud dependent. Since the early 2025 networking update, their routers are pretty good now. The UDM SE is a pretty compelling router/POEswitch/NVR in the home context.

    Their NAS ecosystem is still very new and I would not it a viable option yet. They are also leaning towards the vendor lock-in direction with drives. Its the same reason I would stay away from Synology and QNAP.

    Personally, I run a old desktop as a NAS/homelab running Proxmox(FOSS based hypervisor). I run ZFS on it and its “fine”. It performs fine even with a mixed bunch of disks, provided you have them in pairs or groups of 3 that perform close to identically. I just run a Debian container on the Proxmox as my fileserver and a few VMs for homelabbing.

    One player that works well in a home environment is UnRAID. It a Linux distor that runs on commodity hardware and handles redundancy with “just a bunch of disks” better than most. The UI is friendly to non technical users. The catch is that UI is commercial software. Many consider it a fair exchange for the convenience it brings.

















  • My rule for older hardware, before trusting the ZFS fault reporting, I would follow the following steps.

    (Note these are homelabber steps and not what I would do in the enterprise, where risk and time is a lot more expensive than replacing hardware)

    1. Check the Smart data of the drive. If it reports the drive as faulty, replace it.

    2. Zpool clear the error and see if it comes back. Sometimes drive errors are not cause by the drive itself

    3. Reseat the drive and the cables between the motherboard and the drive. Clear errors after this step. Especially with older hardware and it having travelled from its previous owner to you, something might not be seated properly.

    4. Move the drive to another drive bay, or swap it with another drive. If the errors move with the drive, the drive is faulty. If the errors move to the bay, you probably have a good drive, but a faulty drive bay/cable.