Finally…FINALLY had time to start moving everything over from my old Mac Mini-based NAS to my “new” NAS.

For reference: https://lemmy.dbzer0.com/post/61180593

So far so good! Ultimately, I decided to start with a fresh install of the most recent OMV release (v8.5), and migrated my existing mdadm-managed RAID5 array to that. OMV picked it up immediately, which made that part very easy.

The tricky part I’m dealing with now is remapping the various shares to my Proxmox cluster and VMs. Because I started fresh, I changed things up a little bit and created a second “disk” for each of my four Proxmox-hosted Docker VMs, which will hold those containers’ user data (not the container itself). The secondary VM disks are hosted inside Proxmox’s own NFS mount from the NAS.

Maybe there’s a better way to map the storage, but honestly I’ve learned an absolute shitton about how to properly set up Linux permissions and service users through this whole process. Plus, if the Mac mini was shut off from a power interruption or whatever, I would still have to manually power-on each disk in its USB-connected enclosure.

Unfortunately, during this migration process, one of my 4TB Reds refused to play nice, and checking the SMART stats showed multiple failing sectors. It has 69k (nice) hours, same as its twin. I had anticipated this, as I bought the first pair of EFRX Reds back in 2018, so about a year or two ago I added a newish 4TB Black as a hot spare (already had it, wasn’t using it for anything else). By the time I found the dying Red, mdadm had already automatically removed the Red from the array, pulled in the spare Black, and rebuilt the array. Fucking awesome. Both legitimately and sarcastically…

Obligatory pics!

Fully assembled:

OS install:

And its original config from HP, right before I tore it apart. Check out that dust blanket:

Full specs:

Edit 10/8/26 - finally migrated: https://lemmy.dbzer0.com/post/76651987

I’m finally getting around to migrating my OMV-based NAS from its current “2014 Mac Mini + USB multi-drive enclosure” setup to a more reliable build that doesn’t rely on USB. But I’m torn on CPU choice.

The “new” system is based on Intel 7th gen hardware, since that’s what the majority of my whole homelab runs (with zero complaints). The motherboard is an Asus Prime Q270M-C, meant for more commercial applications, and supports Intel’s vPro/AMT/ME/whatever it’s called (“vPro” from here onward) OOB management setup. I would really like to utilize vPro since I’m familiar with it and most of my machines have this enabled (and not accessible from outside my LAN).

The only compatible 7th gen CPUs with vPro are the i5-7500/T, i5-7600/T, and i7-7700/T. All are cheap (≤$50), easy to find on eBay, and I have no issues using the 35W T SKU. That said - I have a spare, yet perfectly functional Pentium G4560T sitting on my desk, but the only reason I haven’t installed it yet is because it doesn’t support vPro. I also have a 6th gen i5 (which the Asus mobo also supports) in an unused Optiplex 3040 SFF somewhere in my basement, but I don’t think that CPU supports vPro. I should check…

Anyway, I have some options:

1. Use the G4560T and deal with no vPro.
2. Swap the G4560T for the i7-7700T currently installed in my HA instance (Lenovo M710q), but then deal with virtually zero CPU overhead in HA.
3. Buy an i5-7500/7500T
4. Buy an i5-7600/7600T
5. Buy an i7-7700/7700T

I don’t have an issue with any of these options, even losing vPro is something I can deal with. But I like having overhead, and hate having extra hardware laying around.

What say the Lemmings?

P.S.: For those interested, this is the planned NAS build.