TrueNAS 2026.5

Apr 28, 2026 | IT | 0 comments

My blogging fell off the radar again last year due to some personal reasons I really didn’t feel like blogging about (even though I thought about it) and though I drafted a few blogs I never got around to finishing them.  I’ve been playing around with AI, bought a new MacBook and have tested numerous other devices for work (including typing this on a MacBook Neo) and while these are usually things I would blog about, I’ve never really felt the urge.

I did spend a week at home at the beginning of April over the Easter holiday for a change and spend quite some time tinkering with my TrueNAS box getting everything up to date, so what better way to try and ease myself back in than a TrueNAS 2026.5 update!

One thing that’s hasn’t changed is that I’m still running TrueNAS 13.3 although FreeBSD 13.5 will be going EOL later this year which is likely to start to cause me some issues. There have been a couple of minor 13.3 updates (I think the latest version is 13.3-U1.2) but it’s not going to fix the underlying FreeBSD issues which I’ll get into a little later.  Let’s start with the Jails as usual:

Airsonic

No change.  This is no longer updated, but it still works and is a reliable backup for streaming music if I need it.  I don’t do anything and it automatically picks up any new music I add so is still running.

emby

It’s still my media server of choice and something I (and several family and friends) would be lost without. It’s running 4.9.3.0 which is the latest stable release.  I’m still not playing with beta releases as have fallen a little out of love with the emby community given the lack of support for various suggestions, not least MFA.  I still use emby daily though with no plans to change that.

Nextcloud

Still the most important jail.  Although I could use OneDrive or iCloud for this if push came to shove, I like the fact my data is kept local.   The integration with ONLYOFFICE still works reasonably well, although I’ve had a few issue with this losing the connection and updating the VM.  It is running the latest version 33.0.1 (from 30.0.4 in the last blog), with MariaDB 11.8.5 (from 10.6) and PHP 8.4.(from 8.3)

Limesurvey

I eventually found the problem I was having with this, which was an unsupported theme I’d installed.  I removed that which then allowed me to update PHP to 8.4 (from 7.4, which hasn’t been supported for some time), So everything is up to date including running a beta version of Limesurvey (7.0. from 6.6.6) and MariaDB 11.8.5 (from 10.6).  All that said I haven’t run a survey in over 2 years, but it is still handy to have it running, which is why I keep it up dated, or at least do now!

MediaWiki

I rebuilt this again at the beginning of 2026 as I’d left it as an open blog and it became ‘infected’ with pages and pages of spam posts, to the point that trying to clean it was not an option, so I wiped and reinstalled.  It’s now only available to logged in users and hidden behind my NGINX proxy.  It has the latest version of PHP 8.4 and MySQL 8

OpenVPN

Up to date but using this less as one of the other things I’ve been playing with and drafted a blog was zero-trust solutions.  I’ve tried Tailscale and Twingate and have been using them more to access things inside my network. It’s currently running 2.6.16 (from 2.6.12) so it doesn’t really change much anyway.

WordPress

Still just running this blog, so hasn’t really seen much use by I have kept it up to date, so it’s running WordPress 6.9.4 (from 6.7.1), MariaDB 11.8.5 (from 10.6) and PHP 8.4 (from 8.3).

The test instance on Docker is also running 6.9.4 but an unsupported version of PHP (7.3) and MariaDB (10.4) and I’s still thinking I should take this down. It was built when I was thinking about starting up a web development company, but that didn’t happen, and I suspect it never will.

I have deleted all the old jails except for calibre, although I’m not using that as I have a Calibre-Web Docker running.  I’m not sure why I’m holding onto that?

I haven’t neglected the Virtual Machines this year, and everything is now running ubuntu 24.04.4 LTS, although 26.04 was released earlier this week!  That gives me about 3-4 years to upgrade!  I’ve also been keeping all (well most of) the containers/applications updated as per the table below: 

So almost mid-way through 2026 I’m more up to date across my whole ‘micro datacentre’ stack, from an infrastructure-platform-OS-application perspective, than I probably have been for some years.

Storage is still a problem, but still not a major one, well at least not for my main machine.  I am down to 9.9TB on FreeNAS0 (76%), my HDD pool, and 243GB on FreeNAS0s (73%), my SSD pool (which is a slight improvement from 75% last time!)  Both are still much higher than I like, and the situation with TrueNAS is going to need some serious thought over the next 6-12 months.  

