Posts by Sn00zE

I just had this same issue after updates around 6 June 2025. I only use one network port and the other is taped off so i dont use the wrong one. Network identifier changed from "enp3s0" to "enp2s0". Only picked it up because i wanted to access a app in docker using macvlan and couldnt reach the ip because the macvlan was using parent=enp3s0

Using OMV

Version

7.7.10-1 (Sandworm)

The only hardware change was the removal of a Graphics Card i did not use and just pumping heat in the the case.

Oh and here is the catch, Console still says:

Active network card is down mmnnn..

Yet command line says:

Had to update my sources.list from:

#



deb http://debian.saix.net/ bookworm main
deb-src http://debian.saix.net/ bookworm main


# bookworm-updates, previously known as 'volatile'
deb http://debian.saix.net/ bookworm-updates main contrib non-free
deb-src http://debian.saix.net/ bookworm-updates main contrib non-free

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

To the international Debian sources

Quote from gekomod

Code

deb http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
deb-src http://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware


# bookworm-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
deb-src http://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

Display More

Awesome, thanks, got the right sources then. Looks like my localized sources went down about 150 days ago. strange.

Can someone provide output of "cat /etc/apt/sources.list" please?

Hi

Been getting the following reports via mail for my server for the past few days.

Looked at a previous post but doesn't seem to be a related issue. Any help would be appreciated.

Unattended upgrade result: No packages found that can be upgraded
 unattended and no pending auto-removals

Packages with upgradable origin but kept back:
 Debian stable-security:
  openssh-sftp-server openssh-server openssh-client

Unattended-upgrades log:
Starting unattended upgrades script
Allowed origins are: origin=Debian,codename=bookworm,label=Debian-Security, origin=Debian,codename=bookworm-security,label=Debian-Security, origin=Debian,codename=bookworm,label=Debian-Security, origin=Debian,codename=bookworm-security,label=Debian-Security
Initial blacklist:
Initial whitelist (not strict):
No packages found that can be upgraded unattended and no pending auto-removals
Package openssh-client is kept back because a related package is kept back or due to local apt_preferences(5).
Package openssh-server is kept back because a related package is kept back or due to local apt_preferences(5).
Package openssh-sftp-server is kept back because a related package is kept back or due to local apt_preferences(5).

# apt-cache policy openssh-client
openssh-client:
  Installed: 1:9.2p1-2+deb12u3
  Candidate: 1:9.2p1-2+deb12u5
  Version table:
     1:9.2p1-2+deb12u5 500
        500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
 *** 1:9.2p1-2+deb12u3 500
        500 http://debian.saix.net bookworm/main amd64 Packages
        100 /var/lib/dpkg/status

# cat /etc/apt/apt.conf
cat: /etc/apt/apt.conf: No such file or directory

Quote from mrkrabs

This is now working with the latest Business STS Edition 2.20.1

You can follow the instructions to update here or follow the below instructions. Remember to back up first!!!

Stop and remove the current Portainer version

Code

docker stop portainer

Code

docker rm portainer

Pull the image

Code

docker pull portainer/portainer-ee:2.20.1

And deploy (default ports used here)

Code

docker run -d -p 8000:8000 -p 9443:9443 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ee:2.20.1

I can confirm that this is working again on mine.

Display More

Also changed to the STS release, portainer console working now.

My docker process:

docker stop portainer

docker rm portainer

docker run -d -p 8000:8000 -p 9443:9443 --name=portainer --restart=unless-stopped -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:sts

New portal on https://remotehost:9443/

Quote from jesperdahl

Yes, i had the same problem after upgradering Docker with OMV update.

just ran this command, then it works again!

sudo apt install docker-ce=5:25.0.5-1~debian.12~bookworm

So the problem is with the current updated version "docker-ce 5:26.0.0-1~debian.12~bookworm"?

Upgraded from OMV6 > OMV7. Not sure if its related but in portainer i am unable to access any container consoles. Getting error "Unable to retrieve image details". I see same issue reported here https://github.com/portainer/portainer/issues/11436

Anyone else getting this error?

Quote from furny

Good news! Finally, I was able to find out the cause of my issue, reading carefully the release notes. As explained in the Docker Engine V23 Release Notes and namely in known issues , there is a sort of bug: "the existence of any ipvlan networks will prevent the daemon from starting". Since I was using an ipvlan network for one of my containers, that was causing the issue. I removed the ipvlan network, upgraded without any problem, and recreated the container and its network (now a mtacvlan, instead), and everything is working perfectly fine.

I had also disabled apparmor, just in case.

So, beware for this issue, because, from the error reports, it wasn't clear for me the cause.

Good luck to all of you!

Display More

Finally decided to update after this fiasco, oh and yes, I had a ipvlan configured, have since switched to macvlan so deleted the ipvlan and update worked without a problem.

Quote from seanmccabe

I am getting the same issue, the intial fix doesnt seem to have resolved the issue

From RE: docker not working since omv-upgrade in OMV run the docker uninstall, SSH to your machine

sudo apt install docker-ce-cli=5:20.10.23~3-0~debian-bullseye
sudo apt install docker-ce=5:20.10.23~3-0~debian-bullseye
sudo service docker restart

This worked for me. I see the upgrade is available again. not sure if it will break it again without the fix from docker not working since omv-upgrade

Its too hot here and too late to do this now, just needed things running again.

