TrueNAS Scale 25.04.0 Upgrade disaster

Hi all! I am new here and know just enough about TrueNAS to be dangerous… I set up my NAS a little less than 2 years ago and it’s been running great.

The other day I decided to go ahead and upgrade to the latest version of TrueNAS 25.04.0.

I was running 23.10.2 and upgraded in a few steps instead of just all at once. The problem was, I did not check everything between upgrades so I have no idea when the problem occurred.

Once 25.04.0 was running, I noticed I could not access any of my shares from my network computers. When I went into the web interface and started looking, I could see all the disks, I could see the shares but under storage it showed VDEVs offline.

When I selected “Add Pool” it shows " * 3.64 TiB HDD x 3 (WizzPool)"
When I select “IMPORT Pool” is does not show WizzPool or any pools to import.

I have these errors also (which I do not understand):

"### CRITICAL

#### Failed to configure kubernetes cluster for Applications: Missing "WizzPool/ix-applications/releases, WizzPool/ix-applications/k3s" dataset(s) required for starting kubernetes.

2025-05-25 20:01:21 (America/New_York)

Dismiss

cancel

### CRITICAL

#### Failed to sync TRUECHARTS catalog: [EFAULT] Failed to clone 'https://github.com/truecharts/catalog' repository at '/mnt/WizzPool/ix-applications/catalogs/github_com_truecharts_catalog_main' destination: Cmd('git') failed due to: exit code(128) cmdline: git clone -v https://github.com/truecharts/catalog /mnt/WizzPool/ix-applications/catalogs/github_com_truecharts_catalog_main stderr: 'Cloning into '/mnt/WizzPool/ix-applications/catalogs/github_com_truecharts_catalog_main'... fatal: could not read Username for 'https://github.com': No such device or address '

2024-07-12 06:36:40 (America/New_York)

Dismiss

cancel

### CRITICAL

#### Device: /dev/sdb [SAT], not capable of SMART self-check.

2025-03-19 18:56:53 (America/New_York)

Dismiss

cancel

### CRITICAL

#### SMB shares have path-related configuration issues that may impact service stability: Archives: Path does not exist., Documents: Path does not exist., Media: Path does not exist., TimeMachine: Path does not exist., Backups: Path does not exist.

2025-05-25 20:01:17 (America/New_York)

Dismiss

cancel

### CRITICAL

#### Pool WizzPool state is OFFLINE: None

2025-05-25 20:01:20 (America/New_York)

Dismiss"

I also tried rebooting into 23.10.2 but I have the same issue now.

Any suggestions would be greatly appreciated!!!
John

Join the club.

Sorry, but its important to follow the update instructions in the release notes.
The only path that gets tested and validated is that. 25.04 (Fangtooth) Version Notes | TrueNAS Documentation Hub

In each version, we may have some migration steps which clean up issues between versions. For example, 24.04 - 24.10 includes App migration from K8s to Docker.

This is the key diagram:

For rollback to 23.10 it should work, but it depends on whether you updated the pool. What did you in 25.04.0??

2 Likes

I did the steps, one upgrade at a time but yes, failed to do any interim items. I haven’t been able to do anything with the pool. So I don’t believe I could have updated it and I sure didn’t do anything purposely.

What are the steps to role back to 23.10?

Thank you!

So, I assume you don’t know when the issue started… and you didn’t actually import the pool at each step?

If w have no clue as to why, we should probably just focus on getting pool to import again on 23.10.

Can you write up the hardware and specific steps? Do you have the config file and software to reinstall if needed?

What is the sdb device?

System > Boot > activate the 23.10 boot environment, reboot.

4 Likes

Unfortunately you are correct. It never occurred to me to do this…

AMD FX™-8350 Eight-Core Processor, 16 GB ram, 3 WD 4TB - WDC_WD40EFRX-68WT0N0, Boot Disk - TOSHIBA-TL100 SSD - 120GB, MB - Gigabyte 990FXA-UD3.

I used “Update” within TrueNAS to run through each of the available updates. I had forgotten that when I first tried to run the updates, I did try and go right from 23.10.2 to 25.04.0 because it seemed to show that that was an available update path. It did fail the update and that’s when I went back and did each step…
23.10.2 > 24.04 > 24.10 > 25.04. BUT, as I said earlier, I did not even think about having to import the Pool at each step.

I booted into 23.10.2 and the pool shows there but inactive and it does not show up under import just like in 25.04.

Under Disks, it shows the pool as “Exported”, I just can’t do anything with it.

Thanks!

Thank you! I did this with no luck…

It’s looking like the pattern I’ve been noticing very recently, hence my redirect. :slightly_frowning_face:

After you tried to go direct from 23.10.2 to 25.04 and then reverted back when it failed, did you check that the pool was online at that point before you did 23.10.2 to 24.04?

Some of the errors relate to K8S used for Apps.
By updating you triggered some migration processes to Docker.
This process is not reversible.

What Apps were you running?
Can you recreate them?

The sdb error about SMART - I don’t understand. Which device is that… is it part of the pool?

Bottom line… you may have to go back to 25.04, lose your apps, and troubleshoot the pool import issue there.

Weird, I thought one point of moving to ix-apps instead of ix-applications was so that the user would be able to go back, if needed.

The only app I was running was a Pi-hole. I actually hadn’t even been using it recently because it did not seem to be working. I am fine with loosing that and starting over.

Yes, sdb is 1 of the 3 WD drives.

OK, I have no problem doing that. BUT, where in the world do I start?

Thanks for all the help so far!!!

Is 25.04 still on of your boot environments??

Yes, I just rebooted into 25.04.0.

Also, once I did that I noticed that sdb is now my boot disk and not 1 of the 3 WD drives. It’s like it renamed them in 25.04.0. I’m wondering if the SMART error is because it’s an SSD?

Thanks!

Don’t know where or why that would happen?

Its a good lesson in making sure that each step works… we could see where the problem was created.

So, you’ll have to fix the boot pool 1st…

I’m not sure what to do with it at this point. When I try to run a manual test on it, it says “Self-test function not supported”… Here is the message I get…

No, stupid me it never even crossed my mind… :anguished:

This is the Toshiba SSD… it may not support SMART??

Yes, and I think that is what is driving that critical error I posted originally since it is saying almost the exact same thing.

So, I’m guessing there is nothing wrong with the boot drive/pool… Would that be your assessment also?

Thank you!