Restore config to new drive does not work !? (25.10.1)

TrueNAS General
1

I try to create a new truenas boot disk for my updated TrueNas system. Peace of cake I thought. But for some reason it does not work !!! :face_with_bags_under_eyes:

Since I did not want to take risks, I kept my old boot disk. Could have saved me.

So the process:

  • I updated the system to 25.10.1
  • did save the config from system/advanced/manage configuration include include password seed (=> rarfile including freenas-v1-db and pwenc_secret
  • downloaded 25.10.1 iso
  • took a new SSD attached the ssd in state of the ‘old boot ssd’
  • installed 25.10.1 on the new ssd option config via gui
  • boot the system from the new ssd
  • login using ‘truenas_admin’ and related pw
  • went to system/advanced/manage configuration upload file
    => warning screen go

image
image447×442 6.32 KB

And I do expect the system to load the uploaded files and start with the old config.

Not so !!

Really no idea why this does not work !!! :crying_cat:

2

I which way exactly does it not work?

Hard to guess from the information you provided.

3

Why didn’t you just download it through the GUI?

4

To answer the two questions:

  • after uploading the file nothing (seems) to happen. Booting after a few minutes does not change that
  • and .. I did download the config via the gui (after booting from the original boot ssd)
    and did restore via the gui after booting from the newly installed new boot ssd
5

I found the problem :blush:

To install the new version, I had connected an extra LAN-connection, however I did not remove the normal trunk ……

The default nas was listening / communicating at least tried so. Note the temporarily lan does not have vlan’s where the trunk has many!

So after removing the trunk, the original config was loaded.

Removing the temporally lan connection and enabling the trunk did the rest.

So my fault !!

Note however, that IMHO it is strange not to say stupid that a upgrade from the console, directly installing the desired config-file is not possible.

See my post a couple of days back!!

6

I’m not completely understanding the method you used based on this, but we do take care in the documentation to explicitly state supported upgrade methods (here, here, and here, for example) and this doesn’t sound like any of them.

It also tells you in docs and in the console itself that the only supported methods for system changes are the UI (preferred) and API. If you’re doing a lot of untested (on our end) manipulation in the console, you’ve been warned to expect potential breakages.

7

You do not understand the problem I was facing, and the way I solved it.

Note:

  • normally connected via a trunk. Via the trunk I can NOT reach or config a newly installed truenas instance!
  • I did want a clean boot disk, since I had a verdict that some problems were related to the actual boot disk among them issues related to the way data was al lined to sectors etc (see my recent posts)
  • I do have console access via KVM and in this case also local

So I did really prefer an install including the desired config from the console.

I did open a thread a few days ago, if that was an option. Regrettable there was no real option using the console.

So, I did use a more complex trick, by connecting an extra lan to the system and using a new / extra boot disk.

And I did every thing via the GUI, just as IX-system describes!

So please reread my posts

8

Understood I misread this sentence

as it is strange not to say… that an upgrade from the console… is not possible instead of what I think was your intended meaning (that you think such an upgrade should be possible), so I was just pointing out that we already do say which upgrade methods are possible and that is not on the list.

As for your networking setup complexity, you’ve already said you put yourself in that position and eventually found your way out, so I’m happy you’ve managed to get it working.

1 Like