FreeNAS1 is my backup server, which I no longer run 24×7 due to energy costs and space.  It comes out every few months and I back up the important stuff from FreeNAS0(s), but that’s now over 90%, so I’m not backing up everything.  I even had to remove everything from FreeNAS1 and complete a full backup/resync as I reached the 100% limit due to some old snapshots from 2021.  CrashPlan continues to do the offsite stuff in the background, so my backup strategy is still robust, and it’s good I’ve never needed it, touch wood!  That said, FreeNAS0 is making some horrible noises at the minute making me think a drive is about to die.  The HDD pool is in a RAIDZ2 array, so I can afford two simultaneous drive failures without losing any data but just losing one and then resilvering a new drive would be nerve wracking, so I’m not looking forward to that.

I haven even more Raspberry Pi’s running stuff now but still have the Pi4 running a SATA-SSD, which runs an up-to-date version of the Home Assistant Operating System 17.2 (from 14.1) and an equally up-to-date version of Home Assistant Core 2026.4.1 (from 2025.1.0). In addition to providing all the home automation for my Philips Hue lighting and TP-Link switches, I have various integrations for my Tesla and Octopus Energy. Still, the most important is probably the Addon for NGINX Proxy Manager, which controls all access to my network and the Certbot certificate renewals every three months. This has worked brilliantly since I switched from doing this semi-manually in a jail, which I blogged about here!

Anyway, that was my mid-year TrueNAS update!  I’ve drafted this in Word on a loan MacBook Neo, so the big question is now whether this eventually makes it onto my blog.  I think I’m losing my ability to finish things I’ve started as I get older, which I need to address!  I genuinely thought I’d lost this after resetting the MacBook Neo as the supplier wanted it back, but fortunately it autosaved to OneDrive, so i thought I better upload before changing my mind!!

Kidney Stones

Mar 15, 2025 | IT | 0 comments

This was written over a few sessions across a few weeks, so the dates might feel a little off.  Sorry, but it’d been a hell of a start to 2025.

Well, this is a first, and hopefully after the three weeks I’ve just had, most of which was spent in bed, the last time I’ll be blogging about kidney stones!

I’d heard of kidney stones, but didn’t have any idea what they were, what caused them and quite how painfully they are if you’re unfortunate enough to get one.  I also had no clue that’s what might be causing the excruciating pain I suffered late on the 27th of January.  I’d been out to play badminton for the first time in 2025 after spending the end of 2024 with a thigh injury.  It went OK and wasn’t too strenuous, and I felt quite good when I got home.  I went to bed at the usual time, read a little of my book on the Kindle, and then tried to get to sleep.  I had an aching pain in my side and struggled to fall asleep, and after about 30-45 minutes, I got up to get some paracetamol.  I just thought perhaps I’d pulled or twisted something playing badminton, but over the next hour or so the pain intensified and I eventually ended up calling the NHS24 number, a 24 hour service where they can advise on any health issues, and generally a better place to start when the GP surgery is closed and you don’t want to bother the local A&E department.

I got through quickly and explained my situation but was placed on hold while a nurse was available to discuss my problem.  After about 30 minutes the pain was unbearable, and I told my partner I just needed to go to A&E.  It was about 1 am at this point and my 12yo daughter was fast asleep in her room, so after some discussion and calls, my partner managed to get me a taxi to the hospital, which is about a 20-minute drive away.  I continued to hold with NHS24, and did eventually speak to a nurse enroute to A&E.  She advised that they would have probably referred this to an out-of-hour services, and not recommended A&E, but as I was on my way suggested I just continue, but they couldn’t tell me how long I might need to wait.  They did say they would update my record to say they had suggested going to A&E, which might speed things up, but there were no guarantees how busy St. Johns in Livingston might be.  She also mentioned kidney stones as a potential diagnosis, although I wasn’t paying too much attention at this point.

