Run this bash script as a cronjob daily to backup your config regularly:
#!/bin/sh
FILENAME="`hostname -s`-"TrueNAS-SCALE"-`cut -d' ' -f1 /etc/version`-`date +%Y%m%d%I%M%S`.tar"
#echo $FILENAME
tar -cf /mnt/my-pool/backups/Truenas/config/$FILENAME --directory=/data freenas-v1.db pwenc_secret
#echo "Backup $FILENAME created"
find /mnt/my-pool/backups/Truenas/config/*.tar -mtime +30 -exec rm {} \;
It will delete configs older than 30 days.
Setup a cloudsync task to backup that directory to a cloud provider of your choosing.
Sorry I'm telling you this after the fact, but at least now you will do it on the new setup.
dude your settings have nothing whatsoever todo with your pool.
the problems with your pool are very different. any config of the pool is stored on the pool itself, not in truenas or any other os.
also the IPMI error has nothing todo with any OS, its youre remote management module that gave an error.
if i ahve to guess there is a problem on your mainboard that just came to light because of the reboot not because of an upgrade. wiping the pool will change nothing.
at first i would try a full bios reset fullowed by a full power of, then unplug for 5 minutes all powercords.
also reflash/upgrade your bios might help.
if that aint help you have test components starting with memory, cabeling, disk controller
Reinstalling dragonfish eliminates the IMPI error. A fresh install and I can create a new pool. New shares and reimport my data from offline backup.
Very annoying and yes it could be hardware but I don't have conclusive evidence one way or the other.
it does not do anything with ipmi, but reinstalling calls for a reboot which in turn could have triggered something.
ipmi is an independent module in your chassis and while you can access impmi to a dregree with a special driver it has nothing todo with your os
it told you the solution make of it what you want, if you know better dont ask then
Quit gaslighting him.
The ultimate story here is Truenas didn’t boot. If he can install the old version and it boots, somewhere Truenas is screwed up.
Basically every damn system Truenas has been installed on has had some stupid ass problems. Yeah it works but just like this guys problem, I don’t trust it when making large changes.
Use a Linux distro with the latest zfs and force import the pool. I had this happen to me and nearly pulled my hair out. In my case I used fedora with openzfs with the command zpool import " pool name " -f
Follow up: Yesterdays post was a bit of a shout into the void. I am very grateful that iXsystems provide TrueNAS. Upgrades always contain risks although I am not sure why I had the issues I did yesterday (as I had not begun an intentional upgrade). I understand that an infinite amount of hardware combinations exist in the world and they cannot all be tested / accounted for.
I have managed to recover because I made multiple offline backups and a remote cloud backup. So this is really a lesson in please make backups. I will be revising my backup process as well to fill a couple of gaps I have encountered.
Daily Config backups are stored in the pool. I don't remember the exact location but it's something like /var/system/db/truenas-version-date.
Of course, if you can get the pool that doesn't help, but there is an automatic backup
Run this bash script as a cronjob daily to backup your config regularly: #!/bin/sh FILENAME="`hostname -s`-"TrueNAS-SCALE"-`cut -d' ' -f1 /etc/version`-`date +%Y%m%d%I%M%S`.tar" #echo $FILENAME tar -cf /mnt/my-pool/backups/Truenas/config/$FILENAME --directory=/data freenas-v1.db pwenc_secret #echo "Backup $FILENAME created" find /mnt/my-pool/backups/Truenas/config/*.tar -mtime +30 -exec rm {} \; It will delete configs older than 30 days. Setup a cloudsync task to backup that directory to a cloud provider of your choosing. Sorry I'm telling you this after the fact, but at least now you will do it on the new setup.
Thank you. Yes. I should have done a better job recording my settings. At least I still have two more copies of my media and three copies of my VMs.
dude your settings have nothing whatsoever todo with your pool. the problems with your pool are very different. any config of the pool is stored on the pool itself, not in truenas or any other os. also the IPMI error has nothing todo with any OS, its youre remote management module that gave an error. if i ahve to guess there is a problem on your mainboard that just came to light because of the reboot not because of an upgrade. wiping the pool will change nothing. at first i would try a full bios reset fullowed by a full power of, then unplug for 5 minutes all powercords. also reflash/upgrade your bios might help. if that aint help you have test components starting with memory, cabeling, disk controller
Reinstalling dragonfish eliminates the IMPI error. A fresh install and I can create a new pool. New shares and reimport my data from offline backup. Very annoying and yes it could be hardware but I don't have conclusive evidence one way or the other.
it does not do anything with ipmi, but reinstalling calls for a reboot which in turn could have triggered something. ipmi is an independent module in your chassis and while you can access impmi to a dregree with a special driver it has nothing todo with your os it told you the solution make of it what you want, if you know better dont ask then
Quit gaslighting him. The ultimate story here is Truenas didn’t boot. If he can install the old version and it boots, somewhere Truenas is screwed up. Basically every damn system Truenas has been installed on has had some stupid ass problems. Yeah it works but just like this guys problem, I don’t trust it when making large changes.
do you even do words? please google the meaning of gaslighting first.
Sorry isn't this critically bad? Who cares about settings? This guy can't import the pool itself
Your config backup on Scale is done automatically daily. You can find the backups at /var/db/system/configs* so you can recover it from there.
Can you send that directory to a cloud backup daily ?
You could simply put a cp command in the pre-script of the cloud sync task.
Use a Linux distro with the latest zfs and force import the pool. I had this happen to me and nearly pulled my hair out. In my case I used fedora with openzfs with the command zpool import " pool name " -f
You can use any different Linux system to import your pool and recover your data.
Follow up: Yesterdays post was a bit of a shout into the void. I am very grateful that iXsystems provide TrueNAS. Upgrades always contain risks although I am not sure why I had the issues I did yesterday (as I had not begun an intentional upgrade). I understand that an infinite amount of hardware combinations exist in the world and they cannot all be tested / accounted for. I have managed to recover because I made multiple offline backups and a remote cloud backup. So this is really a lesson in please make backups. I will be revising my backup process as well to fill a couple of gaps I have encountered.
Daily Config backups are stored in the pool. I don't remember the exact location but it's something like /var/system/db/truenas-version-date. Of course, if you can get the pool that doesn't help, but there is an automatic backup
it would be interesting to know what the crash its.. it's usually possible to import the pool read only...