stuck at boot on spa_history.c while setting cachefile

[m0nsieurPsych0]

Hi there!

I have been having this error at boot a couple of time over the years and I thought this error was caused from bad usb drives. Every time, I was able to resolve this issue by reinstalling Truenas/Freenas on another usb drive and restoring the config from backup. Lately, I have ditched the usb boot drives in favor of a mirror of two hdd, but again this error came back as of last night. In the last couple of days I had issues with one of my UPS that I have now replaced, but it did cause the system to unexpectedly shutdown a couple of times.

Now, I don't think this error is related to the status of the either the boot pool or the storage pools. When it get stuck at

Code:

spa_history.c:296:spa_history_log_sync(): command: zpool set cachefile=/data/zfs/zpool.cache Stratos

I am still able to press CTRL+C and skip that part and boot the rest of the way. Unfortunately, the system seems to not be loaded properly as I am not able to access either the web interface or the ssh connection. I am however to ping the server and to locally log in with root.

When I log in and I run

Code:

 zpool status 

everything seems to be OK, no error detected either from boot pool or my two other pool Atlantis and Stratos.
I checked the services and middlewared is running, sshd is running and nginx is running. I've tried restarting the services but still I cannot access remotely.
Also, the pool are mounted and I can access the file within them.

I have to add that the console is spammed by an system message pertaining to

Code:

 collectd 1738 - - plugin_dispatch_values: [...] 

and I admit I am not sure if it's bad or not.

To be honest, I don't feel like re-configuring everything from scratch and re-importing the pool if there is an alternative solution available. Since I was not able to find much info about this issue on google or here, I am asking for your help.

Thank you!

PS: keep in mind, that I am not able to easily copy the error message/logs since I can only interact with the local console so here's some picture I took of the problem.

 

[m0nsieurPsych0]

So I was able to recover from this somehow. All I did was boot from the second disk in my mirror config and after letting it run for a while it finally booted.

In the alerts I do have a warning that says:

Code:

The following system core files were found: python3.9.core. Please create a ticket at https://jira.ixsystems.com/ and attach the relevant core files along with a system debug. Once the core files have been archived and attached to the ticket, they may be removed by running the following command in shell: 'rm /var/db/system/cores/*'.
2021-07-13 17:05:57 (America/New_York)

I am going to open a jira ticket, not sure what will come out of, we will see.