When I arrived, I checked in and sat close to the reception, trying to keep out of the way of the other people waiting.  I was clearly in pain and went to the toilet and was quite violently sick, which I think was down to the pain.  I only waited about 20 minutes before my name was called, and I saw a triage nurse to whom I explained the situation.  Again, they could see I was in lot of pain, and after some questions, I was given a syringe full of medicine to ease the pain.  They also found me a hospital trolly in a curtained room so I could lie down while I waited to see a doctor.  

I lost track of time a little at the hospital, in part due to the liquid morphine (oramorph) I found out they’d been giving me, but it did take away the pain even if it did make me somewhat out of it!  I think I saw a doctor between 5-6 am, and she asked a nurse to take an ultrasound scan of my bladder before and after I’d been to the toilet.  They also asked me for a sample (after I’d emptied my bladder, but I’d been drinking lots of water, so I went again not long after.  The blood in my urine (nothing visible) was what pointed them toward the kidney stones, and I wasn’t showing any sign of infection but was in lots of pain.  The doctor arranged for a CT scan, which they did about 8 am, and this identified a 6mm stone and was the diagnosis for my pain.  After this, they seemed keen to send me home, and as the pain was under control, I was more than happy with this.  They prescribed some more Oramorph, which I collected from the hospital pharmacy, and my partner picked me up and took me home.

I remained out of it for the next few days, taking Oramorph every 4 hours, although this didn’t keep on top of the pain, especially during the night when I wasn’t talking any.  I’d spoken to the Urology department at the Western General Hospital in Edinburgh, which is where they had referred my case, and they only review new cases on a Tuesday morning, so the timing of my diagnosis meant I needed to wait a full week before I heard from them.  I’d called work to tell them I’d be off for a few days and spoken to my GP about the medication, as I was still finding myself in lots of pain.  They initially prescribed some more Oramorph and told me to take more of it, but this just made me even more out of it!  They eventually prescribed some Co-codamol, which managed to keep the pain to a dull ache rather than a stabbing pain, which I could manage better.  

I was just waiting for Tuesday afternoon so I could call the Urology department, but they called me before lunchtime.  They have an appointment for Lithotripsy the following Tuesday, which they suggested was the best and quickest option.  I was supposed to be on half-term holiday that week, going down to Durham for a few nights to see my Mum, but that wasn’t going to be much fun full of pain killers, so I was booked in and lots of information was sent about the procedure.  

Lithotripsy is the least invasive way of treating kidney stones, where they use shockwaves to try and breakdown the stone into smaller pieces, so you pass it normally as you pee.  I got through the next few days, and I even managed to do a little work from bed, although I’m not sure it was all that helpful!  

I wasn’t entirely sure what to expect when my partner drove me to the Westen General Hospital in Edinburgh for my lithotripsy appointment, but I don’t think I was expecting it to be so painful.  We’d arrived quite early due to potential parking issues and traffic, but I think the half-term holiday probably helped.  I changed into a gown and wore my Jedi batch robe for most of the time.  I’d not eaten anything, but I had taken a single Co-codamol first thing, which threw them in terms of the pain relief they could give me, but eventually, that was all sorted.  I’d been x-rayed, and the stone was in roughly the same place, so they knew what they needed to do.

The procedure lasted for about 45-50 minutes, and all I had to do was lie down on a bed with a cutout section about halfway down.  This allowed a water bag to be pushed up against my side, through which the shock waves were fired.  I’d be told it would feel like I was being flicked with an elastic band, with increasing intensity, but at least by the highest level, it felt more like being repeatedly punched in the kidneys.  I was given pain relief at various points, but it wasn’t at all pleasant.  Once finished, I had another x-ray and was told they had broken the stone, but little more detail than that. 

I was told I’d need a follow-up x-ray in two weeks, which would hopefully show the stone had passed.  This would be scheduled at St Johns, which is a little closer and easier to get to.  I did a little work from bed for the rest of the week although felt sore for the first few days but did manage to reduce the pain relief, so I’d taken nothing over the weekend.

The next week, I was back at work, and although I didn’t feel 100%, I felt OK and even managed to drive across to Glasgow for a supplier meeting.  We’d also rescheduled an emergency shorter trip down to Durham to see my Mum, who has been admitted back to hospital.  I was going to touch on that in this blog, but I think that might need to wait for a little while.  My daughter and I drove down on the Friday and headed back on the Saturday, after a couple of hospital visits and a short trip to the Metro Centre.

We’d been back about 3 hours, eaten some pizza and were watching The 1% Club when I started to get some strong pains like the first kidney stone pain, but at the front and lower down, around my bladder.  I’d taken some co-codamol, but within an hour, I was rolling around on the floor in pain again and on the phone to NHS24 again.  It was a slightly quicker process, and I’d not want to end up in A&E, and given I already had lots of pain relief at home, I managed to get on top of the pain more quickly.  I did get referred to the out-of-hours service, who called back within 15 minutes and said they’d like to see me at St Johns.

So, it was back in a taxi and across to the hospital.  The Out of Hours service is right next to A&E, but I didn’t have to wait and saw a doctor within 10 minutes.  She thought it sounded like the stone was moving again, and managing with pain relief was the only option.  I could do that from home or be admitted to hospital, which I didn’t fancy. I did give a urine sample, which again had blood levels ‘off the chart’ which supported the diagnosis.  I left with better advice on using the oramorph/co-codamol together, and over the next few days, I managed the pain reasonably well, to the point I wasn’t needing anything by the weekend again.  

I was back to work on Monday and then back at St. John’s on Tuesday for my follow-up x-ray, but they just took pictures and couldn’t tell me what the results said.  I followed up with the Urology department but was told they would review the x-rays over the next few weeks and be back in touch.  I’ve been OK since that point and back at work, albeit with a somewhat achy pain around the same area.  I even managed to get down and see my Mum again this weekend, which happened to be my birthday. She was now back at home, although in a worse place that I am.

I need to follow up with my GP next week, so try and get some feedback from the x-ray.  I still don’t know whether I’ve passed the stone, so I can only hope and keep everything crossed for the next few weeks that things get gradually better.  We’re heading on holiday to New York and Mexico in a few weeks, and I’m hoping I’m not going to need any of the pain relief while I’m there.  

Anyway, that feels like a monster blog, which I can’t imagine anyone would be all that interested in reading.  It will help me remember my kidney stone, although I don’t think I’ll ever forget the intense pain.  It was like nothing I’ve experienced before and not something I hope to have again.  I’ll try and write a blog about my Mum over the coming months, although that might be even more difficult.

Well, it wasn’t quite done!  I spoke to the GP surgery on the next Monday, and they’d not had anything back from the hospital and suggested following up with them.  I left them a message and made a note to follow up with them later in the week.  I’d bought tickets last year to see Fish’s very last concert in Glasgow on the 10 March, so I’d jumped on the train and after a quick bite to eat, walked down to the O2 Academy.  I was standing in the section nearest the stage, but not at the front and closer to the first steps up.  After a couple of songs, I wasn’t feeling great and decided to head to the back, hoping to find somewhere I might be able to sit.  I found a table that at least I could rest on, but after a couple more songs, I headed into the foyer for a break.  One of the O2 Academy staff could see I wasn’t well and told me there was a first aid office if I needed it.  I asked about a seat on the balcony, and amazingly, they managed to find me a great reserved seat from which I managed to enjoy the rest of the gig.

I walked straight back to the station afterward and got the train home, but when I arrived at 00:00, I was already in some pain.  Stupidly, I just took a couple of paracetamols, so after another hour or so, I was in agony again.  I took some Oramorph hoping that might help, but another hour later, I had some co-codamol and more Oramorph before calling NHS24, again!  It was quite a quick call this time, but I was already in a taxi when it finished, heading to St. Johns.  I’d had a call back from NHS Lothian, who booked an out-of-hours appointment as soon as I arrived.  That appointment wasn’t as great, and they took at least 30-45 minutes after speaking to me before staying. I needed to head to the Western General Hospital in Edinburgh, where they had a dedicated Urology department, which is where I’d had the lithotripsy.  40 minutes later and £40 in a taxi, and I was waiting at a different hospital.

To be fair, they saw me quite quickly, and I was given a bed while more blood and urine tests were taken and various doctors and nurses visited.  I’d been awake for quite some time by then and had lots more pain relief, so I was pretty much out of things for a few hours.  I had some more x-rays, and eventually a Urology consultant visited who’d reviewed everything over the last 6 weeks.  He went on to explain that the first hospital visit was for the stone leaving my kidney and trying to find its way into the urethra, which it couldn’t due to the size.  After the lithotripsy, the x-rays showed my stone had been broken in half (not very common, as they normally shatter into many smaller pieces), with one half finding its way into the urethra toward my bladder and the other heading back toward my kidney, which the consultant hadn’t seen before.  He then thought that the second hospital visit was caused by the first stone trying to get into the urethra from the bladder, which is the tightest part of the journey.  He thought I’d passed that, but this third visit was the second half of the stone reaching the same point.  He expected that to be passed too within the next 4-5 days, after which I should be stone-free.  I was sent home a few hours later after some more pain relief and further medication to help pass the stone.

I managed the pain at home over the next couple of days and had a trip to Durham to say goodbye to my Mum before updating this blog this weekend.  I’m hoping this is the last I’ll be writing about kidney stones, but who knows?

TrueNAS 2025

Jan 7, 2025 | IT | 0 comments

Well, I didn’t manage to blog every month in 2024, but I did manage more than 12, so I think that’s not a bad effort, given the two-year break!

I know that I have another TrueNAS blog to start this year (after not blogging for so long) here and here, but it has become a bit of an annual event to blog about my server and the services running on it.  Better not mess with that balance, so here’s what my boss would call a ‘state of the nation’ or a ‘view from the bridge’ for my TrueNAS server going into 2025…

The biggest change was upgrading TrueNAS from 13.0-U6 to 13.3, which updated the version of FreeBSD from 13.1 to 13.3.  This allowed the jails to be updated from 13.1 (which was no longer supported) to 13.3, or for most of my jails to 13.4, which is supported until the middle of 2025.  I think there will be a 13.5, which should also be compatible and supported into 2026, hopefully!  I blogged about all that here.  Although it was quite a challenge at the time, I managed to get the FEMP stack updated for most of the jails running this, which is a good place to start the year:

Airsonic

This is probably running the same version as it was when I did the blog at the end of 2022, as Airsonic hasn’t been updated!  As it was back then, it’s rarely used, and I’m now pretty much exclusively listening to music on Apple Music or occasionally through emby.  It’s a handy backup, and picks up music from the same place I save it for emby, so it takes zero effort to update.

emby

emby is still my media server of choice and something I (and several family and friends) would be lost without. It’s running 4.8.10.0 (from 4.7.14.0 at the beginning of the year), which is the latest stable release, and I’ve not tested the beta releases at all this year.

Nextcloud

This has become the most crucial jail for me, and while emby gives it a run for its money, I’d struggle without Nextcloud now.  I suppose I could migrate everything to Onedrive or iCloud, but the point is to keep my data local.  There isn’t an option to do this for emby, so I’d be equally lost without that, but I also have other people using Nextcloud, so this would be the most difficult to replace.  The integration with ONLYOFFICE makes it a genuine Office 365 alternative running from my micro-data centre!  I’m bang up to date, running the latest 30.0.4 (from 27.1.5), with MariaDB 10.6 and PHP 8.3 upgraded in 2024.

Limesurvey

This is the problem, child, as I’m struggling to update the version of PHP beyond 7.4, which hasn’t been supported for some time.  Everything else is up to date (Limesurvey 6.6.6 from 6.4.0 and MariaDB 10.6), and I’m not really using it in anger anymore as I’m no longer a Trustee for my daughter’s Out of School Club.  It’s handy to have running, though, so I keep it updated.  I might try to rebuild the jail to see if I can get PHP onto something supported.

MediaWiki

I rebuilt this during 2024, more to test how to upgrade MariaDB than anything else.  I still haven’t found a use for this; it wasn’t even listed in the previous update! Perhaps one day…

OpenVPN

I was always quite nervous about updating this, and I don’t do it all that often, but it’s never been a problem.  I still use it when I’m away from home, so I update it every 3-4 months.  It’s currently running 2.6.12 (from 2.5.3).

WordPress

This is just running my blog now, as the company (and website) are no more! I keep this pretty much up to date, so it’s running WordPress 6.7.1 (from 6.4.2), MariaDB 10.6, and PHP 8.3. The test instance on Docker hasn’t been updated for way too long, and I really should think about taking that down. It was built when I was thinking about starting up a web development company, but that didn’t happen, and I suspect it never will.

I still haven’t deleted my old calibre jail, but everything else (plex, Bitwarden, Minecraft and Photoprism) is gone.

Given all the changes to TrueNAS and the jails, the Virtual Machines have been a little neglected, at least from an OS perspective.  I run application updates and security patches but haven’t updated the OS. I think Ubuntu 20.04 LTS is supported until the middle of 2025, so 2025 might be the year of the VM.  I’m cheating here with a table very similar to the one used at the beginning of the year:

 

 

Name	OS 2024	OS 2025	Application(s)
cplan	ubuntu-desktop 22.4.3	ubuntu-desktop 22.4.3	This runs Crashplan exclusively, and I forget it’s there, other than the weekly e-mail to remind me it’s backing up my TrueNAS server and the monthly invoice for $11.99!  It’s still the cheapest I can find for offsite backup, which is especially important as my onsite backup no longer runs 24×7, given the rising electricity costs and a remodelled home office with no space for two large workstations/servers. It does get updated every few months, but it’s nice to know that Crashplan has a much more up-to-date backup.  I’m using about 2.5TB of storage!
mattermost	ubuntu server 20.4.2	ubuntu server 20.4.3	I should upgrade the OS for this one, but it is still supported until 2025 and will be updated whenever I update the LTS release of Mattermost. It was running 8.1.0 and is now running 9.11.0.
oedocs	ubuntu server 22.4.3	ubuntu server 22.4.3	I should have called this oodocs, as it’s running ONLYOFFICE Document Server, which I use with Nextcloud, but it just works, so I have left things alone. I’m getting wiser in my old age! It’s updated every few months and is currently running  8.2.0 (from 7.5.0).
pihole	ubuntu server 22.4.1	ubuntu server 22.4.1	Another one I update regularly has worked brilliantly to hide most advertising when web browsing, but also speed up DNS searches using unbound.  The version of PHP is lagging a little behind on 8.1, but Pi-hole is running the latest 5.8.3, although it must be due for an update soon.
portainer	ubuntu server 20.4.4	ubuntu server 20.4.4	It’s another with the wrong name, as it’s running all my Docker containers, although one is Portainer. It is hard to cover them all in detail here. Still, the main ones are Bitwarden, Calibre-web, Teslamate/Grafana, Uptime Kuma, WordPress (a development version), and other web tools (LEMP stack, phpmyadmin, etc.)

I guess you’d summarise the year as ‘updated jails, maintained VMs,’ but most things are running supported versions of the app, database and supporting stack, other than a few exceptions.  Storage is starting to become more of a concern.  I am down to 12.2TB on FreeNAS0 (70%), my HDD pool, and 228GB on FreeNAS0s (75%), my SSD pool.  Both of these are higher than I like, and while I still have another year or so, I really need to give some thought to my future strategy in 2025.  FreeNAS1 is my backup server, which I no longer run 24×7 due to energy costs and space.  It comes out every month or so, and I back up the really important stuff from FreeNAS0(s), but that’s now over 90%, so I’m not backing up everything.  CrashPlan is still doing the offsite stuff, so my backup strategy is still robust, and it’s good I’ve never needed it, touch wood!

 

 

I’m still running a Raspberry Pi 4 from an SSD, which runs a pretty up-to-date version of the Home Assistant Operating System (14.1) and an equally up-to-date version of Home Assistant Core (2025.1.0). In addition to providing all the home automation for my Philips Hue lighting and TP-Link switches, I have various integrations for my Tesla and Octopus Energy. Still, the most important is probably the Addon for NGINX Proxy Manager, which controls all access to my network and the Certbot certificate renewals every three months. This has worked brilliantly since I switched from doing this semi-manually in a jail, which I blogged about here!

Anyway, that was my New Year TrueNAS update!  It feels like a while since I’ve wished anyone reading this a happy New Year!  I’m hoping to keep blogging through 2025, as enjoyed my return in 2024.  It wasn’t perhaps as regular as I’d planned, but I think I managed an average of a blog month which will be the target again for 2025.

Let’s finish with a gallery of logos, which I think helps to show the scale (pun intended) of what I’m running on my TrueNAS Core server.  I hope you have a wonderful 2025…