I broke access to TrueNas 12.0-U4

[Jedrek]

I am asking you for help in restoring my NAS. Since I had an error in the data indications after the update, I used this method: https://github.com/truenas/middleware/pull/6772/commits/5426a7d0d7fd11d4d5c6c77ede9993204e611e14 to fix the problem.
Unfortunately, I didn't have a python 3.8 directory so I applied the patch to the python 3.9 directory. After reboot, the device does not boot completely, no access. Please help


What's the best way to get my NAS back up and running using Windows? I am asking for professional advice, because I care about data recovery, e.g. jails, built-in and created accounts, permission settings, etc.

 

[elvisimprsntr]

You have a current config backup and backup of your data, right?

 

[Jedrek]

I only have a backup of the settings that the system created automatically before upgrading from 12.0-U3 to 12.0-U4.

I don't know if I'm thinking right, but I need to somehow get into this changed events.py file in python 3.9 and restore its settings.
But how to do it, for example, from Windows or maybe some edition of linux live?

I already know where I accidentally made a mistake in patching the .py script.
Is there any way to get "from outside" to this file then?

 

[SweetAndLow]

Reinstall the OS and upload your config file. Should be fixed in 5min.

 

[Jedrek]

Can I install version 12.0-U4 with the configuration files for version 12.0-U3.1 that I received before updating to version 12.0-U4?
Will it work? My priority are working jails.
My next question:
whether exist Jails will be work or not ?


Since I am not sure that all JAILS will work after recovery as before, please give a material advice on how I can file "events.py" which I extracted from the original image truenas 12.0-U4 move to the correct place on the startup disk truenas, or how to reach the disk which is in UFS format to have access to write and read this data.

Please help me

 

[elvisimprsntr]

I just migrated my boot pool from a external USB3 M.2 SSD to a eUSB DOM and was successfully able to restore the config backup.

TrueNAS automatically remounted all the dataset pools, including jails and plugins.

Code:

1. Save config via GUI (export secret seed)
2. Manually backup /root/.ssh/ folder
3. Install TrueNAS CORE on DOM (UEFI mode)
4. Restore config via GUI
5. Restore /root/.ssh/ folder

The only caveat is I restored a config backup that was generated using the same TrueNAS version.

 

[Jedrek]

Now because i don't have a access to my NAS, and bootdisk don't boot successfull and I can't backup a /root/.ssh/ folder
You can migrate if Your system is healtly. Now my system not booting.
SSH not working too.

 

[elvisimprsntr]

Now because i don't have a access to my NAS, and bootdisk don't boot successfull and I can't backup a /root/.ssh/ folder
You can migrate if Your system is healtly. Now my system not booting.
SSH not working too.

Not having the /root/.ssh/ folder is not critical if you don't have any RSYNC via SSH tasks between two systems.
Even then, you can simply go through the steps of generating new authorized keys.

How about re-installing 12.0-U3.1 and restore the config backup you already have?

 

[Jedrek]

Thanks for the hint. Somehow, I am not entirely convinced that it will succeed. Meanwhile, I will look for other solutions and in the end, I will put version 12.0-U3.1 on version 12.0-U4 and restore the settings from the file with the secret code.

I was hoping that at this stage it would be enough to restore some damaged script file (e.g. with a virtual machine and FreeBSD or with FreeBSD Live)

 

[SweetAndLow]

Thanks for the hint. Somehow, I am not entirely convinced that it will succeed. Meanwhile, I will look for other solutions and in the end, I will put version 12.0-U3.1 on version 12.0-U4 and restore the settings from the file with the secret code.

I was hoping that at this stage it would be enough to restore some damaged script file (e.g. with a virtual machine and FreeBSD or with FreeBSD Live)

You could have been done by now. Get a new boot device and save the old one of you are scared.

You could also hook up a monitor and select the older boot environment if you just want to roll back. Just reinstall already it's almost exactly what an upgrade does anyways.



You didn't really share your system setup so I assume no encryption or strange config.

 

[Jedrek]

Thank you very much for all your help. I was able to put the system back up with the installer options:
1. UPDATE (Not NEW INSTALATION)
2. Format the BOOT device

I didn't have to do anything else, restore nothing, the system has updated all settings !!!
Thank you again. I'm happy.

Obviously the dashboard is buggy, doesn't show much information, but it's hard. Maybe the next update will fix this problem