Posts by KVL

Good morning,

I have just had an uexpected reboot this night - at least unexpected for me..

System is 7.7.1-2 (Sandworm) / Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz / Linux 6.12.12+bpo-amd64

Several KVMs were running. No USB devices attached to them. Only one keyboard is attached to the host as the only USB device.

I cant really conclude what happened. Something points to USB on the KVM (VIA Labs) even it is not in use. But the last entry is 14 minutes before it rebooted, so maybe not related.

I am not aware of any power outtage here.

Can you any of you help me to point me in the direction to what happend?

journalctl -b -1 -e

Mar 14 02:11:58 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 02:12:03 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 02:12:03 omv kernel: usb 4-5: device not accepting address 98, error -62

Mar 14 02:12:37 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 02:12:37 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 02:12:37 omv kernel: usb 4-5: device not accepting address 98, error -62

Mar 14 02:12:37 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 02:12:37 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 02:12:37 omv kernel: usb 4-5: device not accepting address 98, error -62

Mar 14 02:12:37 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 02:12:37 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 02:12:37 omv kernel: usb 4-5: device not accepting address 98, error -62

Mar 14 02:12:37 omv kernel: usb 4-5: USB disconnect, device number 98

Mar 14 02:12:42 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 02:12:47 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 02:12:47 omv kernel: usb 4-5: device not accepting address 99, error -62

Mar 14 02:12:47 omv kernel: xhci_hcd 0000:00:14.0: ERROR Transfer event for disabled endpoint slot 14 ep 0

Mar 14 02:12:47 omv kernel: xhci_hcd 0000:00:14.0: @000000010424f700 00000000 00000000 0c000000 0e018000

Mar 14 02:12:52 omv systemd-udevd[934]: 4-5: Worker [98013] processing SEQNUM=11727 is taking a long time

Mar 14 02:12:53 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 02:12:58 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 02:12:58 omv kernel: usb 4-5: device not accepting address 100, error -62

Mar 14 02:12:58 omv kernel: xhci_hcd 0000:00:14.0: ERROR Transfer event for disabled endpoint slot 15 ep 0

Mar 14 02:12:58 omv kernel: xhci_hcd 0000:00:14.0: @000000010424f7b0 00000000 00000000 0c000000 0f018000

Mar 14 02:12:59 omv kernel: usb usb4-port5: attempt power cycle

Mar 14 02:12:59 omv kernel: usb 4-5: new SuperSpeed USB device number 101 using xhci_hcd

Mar 14 02:12:59 omv kernel: usb 4-5: New USB device found, idVendor=17aa, idProduct=1034, bcdDevice=53.75

Mar 14 02:12:59 omv kernel: usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0

Mar 14 02:12:59 omv kernel: usb 4-5: Product: USB Hub

Mar 14 02:12:59 omv kernel: usb 4-5: Manufacturer: VIA Labs, Inc.

Mar 14 02:12:59 omv kernel: hub 4-5:1.0: USB hub found

Mar 14 02:12:59 omv kernel: hub 4-5:1.0: 4 ports detected

Mar 14 02:12:59 omv libvirtd[38927]: internal error: Missing udev property 'ID_VENDOR_ID' on '4-5'

Mar 14 02:39:00 omv systemd[1]: Starting phpsessionclean.service - Clean php session files...

Mar 14 02:39:00 omv systemd[1]: phpsessionclean.service: Deactivated successfully.

Mar 14 02:39:00 omv systemd[1]: Finished phpsessionclean.service - Clean php session files.

Mar 14 02:39:01 omv CRON[98535]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Mar 14 02:39:01 omv CRON[98536]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)

Mar 14 02:39:01 omv CRON[98535]: pam_unix(cron:session): session closed for user root

Mar 14 03:09:00 omv systemd[1]: Starting phpsessionclean.service - Clean php session files...

Mar 14 03:09:00 omv systemd[1]: phpsessionclean.service: Deactivated successfully.

Mar 14 03:09:00 omv systemd[1]: Finished phpsessionclean.service - Clean php session files.

Mar 14 03:09:01 omv CRON[99107]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Mar 14 03:09:01 omv CRON[99108]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)

Mar 14 03:09:01 omv CRON[99107]: pam_unix(cron:session): session closed for user root

