Failed Core to Scale upgrade

Even though I’ve been running freenas/Truenas for years, I’m a noob concerning anything to do with it. It has just worked.
Last weekend I attempted to upgrade from Core 13.0 U6.1 to Scale 23.10.2. This failed because of geli. I had the system boot back on Core and this weekend removed the encryption based on this article:

Everything looks fine but I cannot move forward with the upgrade. The error “30 is not a valid pool status” appears to be the issue. If I try to scrub the pools my main data pool is fine, but the 30 error appears to be an issue with the boot pool.

midclt call freenas-boot 7
30 is not a valid PoolStatus

Output of zpool status on freenas-boot:

root@freenas-1[~]# zpool status -v freenas-boot             
  pool: freenas-boot
 state: ONLINE
status: This pool has a compatibility list specified, but it could not be
	read/parsed at this time. The pool can still be used, but this
	should be investigated.
action: Check the value of the 'compatibility' property against the
	appropriate file in /usr/local/etc/zfs/compatibility.d or /usr/local/share/zfs/compatibility.d.
  scan: scrub repaired 0B in 00:00:17 with 0 errors on Fri Apr  5 03:45:17 2024

	freenas-boot  ONLINE       0     0     0
	  nvd0p2      ONLINE       0     0     0

errors: No known data errors

Again, I wish to stress I’m a noob at this and do not want to make things worse. The system is a TRUENAS-MINI-3.0-X+

Any help or additional information I can provide would be greatly appreciated on next steps.

Thank you in advance.

First of all, Welcome to the forums. Too bad it couldn’t be on better circumstances.

  1. Backup all your data! if possible.
  2. From the TrueNAS GUI, save a copy of your TrueNAS configuration files. These will be important shortly.
  3. From the CLI/Shell run zpool scrub freenas-boot
  4. From the CLI/Shell run zpool scrub your_pool_name
    If you have multiple pools, run a scrub on all of them.
  5. Run zpool status -v
  6. Make sure your pools do not have any errors. If the freenas-boot has an error, we can life with it for now.
  7. If you have any pool errors, those need to be fixed.
  8. If all your main pools are in good condition, it is time to do the unthinkable (just kidding), I can’t tell what your hardware is, you should post that kind of information when you as a question, but I want you to remove your boot drive if possible to save it for now, replace it with something else. This could be an 8GB or better USB flash drive, SSD, HDD, you get the idea.
  9. Download the complete ISO of TrueNAS 23.10.2 and install TrueNAS to this new boot drive. Or if you desire to go back to CORE, use that ISO.
  10. In the TrueNAS GUI, upload your old configuration file. A reboot should have your system running normally again.

This should work fine.

If all is lost and you at least have a backup of your data, you could just destroy everything and start all over using SCALE. It really depends on the data you have and applications you may be running.

Good Luck.

EDIT: If you get an error message, if you know what is going on then act on it, if not, post what is happening so we can provide you good advice.

Thank you for the quick reply. It will be at least next weekend before I can try anything new. I’ve scrubbed my data pool and it is in tip top shape. The problem appears to be with the freenas-boot pool. The scrub completes and the pool is accessible, but complains about a compatibility list issue.

The system is an iX Systems TRUENAS MINI X+. A system produced by iX Systems.

The next time I get some time with the system I will attempt to boot from a USB stick and reinstall the boot pool unless you think that is a bad idea. I have the config for the NAS backed up, I’m just concerned the cause of the ‘30 is not a valid pool status’ error is in that config. Fingers crossed.

@joeschmuck couldnt he just export his pool, unplug all the disks, install scale and import pools again? as long it isnt encrypted that should work. but as always, do a backup and then try.

Yes, sort of, that is what I’m basically doing, just without exporting and importing. The boot-pool must be recreated. If you save the TrueNAS config file, then reinstall TrueNAS over the boot drive (I prefer to use a different boot drive if available, allows rolling back time if you must), and when you boot up, you use the GUI to restore your config file, reboot (should happen all on it’s own), and the pools should be automatically mounted. It’s the same configuration so I don’t export the pool, but you could do that, I personally find it not required.

Thanks again guys,

I’m pretty sure I have a spare NVMe drive sitting around I can swap in for the current boot drive to preserve the original ‘just in case’.

Thanks again,