Comment on Come to say thank you. Time to move from proprietary to Open Source
Sproutling@lemmy.ml 6 days ago
When my QNAP finally died on me, I decided to build a DIY NAS and did consider some of the NAS OSes, but I ultimately decided that I really just wanted a regular Linux server. I always find the built-in app stores limiting and end up manually running Docker commands anyways so I don’t feel like I ever take advantage of the OS features.
I just have an Arch box and several docker-compose files for my various self-hosting needs, and it’s all stored on top of a ZFS RaidZ-1. The ZFS array does monthly scrubs and sends me an email with the results. Sometimes keeping it simple is the best option, but YMMV.
My NASs are purely NAS, I prefer a Debian server for… Pretty much everything. But my storage only does storage, I keep those separate (even for an old PC acting as a NAS).
No matter what goes down, I can bring it back up, even with a hardware failure.
I used to do that. I had a QNAP NAS and a small Intel NUC running Arch that would host all my services. I would just mount the NAS folders via Samba into the NUC. Problem is that services can’t watch the filesystem for changes. If I add a video to my Jellyfin directory, Jellyfin won’t automatically initiate a scan.
Nowadays, I just combine them into one. Just seems simpler that way.
I just have my downloader trigger a scan at completion.
I have a few proxmox clusters going, combining it all wouldn’t be practical. This way my servers (tiny/mini/micros I’ve repurposed) stay small with decent sized ssd’s, big storage in 2 NAS’s, and a third for backups.
I would just mount the NAS folders via Samba into the NUC. Problem is that services can’t watch the filesystem for changes. If I add a video to my Jellyfin directory, Jellyfin won’t automatically initiate a scan.
That sounds like a config issue. I use NFS shares in a similar way, and Plex/*arr/etc has zero issues watching for changes.
I think it’s a samba limitation. Maybe NFS works well for that case.
Out of curiosity as an owner of a QNAP NAS, how did it go out? Any signs it was in its last legs? Now that I’ve used one, the form factor is the only thing better than most options out there when I got it.
Nowadays all QNAP, Sinology and other NAS vendors supposedly offer a lot of extra value with their cloud options, but I find them a sure way to get hacked based on the average company’s investment in security (I work in IT, it is a sad affair sometimes) combined with all the ransomware specifically targeting them due to old packages they rely on = I’ll build my next system from the ground up, even if the initial cost is higher and the result is uglier.
It was this nasty Intel clock drift bug: forum.qnap.com/viewtopic.php?t=157459
Support was completely unresponsive and refused to do anything. Didn’t even acknowledge the issue AFAIK. I tried to add the resistor but my copy of the NAS didn’t expose the right pins so I couldn’t even solder them on if I wanted to. Then I tried mounting my drives into another Linux machine, at which point I realized they were using some custom version of LVM that didn’t work with standard Linux. I ended up having to buy a new QNAP NAS just to retrieve my data and then I returned it.
After that, I swore off proprietary NASes. If I can’t easily retrieve data from perfectly good drives, it is an absolute no go.
If I can’t easily retrieve data from perfectly good drives, it is an absolute no go.
I’ve been running the same md-raid drives through three different machines. I love that about md-raid. Pull the drives out of one system, stick them into another system with mdadm installed, and it recognizes the array immediately.
I have feeling I may find myself here in time, as I develop this setup more.
If you’re familiar with Linux, I highly recommend it. The flexibility is just great and you can setup whatever dashboards / management tools you need. No need to tie yourself to a specific solution IMHO.
If you’re going with Docker containers, a lot of the NAS OSes just hold you back because they don’t support all the options that Docker offers. You’ll be fighting the system if you need to do any advanced Docker configuration.
Thank you!
I’m not familiar, yet. My background is MS OS but going back as far as CLIs so I’m confident I’ll learn fast.
If you want reliability, keep your NAS as a NAS, and run everything else in VMs. Don’t run applications on the same system as NAS stuff. If you screw something up, you’ll have to rebuild the whole thing. Run your applications in a VM at the minimum, that way you can just blow it away and start over if it gets fucked, without touching the NAS.
I went with OMV because 1. I’m cheap, and 2. I could configure it how I wanted.
Glad I went that way, because I was considering “upgrading” to a Synology for a while.
Oh yeah. I bet you’re feeling lucky you didn’t switch to Synology given the recent drama where they’re locking features down to their branded hard drives, which we all know are just up-charged drives from regular vendors.
What drive bay enclosure are you using btw and how does it connect to your Mac mini?
Never heard of dockge. I’ll have to check it out! I’ve just been using podman and docker-compose scripts.
Drive bay I’m using is a Sabrent DS-SC4B, connected via USB3. I’m currently collecting parts for an actual tower build based on a G4560T.
Interesting! I am assuming each drive shows up as an independent drive that you can raid up however you want in software? Man I was looking for something like this, but at the time I was building my NAS, I couldn’t find something similar so I just decided to build a whole new machine with enough space to contain the drives themselves. Had I known, I might have gone with this and a NUC or something. How’s the performance?
dan@upvote.au 6 days ago
I like Unraid because it’s essentially “just Linux” but with a nice web UI. It’s got a great UI for Docker, VMs (KVM) and Linux containers (LXC).
unwillingsomnambulist@midwest.social 6 days ago
Just got unraid up and running for the first time today. There’s a bit of a learning curve coming from TrueNAS Scale but it supports my use case: throwing whatever spinning rust I have into one big array. Seems to work alright, hardware could use additional cooling so I’ve shut it off until a new heatsink arrives.
doeknius_gloek@discuss.tchncs.de 6 days ago
What made you switch from TrueNAS Scale to Unraid, if I may ask? Is it just the ability to mix different drive sizes? I’m currently using TrueNAS Core and thinking about migrating to TrueNAS Scale.
unwillingsomnambulist@midwest.social 6 days ago
Yes, that’s the only reason. You can mix drive sizes and still have a dedicated parity drive to rebuild from in case things go poorly. I am aware that it’s basically LVM with extra steps, but for a NAS I just want it to be as appliance-like as possible.
Still using Scale at work, though - that use case is different.