update from 7.4.17 to 7.5.0 failed

Seeing the same issue with the update I have done on my Pi4

Connected a keyboard and mouse and opened first -aid.

Going to read up what I should be doing from there.

Following up, I had to login to the device via keyboard and mouse

Run omv-firstaid

And run through the network config again for eth0. This was setup as DHCP before and it was set like this again.

Once this one completed my network issue was resolved.

I'm having the same issue here - did the most recent update and now the Pi won't recognize ethernet (and I didn't set it up with WIFI).

I'd like to follow your steps, as I'm sure that would fix it, and also provide more details as to what went wrong but I did a headless install on the Pi and now that I don't have internet on it, I don't think I can get anything from it. Please correct me if I'm wrong, but I'm assuming that I won't be able to access the command line via a monitor and keyboard, right?

If not, my guess is I'll need to start all over again.

same happened on my RPi4. It's dead now , not even responding to ping. Unfortunately I do not have keyboard and monitor:)

Same issue on my RPi4, no remote communication at all (on router looks like switched off). I don't have monitor connected, so no error message.

Quote from Mrbroo

Following up, I had to login to the device via keyboard and mouse

Run omv-firstaid

And run through the network config again for eth0. This was setup as DHCP before and it was set like this again.

Once this one completed my network issue was resolved.

Display More

does anyone know if it is possible to config it via editing specific file on SD card?

ok, solution from Mrbroo works

I have a quite differnt issue with the update since I have a x86 machine.

after updating to 7.5.0 there are pending configuration changes indicated, which fail with following error message:

result: all Docker Containers are not working anymore. I will now consider twice to update omv, when its running fine.

Pending configuration changes You must apply these changes in order for them to take effect. The following modules will be updated: 

systemd-networkd

see full error message in attached file

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color systemd-networkd 2>&1' with exit code '1': debian:Data failed to compile:----------Rendering SLS 'base:omv.deploy.systemd-networkd.default' failed: Jinja variable 'salt.utils.templates.AliasedLoader object' has no attribute 'file.readdir'; line 23

UPDATE: apt update is also failing via ssh and web gui after the update:

Holen:14 https://openmediavault-plugin-developers.github.io/packages/debian sandworm InRelease [3.939 B]
Es wurden 3.939 B in 2 s geholt (2.458 B/s).                                   
Traceback (most recent call last):
  File "/usr/sbin/omv-mkaptidx", line 236, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/lib/python3/dist-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/sbin/omv-mkaptidx", line 128, in main
    cache = apt.cache.Cache()
            ^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__
    self.open(progress)
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 232, in open
    self._cache = apt_pkg.Cache(progress)
                  ^^^^^^^^^^^^^^^^^^^^^^^
apt_pkg.Error: E:Problem parsing dependency 20 of libghc-filestore-dev:amd64=0.6.5-2+b3, E:Error occurred while processing libghc-filestore-dev (NewVersion2), E:Problem with MergeList /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_main_binary-amd64_Packages, E:The package lists or status file could not be parsed or opened.
Paketlisten werden gelesen… Fehler!
E: Problem parsing dependency 20 of libghc-filestore-dev:amd64=0.6.5-2+b3
E: Fehler aufgetreten beim Verarbeiten von libghc-filestore-dev (NewVersion2)
E: Problem with MergeList /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_main_binary-amd64_Packages
E: Die Paketliste oder die Statusdatei konnte nicht eingelesen oder geöffnet werden.

Quote from ryecoaaron

No one can help you without more info. You will have to plug in a keyboard and monitor. You might just need to run omv-firstaid

Hey sir! I applyed a fix you had in docker not working since omv-upgrade about grub. Will this conflict with omv first aid or is there a way to undo that change easy so i can just test first aid out?

Quote from piter1984

does anyone know if it is possible to config it via editing specific file on SD card?

Same question for me. I haven't keyboard and display, but I can read ssd by winspc.

Please help us

Quote from Mrbroo

Following up, I had to login to the device via keyboard and mouse

Run omv-firstaid

And run through the network config again for eth0. This was setup as DHCP before and it was set like this again.

Once this one completed my network issue was resolved.

Display More

Confirmed, this worked out very well.

On the one hand, it's just a pity that I had to open my server to be able to connect an external screen. On the other hand, great opportunity to clean it from some accumulated dust

Thank you, this made my Saturday evening.

I only have a headless Pi using SSH only.

IMO a OS update changing network configuration should be noticed by OMV setup. This issue today looks to me like a clear disadvantage.

I'll prepare a new setup as I have no other option.

A new install resolved the problem.

No, I don't have an extra Screen and I didn't want that way to go. The OS is a lite PiOs so no gui, no extras.

I'm fine now and system is up an running properly.

My system is based on RPi4 and is configured with eth0 as NW-adapter.

So I expected the often mentioned NW-issues and waited w the update

But today, w some changes, I could manage to update to 7.5.0-1 without messing up NW config.

What I did:

- talked to a Linux/OMV expert asking for help

- she understood the problem by reading the issue on Github and gave me the following cookbook:

1- create a copy of current system disk and boot from it (to work on a copy, just for safety reasons)

2- add parameter net.ifnames=0 to /boot/cmdline.txt (forcing kernel to use old if-names like eth0)

3- restart system to activate parameter

4- Start update

Result: Working w/o any issues!

Only question left from myside: how to switch system safely from eth0 to end0 (or to new naming schema)?