TrueNAS stucked in check-ha status

Bymarek

You can check the version of each controller from the CLI with the following command:

cat /etc/version

On the system that is NOT running 12.0-U81., you would want to run the following commands:

That command will pull the latest download file

freenas-update -T TrueNAS-12.0-STABLE -v check

That command will create the boot environment

freenas-update -T TrueNAS-12.0-STABLE -v update

After that „update“ command finishes (5-10 minutes or so), you will need to type „reboot“ to reboot the controller and have the update take effect.

reboot

Following that process, you should have both controllers running the same OS.

If you bought a Support option from ixsystems you can log into the UI and provide a new debug so ixsystems can verify system health/status.

Similar Posts

Migrating VMs from Hyper-V to Proxmox

Bymarek

Migrating virtual machines from Hyper-V to Proxmox allows you to leverage the flexibility and features of Proxmox VE. This process involves exporting the VM from Hyper-V, converting the disk format from VHDX/AVHDX to QCOW2, and configuring the VM in Proxmox. With this step-by-step guide, you’ll ensure a smooth and efficient transition, preserving your VM’s settings and performance while preparing it for optimal use in Proxmox.

Automatically Shutdown Your Linux System 8 Hours After Booting with systemd Timer

Bymarek

Set up an automatic shutdown on your Linux or TrueNAS SCALE system using systemd timers to power off the machine 8 hours after boot. This approach helps automate processes and conserve energy. You can also manually interrupt or modify the shutdown timer whenever needed.

Automating Proxmox (PVE) Shutdown: A Simple Guide

Bymarek

Proxmox VE provides a straightforward way to manually shut down your server, ensuring all virtual machines (VMs) and containers stop gracefully. However, if you need to schedule automatic shutdowns, the web interface lacks a built-in scheduler. In this guide, we’ll explore how to manually shut down your Proxmox node, set up an automated shutdown using cron, and configure the startup and shutdown order for your VMs.

Why You Should Keep Your ZFS Pool Below 80% Capacity

Bymarek

ZFS pools should ideally stay below 80% capacity to maintain performance and reliability. Exceeding this limit can lead to slow write speeds, increased fragmentation, inefficient space allocation, and prolonged scrub or resilver times. This article explains the technical reasons behind this recommendation and provides best practices for keeping your ZFS pool running efficiently.

Why ashift Matters in ZFS: Getting It Right for Performance and Longevity

Bymarek

With ZFS, ashift is your key to matching your drive’s stride. Choose the right size for your disk to keep writes quick and wear low. Set it too small, and it trips over itself; too big, it overpacks space. Get it spot-on when you begin, and enjoy a smooth, lasting storage setup.