Moving existing HDD-s + config.xml + fstab content (except new OS drive) into new hardware

mes mariusz · 3. Mai 2023

Hi.

I moved all existing HDD's and config.xml and fstab content (except new OS drive) into new hardware with fresh installed OMV.

As I mentioned config.xml has been replaced by this from the older hardware. It must work, because all drives have been moved from the old OMV into this new one. So all UUID, and so one remains the same.

The same for fstab except / and SWAP (because of new OS drive).

So I made omv-salt deploy run fstab (everything OK, no any errors.

After reboot everything seems to work excelent (including samba and all shares. But I noticed that e-mail notification doesn't work anymore. So I tried to disable the notifications and enable it again. When I try to save my settings I see:

Any help how to find the reason / how to make this working again ?

Thank you and best regards

Mariusz

gderf · 3. Mai 2023

An existing config.xml from one installation is not portable to another fresh installation.

chente · 3. Mai 2023

Zitat von mes mariusz

Any help how to find the reason / how to make this working again ?

Zitat von gderf

An existing config.xml from one installation is not portable to another fresh installation.

It can be done, but more needs to be done. This script does it for you.

Thema

[How to] Migrate/Restore OMV Settings to Another System with omv-regen

UTILITY TO MIGRATE OMV CONFIGURATION TO ANOTHER SYSTEM OR
DO A NEW OMV INSTALLATION AND KEEP THE SETTINGS

Si quieres leer todo esto en español puedes hacerlo en github

omv-regen

INSTALLATION:

Copy and paste the following line into a terminal and run it as root or with sudo.
sudo wget -O - https://raw.githubusercontent.com/xhente/omv-regen/master/omv-regen.sh | sudo bash

STEP 1. Create a backup of the original system with omv-regen.
STEP 2. Do a fresh installation of OMV on the disk you want and

…

chente

29. April 2023

chente · 3. Mai 2023

Zitat von mes mariusz

Any help how to find the reason / how to make this working again ?

Do not run omv-regen on the installation you have now. It must be a clean installation of OMV.

mes mariusz · 3. Mai 2023

Thankl you. I will check your solution.

Paralelly I checked which modules returns mistakes and I see that only smartmontools makes the issue:

#omv-salt deploy run smartmontools

Code

debian:
Data failed to compile:
----------
Rendering SLS 'base:omv.deploy.smartmontools.default' failed: Jinja error: The property 'tempinfo' does not exist in the model 'conf.service.smartmontools'.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 497, in render_jinja_tmpl
output = template.render(**decoded_context)
File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1090, in render
self.environment.handle_exception()
File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 832, in handle_exception
reraise(*rewrite_traceback_stack(source=source))
File "/usr/lib/python3/dist-packages/jinja2/_compat.py", line 28, in reraise
raise value.with_traceback(tb)
File "<template>", line 25, in top-level template code
File "/usr/lib/python3/dist-packages/jinja2/sandbox.py", line 465, in call
return __context.call(__obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
return self.loader.run(run_func, *args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
return _func_or_method(*args, **kwargs)
File "/var/cache/salt/minion/extmods/modules/omv_conf.py", line 41, in get
objs = db.get(id_, identifier)
File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 85, in get
query.execute()
File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 735, in execute
self._response = self._elements_to_object(elements)
File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 490, in _elements_to_object
result.set_dict(self._element_to_dict(elements[0]), False)
File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 208, in set_dict
self.set(key, value, validate)
File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 182, in set
self.assert_exists(name)
File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 152, in assert_exists
raise openmediavault.exceptions.AssertException(
openmediavault.exceptions.AssertException: The property 'tempinfo' does not exist in the model 'conf.service.smartmontools'.


; line 25


---
[...]
# Documentation/Howto:
# https://help.ubuntu.com/community/Smartmontools
# http://en.gentoo-wiki.com/wiki/Smartmontools
# http://www.linux-user.de/ausgabe/2004/10/056-smartmontools


{% set config = salt['omv_conf.get']('conf.service.smartmontools') %}    <======================


configure_default_smartmontools:
file.managed:
- name: "/etc/default/smartmontools"
- source:
[...]
---

Alles anzeigen

chente · 3. Mai 2023

Zitat von mes mariusz

Paralelly I checked which modules returns mistakes and I see that only smartmontools makes the issue:

You will have more errors than that. Although in the GUI it seems that things work, the reality is not. Look at everything the script does during the process, it's done in an orderly fashion applying changes at each step. https://github.com/xhente/omv-regen/blob/master/omv-regen.sh

mes mariusz · 3. Mai 2023

Unfortunately, with this script I cant do it (I forgot thjis was OMV v5).

"Unsupported version. Only OMV 6.x. are supported. Exiting..."

So anyway I will try to fight manually to move some parts of config.xml

We will see...

chente · 3. Mai 2023

Zitat von mes mariusz

Unfortunately, with this script I cant do it (I forgot thjis was OMV v5).
"Unsupported version. Only OMV 6.x. are supported. Exiting..."

In that case you can't use the script, effectively. I put that limitation because this is not tested on OMV5. I don't even remember if the database was similar and I guess many more parts will change.

If you still want to try it you can edit the script but I don't guarantee anything.

Zitat von mes mariusz

So anyway I will try to fight manually to move some parts of config.xml

The process is basically replace one part of config.xml apply salt changes, replace another part, apply salt changes...

On github you have a table with the salt modules that apply to each section of config.xml. It is long. https://github.com/xhente/omv-regen

gderf · 3. Mai 2023

Is there some reason you haven't stated that makes the original system disk unusable on the new hardware?

mes mariusz · 3. Mai 2023

1. I would like to use smaller one (32 GB instead of current one 250 GB SSD)

2. I would like to upgrade to ONM v6 (no reason to stay at v5)
3. Old OMV was used on other location (got other IP @ old LAN). I'm a bit surprised because I thought that it was configured as DHCP client and it's independent from old IP. But I see this OMV dont ask DHCP server about IP to get it, so I think even if that was OMV6, then omv-regen could be easily usable becauso (maybe) old (bad) network settings would be moved.

gderf · 3. Mai 2023

1. It's possible to attempt moving from a 250GB SSD to a smaller one, if certain steps are taken.

2. An OMV 5 is upgradeable to OMV6.

3. Not possible to say what exactly is happening with this other than to say it's almost certainly fixable.

chente · 3. Mai 2023

Zitat von mes mariusz

But I see this OMV dont ask DHCP server about IP to get it, so I think even if that was OMV6, then omv-regen could be easily usable becauso (maybe) old (bad) network settings would be moved.

The script checks plugin versions too, for a reason, if the version is different the corresponding part of config.xml may also be different, which would lead to configuration errors.

I don't think you can use it even by cracking the OMV version check.

You would end up in less time doing the configuration manually in the GUI.

macom · 3. Mai 2023

Zitat von mes mariusz

3. Old OMV was used on other location (got other IP @ old LAN). I'm a bit surprised because I thought that it was configured as DHCP client and it's independent from old IP.

With DHCP the router decides which IP is given to the client. So it is normal that the client gets a different IP at first connection and - depending on the router - at every boot or even in between.

mes mariusz · 3. Mai 2023

Zitat von gderf

2. An OMV 5 is upgradeable to OMV6.

Thank you for the hint,

Then If I will be able to repair the network on that OMV5 (via standard Debian config files /etc/network...) I could even upgrade.

At the moment I see I have no other choice because of this smartmontools error which I can't managed until still.

I believe that just one module-mistake separates me from easy success

All other mudules seems to be deployed orrectly.

Code

# omv-salt deploy run smartmontools
debian:
    Data failed to compile:
----------
    Rendering SLS 'base:omv.deploy.smartmontools.default' failed: Jinja error: The property 'tempinfo' does not exist in the model 'conf.service.smartmontools'.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 497, in render_jinja_tmpl
    output = template.render(**decoded_context)
  File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1090, in render
    self.environment.handle_exception()
  File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 832, in handle_exception
    reraise(*rewrite_traceback_stack(source=source))
  File "/usr/lib/python3/dist-packages/jinja2/_compat.py", line 28, in reraise
    raise value.with_traceback(tb)
  File "<template>", line 25, in top-level template code
  File "/usr/lib/python3/dist-packages/jinja2/sandbox.py", line 465, in call
    return __context.call(__obj, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 1235, in __call__
    return self.loader.run(run_func, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2268, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/salt/loader.py", line 2283, in _run_as
    return _func_or_method(*args, **kwargs)
  File "/var/cache/salt/minion/extmods/modules/omv_conf.py", line 41, in get
    objs = db.get(id_, identifier)
  File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 85, in get
    query.execute()
  File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 735, in execute
    self._response = self._elements_to_object(elements)
  File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 490, in _elements_to_object
    result.set_dict(self._element_to_dict(elements[0]), False)
  File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 208, in set_dict
    self.set(key, value, validate)
  File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 182, in set
    self.assert_exists(name)
  File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 152, in assert_exists
    raise openmediavault.exceptions.AssertException(
openmediavault.exceptions.AssertException: The property 'tempinfo' does not exist in the model 'conf.service.smartmontools'.

; line 25

---
[...]
# Documentation/Howto:
# https://help.ubuntu.com/community/Smartmontools
# http://en.gentoo-wiki.com/wiki/Smartmontools
# http://www.linux-user.de/ausgabe/2004/10/056-smartmontools

{% set config = salt['omv_conf.get']('conf.service.smartmontools') %}    <======================

configure_default_smartmontools:
  file.managed:
    - name: "/etc/default/smartmontools"
    - source:
[...]
---

Alles anzeigen

mes mariusz · 3. Mai 2023

Zitat von macom

With DHCP the router decides which IP is given to the client. So it is normal that the client gets a different IP at first connection and - depending on the router - at every boot or even in between.

Generally yes. I use properly configured Mikrotik at my home(s) / locations networks, so each single MAC is given the same IP each time.

Soma · 3. Mai 2023

Jinja2 errors might give a hint if searched on the forum.

Usual issues were PIP packages install that break OMV.

mes mariusz · 3. Mai 2023

Finally everytching started working after I applied this:

Code

omv-confdbadm migrate conf 6.0.0

Great

Zitat

# omv-salt deploy run smartmontools

debian:

----------

ID: configure_default_smartmontools

Function: file.managed

Name: /etc/default/smartmontools

Result: True

Comment: File /etc/default/smartmontools is in the correct state

Started: 18:51:26.564513

Duration: 34.646 ms

Changes:

----------

ID: divert_default_smartmontools

Function: omv_dpkg.divert_add

Name: /etc/default/smartmontools

Result: True

Comment: Leaving 'local diversion of /etc/default/smartmontools to /etc/default/smartmontools.distrib'

Started: 18:51:26.599671

Duration: 18.555 ms

Changes:

----------

ID: configure_smartd_conf

Function: file.managed

Name: /etc/smartd.conf

Result: True

Comment: File /etc/smartd.conf is in the correct state

Started: 18:51:26.618530

Duration: 44.786 ms

Changes:

----------

ID: divert_smartd_conf

Function: omv_dpkg.divert_add

Name: /etc/smartd.conf

Result: True

Comment: Leaving 'local diversion of /etc/smartd.conf to /etc/smartd.conf.distrib'

Started: 18:51:26.663451

Duration: 18.384 ms

Changes:

----------

ID: stop_smartmontools_service

Function: service.dead

Name: smartmontools

Result: True

Comment: The service smartmontools is already dead

Started: 18:51:26.707208

Duration: 67.225 ms

Changes:

Summary for debian

------------

Succeeded: 5

Failed: 0

------------

Total states run: 5

Total run time: 183.596 ms

Alles anzeigen

Moving existing HDD-s + config.xml + fstab content (except new OS drive) into new hardware

omv-regen

INSTALLATION:

chente 3. Mai 2023

Jetzt mitmachen!