Today I completed migrating over to TrueNAS Scale. Unfortunately I had issues making the file transfer over SSH, likely due to using passwords instead of SSH keys. So I transferred the files by hand instead.

The initial setup was difficult due to poor documentation, but overall the flow was simple.

The problem I personally found was that QuTS Hero keeps making trade-offs that I didn't like. It kept dumbing down the core components (like ZFS) to make it easier for newbies, at the expense of making it harder for people like myself who already knew what ZFS commands they wanted to run. It also made the UI overly complicated, with a full virtual desktop environment in the browser, instead of a traditional admin interface.

After having had a great 10 years using my Fractal Node 304 case (with upgrades over the years including a new RAID controller), I have decided to switch to a purpose-built case with hot-swap bays.

Here's the hardward I'm currently running, which I intend to replace:

When doing this, I would also like to select a combination of software and hardware that will allow me to see clearly which disk needs to be replaced, when failure does happen.

I have, however, otherwise had a great experience with FreeNAS (and then TrueNAS Core) over the years, and am highly impressed with ZFS, so I'd like to keep as much other stuff the same as possible.

I've chosen to split the CLI out of this project, and make this project a standalone docs project.

This is because:

• A monorepo is overly complex for what I need
• I don't need to have the two tightly coupled in deployments
• I can now open-source these docs without needing to worry about my CLI

This marks a pivot for this site to now document thoughts and configuration around my server, rather than the CLI I use to automate repetitive tasks.

I will probably continue to document the thinking and changes I make in these blogs anyway, but that remains to be seen.

Using a monorepo was ambitious for this project, and upon reflection, the docs and main project do not have any need to be deployed in sync.

As such, I've elected to split the server-admin into server-admin-docs and server-admin-cli.

Currently, only server-admin-docs exists. I expect to create the -cli part either later today, or at some point in the near future.

Today I chose to create this project, with a mix of documentation and a CLI in a monorepo structure. Hopefully, it'll prove easy to maintain.