Mar 14 03:10:01 omv CRON[99161]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Mar 14 03:10:01 omv CRON[99162]: (root) CMD (test -e /run/systemd/system SERVICE_MODE=1 /sbin/e2scrub_all -A -r)

Mar 14 03:10:01 omv CRON[99161]: pam_unix(cron:session): session closed for user root

Mar 14 03:39:00 omv systemd[1]: Starting phpsessionclean.service - Clean php session files...

Mar 14 03:39:00 omv systemd[1]: phpsessionclean.service: Deactivated successfully.

Mar 14 03:39:00 omv systemd[1]: Finished phpsessionclean.service - Clean php session files.

Mar 14 03:39:01 omv CRON[99703]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Mar 14 03:39:01 omv CRON[99704]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)

Mar 14 03:39:01 omv CRON[99703]: pam_unix(cron:session): session closed for user root

Mar 14 04:09:00 omv systemd[1]: Starting phpsessionclean.service - Clean php session files...

Mar 14 04:09:00 omv systemd[1]: phpsessionclean.service: Deactivated successfully.

Mar 14 04:09:00 omv systemd[1]: Finished phpsessionclean.service - Clean php session files.

Mar 14 04:09:01 omv CRON[100231]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Mar 14 04:09:01 omv CRON[100232]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)

Mar 14 04:09:01 omv CRON[100231]: pam_unix(cron:session): session closed for user root

Mar 14 04:39:00 omv systemd[1]: Starting phpsessionclean.service - Clean php session files...

Mar 14 04:39:01 omv systemd[1]: phpsessionclean.service: Deactivated successfully.

Mar 14 04:39:01 omv systemd[1]: Finished phpsessionclean.service - Clean php session files.

Mar 14 04:39:01 omv CRON[100851]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Mar 14 04:39:01 omv CRON[100852]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)

Mar 14 04:39:01 omv CRON[100851]: pam_unix(cron:session): session closed for user root

Mar 14 05:09:00 omv systemd[1]: Starting phpsessionclean.service - Clean php session files...

Mar 14 05:09:01 omv systemd[1]: phpsessionclean.service: Deactivated successfully.

Mar 14 05:09:01 omv systemd[1]: Finished phpsessionclean.service - Clean php session files.

Mar 14 05:09:01 omv CRON[101420]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)

Mar 14 05:09:01 omv CRON[101421]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)

Mar 14 05:09:01 omv CRON[101420]: pam_unix(cron:session): session closed for user root

Mar 14 05:16:17 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

Mar 14 05:16:22 omv kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command

-- Boot 164c7a946cfa4e8b969a4d545845debe --