Just picked up something weird after fresh install of OMV.

The network device name under the GUI is different from the ssh session when doing "ip a".

During setup it was enp3s0 and now says enp4s0 via commandline

GUI:

enp3s0

SSH Command line:

enp4s0

How is this possible? Which one is correct?

There are two nic's on this motherboard and I'm only using the one.

Quote from Frepke

And still not able to remove your docker network (maybe in Portainer)

Docker service is stopped, portainer is living in the docker service on this server. So that will not work.

After the network was created I lost all connectivity to the server.

will need to reinstall docker probably then

Quote from Frepke

Did you unplug your network cable before rebooting?

Yes, no network cables connect now.

Was able to boot the server with docker service stopped.

Quote from Frepke

Remove your docker network wit:

Code

docker network rm MyNetwork

That was the first thing I wanted to do, basic documentation yes. But the docker service is none responsive. cant run any docker commands

Hi There,

I tried to create a docker network with the same ip range of my home network and now my OMV server has no network connectivity. Guess that was not a good idea.

Rebooted the server and logged in via command console, docker service is not responding, unable to run docker commands.

Tried to change the OMV Server ip to 192.168.1.100 via omv-firstaid which was successful.

Docker service still not responding.

OMV Server:

ip: 192.168.0.100

subnet: 255.255.255.0

gateway: 192.168.0.1

Docker network:

name: MyNetwork

range: 192.168.0.0/24

gateway: 192.168.0.1

Anyone have any ideas?

Is there a way to remove this stupid network i created from the docker config file before docker service would start?

EDIT:

Currently trying to "systemctl disable docker.service" but its really slow and still running

Thank you for the input. Will see what I can do.

Quote from ryecoaaron

Your system is a mess. I would consider a fresh install. As long as your docker containers and VM disks are on data disks, it should be easy to recreate everything.

Damn, also think so yes, cant do any installs or even uninstalls of packages.

Just to check, I have my docker containers on a data disk. Can the previous docker data be imported, ie. all the previous settings and docker profiles?

Guess I have to redo all my samba folder permissions for all shares? Had ACL settings on media directories.

There were some updates available in the UI so I tried to run them. Now i dont have a UI - 502 Bad Gateway Ngnix

See attached list for updates output

root@vault:/# sudo nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

root@vault:/# omv-engined -d -f
PHP Fatal error:  Uncaught Error: Call to undefined function mb_strtolower() in /usr/share/php/openmediavault/autoloader.inc:28
Stack trace:
#0 [internal function]: {closure}('OMV\\Environment')
#1 /usr/sbin/omv-engined(357): spl_autoload_call('OMV\\Environment')
#2 {main}
  thrown in /usr/share/php/openmediavault/autoloader.inc on line 28
omv-engined[25852]: PHP Fatal error: Uncaught Error: Call to undefined function mb_strtolower() in /usr/share/php/openmediavault/autoloader.inc:28
Stack trace:
#0 [internal function]: {closure}('OMV\\Environment')
#1 /usr/sbin/omv-engined(357): spl_autoload_call('OMV\\Environment')
#2 {main}
  thrown in /usr/share/php/openmediavault/autoloader.inc on line 28
PHP Fatal error: Uncaught Error: Call to undefined function mb_strtolower() in /usr/share/php/openmediavault/autoloader.inc:28
Stack trace:
#0 [internal function]: {closure}('OMV\\Environment')
#1 /usr/sbin/omv-engined(357): spl_autoload_call('OMV\\Environment')
#2 {main}
  thrown in /usr/share/php/openmediavault/autoloader.inc on line 28

Hi Guys,

I need some guidance on upgrading my current server distribution to the latest.

Am I safe to follow the upgrade guide https://openmediavault.readthe…o/en/5.x/various/apt.html or should I look at Upgrade Scripts for non-interactive major release upgrades (2->3, 3->4, 4->5) and do the upgrade one release at a time?

My biggest question, which is a nightmare to confirm, is the addons. Below is some information about the addons i still have active and installed. most other addons was removed I don't need anymore or was replaced by docker containers.

Also, there allot of errors during "apt-get update", anything to be concerned about?

Currently on V3.0.100 (Erasmus)

dpkg -l | grep openm

ii  openmediavault                                                   3.0.100                              all          Open network attached storage solution
ii  openmediavault-docker-gui                                        3.1.9                                amd64        OpenMediaVault plugin for Docker
ii  openmediavault-fail2ban                                          1.3.1                                all          OpenMediaVault Fail2ban plugin
ii  openmediavault-omvextrasorg                                      3.4.32                               all          OMV-Extras.org Package Repositories for OpenMediaVault
pc  openmediavault-pyload                                            3.0                                  all          OpenMediaVault pyLoad plugin
ii  openmediavault-virtualbox                                        3.0.8                                all          VirtualBox plugin for OpenMediaVault.

apt list --installed | grep openmediavault-

openmediavault-docker-gui/now 3.1.9 amd64 [installed,upgradable to: 4.1.6]
openmediavault-fail2ban/now 1.3.1 all [installed,upgradable to: 4.0.2]
openmediavault-omvextrasorg/now 3.4.32 all [installed,upgradable to: 4.1.16]
openmediavault-virtualbox/now 3.0.8 all [installed,upgradable to: 4.1.2]

apt-get update

apt-get update.txt

Best post! Thank you. The new scaling in OMW 3.0 was driving me mad.