Mar 14 05:30:35 omv kernel: Linux version 6.12.12+bpo-amd64 (debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (>

Mar 14 05:30:35 omv kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.12.12+bpo-amd64 root=UUID=2dc05cd7-e678-4656-bdfd-e127a974e2b5 ro quiet

journalctl --system --grep="shutdown" --no-pager

-- Boot 164c7a946cfa4e8b969a4d545845debe --

Mar 14 05:30:35 omv systemd[1]: Reached target virt-guest-shutdown.target - Libvirt guests shutdown.

Mar 14 05:32:05 omv systemd[1]: mdadm-shutdown.service - Prepare mdadm shutdown initramfs was skipped because of an unmet condition check (ConditionFileIsExecutable=/usr/bin/dracut).

Mar 14 05:32:06 omv systemd[1]: Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP...

Mar 14 05:32:06 omv systemd[1]: Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.

Mar 14 05:32:06 omv systemd[1]: Started unattended-upgrades.service - Unattended Upgrades Shutdown.

Mar 14 05:32:09 omv containerd[1374]: time="2025-03-14T05:32:09.133049117+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1

Mar 14 05:32:09 omv containerd[1374]: time="2025-03-14T05:32:09.207109090+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1

Mar 14 05:32:09 omv containerd[1374]: time="2025-03-14T05:32:09.216679489+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1

Mar 14 05:32:09 omv containerd[1374]: time="2025-03-14T05:32:09.220316617+01:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1

The only message I got was "Error 500 - Unable to add network adapter to VM". No further information.

I was able to create a new blank VM and assign the Br0 to it without problems.

I removed my existing VMs, and created them again with same specifications, disks etc and could also here assign the Br0 without issues.

So it seems there was some issues on the existing VMs, even I already had all network information removed.

It works now as wanted - they are able to connect to the host - THANKS! But unfortunately I didnt leave much information for further trouble shooting on the issue with the existing VMs.

I am looking forward to see how the Linux and Windows VMs operate and perform - I am only used to work with VMware and VirtualBox.

Thanks again for your help!

Many thanks!

Sounds easy, though, I tried it.

The OMV host has the new interface as the guide describe and is on the net.

I have removed the networks from the KVMs, and tried to add a new network, bridge assigned to br0, as described the the technote.

But it fails, with Error 500 - Unable to add network adapter to VM..

Any clue - or suggestions where to look for further information?

Hello,

I have just configued KVM via the plugin on OMV 7.7

The guests - Windows and Linux - are up running and connected in bridge mode via macvtap. The guest machines can reach all devices on the network, except the host it self.

I have tried to see if it can be bypassed in the firewall, but seems to be the design of macvtap. Alternatives are additional NICs in the guests, or using macvlan. I would like to avoid the extra NIC, leaving it to macvlan. But I dont find anything about in, only in regards to Docker.

Does the OMV / KVM support the macvlan? Do I somehow need to install or load it?

If not, what alternatives do I have to be able to reach the host?

Many thanks K

Hi,

I have KVM running on OMV 6.0.28-3. Two guests are running with static IPs on a bridged KVM network.

One #1 guest uses the second #2 guest as gateway, which works well. The guest #1 can ping all devices on the local network, but cant ping/access the actual OMV / KVM host.

The OMV / KVM host can ping and access both guests... The guest #2 is an Ubuntu which routes traffic via OpenVPN.

It worked well when using VirtualBox, but not with KVM.

What I am missing here - why cant my guest #2 not access the host?

Regards K

I have installed the KVM plug in, and converted my Linux and Windows (with the proper drives). And a nrw bridge network. Running smooth so far, very simple process. Hopefully it will stay, and I can avoid the VirtualBox hassle. Thanks for the simple advice: KVM

Few days I reinstalled with with a plan new installation of OMV 6.0.27-1.

Two external 7 tb disks are attached with USB.

Yesterday night the OMV halted with similar errors as above.

[ 3.753464] scsi 2:0:0:1: Wrong diagnostic page; asked for 1 got 8[ 3.753476] scsi 2:0:0:1: Failed to get diagnostic page 0x1
[ 3.753481] scsi 2:0:0:1: Failed to bind enclosure -19

Hi,

I used to have Virtualbox and Phpvirtualbox running on my OMV5 by using this guide:

Guide: Virtualbox 6.x and PHPVirtualbox on OMV5 and Debian 10.x - Guides - openmediavault

I have had to reinstall the box with OMV6.

Does the linked guide still work on OMV6, or what expierence have you had with this configuration. ?

Or should I take the step and move to the KVM plugin (both running Linux and Windows machines..)?

Regards, K

ntlm auth = yes

You will have to download the .deb manually from Oracle, and install it with dpkg.

I have also downgraded to 6.1.24, and it works again.

I got the same issue, after upgrading the OMV and VBox.

I wonder if this relates to the newly released bug/fix:

openmediavault 5.5.17

WARNING … This update might cause problems on systems that are using USB hardware based on JMicron controllers.

• Update locales.
• Issue #842: Fix bug in UDEV rules to workaround a JMicron bug. If your USB controller reports the vendor ‘JMICRON’, then you might be affected by this issue. After installing this package your mounted filesystem configuration might be broken. To fix that, you need to unmount and remount the filesystems that are connected via this USB controller. If the filesystem contains any shared folders, you can’t unmount it, because of that you need to delete all shared folders that are located on the filesystem to be unmounted. Make sure to choose the right menu to only delete the shared folder configuration WITHOUT the content. You can only delete shared folders they are not used by any service, so make sure this applies to these shared folders. After you’ve unmounted these filesystems in the UI, apply the changes, reboot the system and then mount the filesystems again. After that you can reconfigure your shared folders and services from scratch. Sorry for this inconvenience.
• Issue #846: Fix locking issue in SMB recycle bin cleanup and iptables scripts.

I have also gotten the issue since the last two weeks. Lenovo Desktop and with SSD disks.

Good morning,

I have till now - on OMV5 - avoided to use Docker container instead of the old plugins, but might have realized the strength of the Docker . I have now used it for a few addons and found it rather nice, flexible and useful. I will try to work more with it.

Sorry if my question has already been answered, thou couldnt find any information on it. If, then maybe you can point me to the tread.

As I understand, the Docker shares the same kernel on the host (and as OMV), where by it will be using the same users and groups (UID and GID).

The Docker on OMV is loaded as root and also the Portainer which I have deployed. It seems required due to being able to create the volumes etc on the host.

Other containers deployed are also running under root. Isn't this a security issue?

E.g if I deploy a simple NGINX container will run as root, which I would not expect to the be the case / best practice.

I have tried to - without knowing if it makes sense to add e.g. '--user=nginxuser' in the Portainer command in the GUI. As well creating ENV on the container, like UID and GID. Also setting the User in the Portainer Container Command in the GUI. Thou nothing makes a difference (also based on guessing..) The user nginxuser is created directly on the host and is available in the /etc/passwd and /etc/group.

Is it not possible to run a container via Portainer under a non-root account?

Or is it actually just not an issue running it all as root?

Again, sorry if it has also been answered - I was not able to find anything about it .

Best regards K

Hello,

I would like to create a mail server on my OMV 4.1.32 and have pointed my MX record to the box..
What I would like to achieve, is a simple server, which provides me with an single interface - console or web - where I can pull the email from what mail address I have allowed for the domain / MX.

Nothing fancy - just a single box for my ad-hoc addresses..

Can anyone guide me to such a simple setup - should I installed it on the core OMV, or should I extended it have it running via Virtual Box appliance, or a Docker image?

Best regards, K

Thanks Adoby,

I am sure you are right - I will not be better than the defaults, so will leave it to this.
Thanks for your input and to have me realize..

Hello,

I have a ThinkStation, which runs OMV 4. The machine has 16 cores..
Does OMV automatically handle these cpus/cores optimal, or can tweak it somehow. Eg, tell virtual box to use 8, web service 2, Plex 4 etc, or is that transparent done in the most optimal way by the OS

Regards K

I got it working as I wanted. Here you are, if anyone else wanna do similar.

iptables -F
iptables -X
iptables -Z

iptables -N STATE0
iptables -A STATE0 -j LOG --log-prefix '*** ' -m limit --limit 5/m
iptables -A STATE0 -p udp --dport 1010 -m recent --name KNOCK1 --set -j DROP
iptables -A STATE0 -j DROP

iptables -N STATE1
iptables -A STATE1 -m recent --name KNOCK1 --remove
iptables -A STATE1 -j LOG --log-prefix '*** KNOCK 1 ' -m limit --limit 5/m
iptables -A STATE1 -p udp --dport 2020 -m recent --name KNOCK2 --set -j DROP
iptables -A STATE1 -j STATE0

iptables -N STATE2
iptables -A STATE2 -j LOG --log-prefix '*** KNOCK 2 ' -m limit --limit 5/m
iptables -A STATE2 -m recent --name KNOCK2 --remove
iptables -A STATE2 -p udp --dport 3030 -m recent --name KNOCK3 --set -j DROP
iptables -A STATE2 -j STATE0

iptables -N STATE3
iptables -A STATE3 -m recent --name KNOCK3 --remove
iptables -A STATE3 -j LOG --log-prefix '*** KNOCK OK ' -m limit --limit 5/m
iptables -A STATE3 -j LOG --log-prefix '*** ' -m limit --limit 5/m
iptables -A STATE3 -p tcp --dport 22 -j ACCEPT
iptables -A STATE3 -j STATE0

iptables -N TRUSTED
iptables -A TRUSTED -j LOG --log-prefix '*** TRUSTED ' -m limit --limit 5/m
iptables -A TRUSTED -j ACCEPT

iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A INPUT -s 127.0.0.0/8 -j ACCEPT
iptables -A INPUT -p icmp -j ACCEPT

iptables -A INPUT -p tcp --dport <myPort> -j ACCEPT
iptables -A INPUT -p tcp --dport <myPort> -j ACCEPT

iptables -A INPUT -m recent --name KNOCK3 --rcheck -j STATE3 --seconds 30
iptables -A INPUT -m recent --name KNOCK2 --rcheck -j STATE2 --seconds 30
iptables -A INPUT -m recent --name KNOCK1 --rcheck -j STATE1 --seconds 30
iptables -A INPUT -j STATE0

Thanks, I ended up mounting the old drives as external and copied the data over.