Posts by Stanislas

After hours of research, I had found people who had stability problems with the r8169 version of the various realtek in the kernel so I had resolved to stay in DHCP (because the problem was solved).

Aus der Community linux4noobs auf Reddit

Entdecke diesen Beitrag und mehr aus der Community linux4noobs

www.reddit.com

[Résolu] Connexion ethernet qui se perd : kernel module en cause ? / Accès internet et réseaux / Forum Ubuntu-fr.org

But last week I saw a firmware-realtek update in OMV

firmware-realtek:amd64 (20241210-1~bpo12+1, 20250410-2~bpo12+1)

And having switched back to IP static to test, it seems that the problem has been solved with this update.

I hope there won't be any more problems

After hours of research, I had found people who had stability problems with the r8169 version of the various realtek in the kernel so I had resolved to stay in DHCP (because the problem was solved).

Aus der Community linux4noobs auf Reddit

Entdecke diesen Beitrag und mehr aus der Community linux4noobs

www.reddit.com

[Résolu] Connexion ethernet qui se perd : kernel module en cause ? / Accès internet et réseaux / Forum Ubuntu-fr.org

But last week I saw a firmware-realtek update in OMV

firmware-realtek:amd64 (20241210-1~bpo12+1, 20250410-2~bpo12+1)

And having switched back to IP static to test, it seems that the problem has been solved with this update.

I hope there won't be any more problems

Hello everyone,

My main network card is a pcie card 2.5 Gb : https://www.amazon.fr/dp/B0CF1…t_b_fed_asin_title_1&th=1

I have a 2.5 switch between my router and my server : https://www.amazon.fr/dp/B0C64…t_b_fed_asin_title_1&th=1

I have a problem with my server, sometimes, when exiting standby, it seems that the physical network link is not completely up and reconfiguring the network cards when exiting standby causes me to lose my default route.

There is no problem with DHCP.

root@nas:~# journalctl --since "2025-05-14 08:00:00" --until "2025-05-14 08:05:00" | grep enp7s0
mai 14 08:00:11 nas kernel: r8169 0000:07:00.0 enp7s0: Link is Down
mai 14 08:00:11 nas kernel: r8169 0000:07:00.0 enp7s0: Link is Down
mai 14 08:00:11 nas kernel: r8169 0000:07:00.0 enp7s0: Link is Up - 2.5Gbps/Full - flow control rx/tx
mai 14 08:00:10 nas systemd-networkd[531]: enp7s0: Lost carrier
mai 14 08:00:10 nas avahi-daemon[775]: Withdrawing address record for 192.168.10.10 on enp7s0.
mai 14 08:00:10 nas systemd-networkd[531]: enp7s0: Gained carrier
mai 14 08:00:10 nas avahi-daemon[775]: Leaving mDNS multicast group on interface enp7s0.IPv4 with address 192.168.10.10.
mai 14 08:00:10 nas avahi-daemon[775]: Interface enp7s0.IPv4 no longer relevant for mDNS.
mai 14 08:00:11 nas systemd-networkd[531]: enp7s0: Could not set route: Nexthop has invalid gateway. Le réseau n'est pas accessible
mai 14 08:00:11 nas systemd-networkd[531]: enp7s0: Failed
mai 14 08:00:11 nas avahi-daemon[775]: Joining mDNS multicast group on interface enp7s0.IPv4 with address 192.168.10.10.
mai 14 08:00:11 nas avahi-daemon[775]: New relevant interface enp7s0.IPv4 for mDNS.
mai 14 08:00:11 nas avahi-daemon[775]: Registering new address record for 192.168.10.10 on enp7s0.IPv4.
mai 14 08:00:17 nas autoshutdown[3245501]: root: INFO: '_get_network_details(): 'enp7s0' has IPv4 address: 192.168.10.10, IPv6 address: N/A'
mai 14 08:00:17 nas autoshutdown[3245501]: root: INFO: '_check_ul_dl_rate(): Running on interface: enp7s0'

I can confirm there is no connection with autoshutdown-plugin. The problem appears randomly after resuming. I will try to check my switch and my network card.

EDIT : editing the /etc/default/networking file is useless, it doesn't work.

I Will try a fix proposed by chatGPT :

nano /etc/systemd/system/fix-network-after-resume.service

[Unit]
Description=Reconfigure enp7s0 after resume
After=suspend.target
Wants=network-online.target

[Service]
Type=oneshot
ExecStart=/bin/bash -c "sleep 5 && networkctl reconfigure enp7s0"

[Install]
WantedBy=suspend.target

No one has any idea ???

Quote from raulfg3

please delete the atached files and change passwords.

Thank you very much, I didn't know that the check put the .env information in plain text.

Quote from ryecoaaron

This should be fixed in 7.4.5 in the repo now.

It works successfully ! Thank you !

Ok thanks for the explanation.

If you need any further information or testing, don't hesitate to ask here.

Waiting for a patch, I thank you for your help and all your work in this community around openmediavault.

Quote from ryecoaaron

When you obfuscate paths and uuids, it just makes it harder to tell what the script is doing. Trying to figure out what is wrong.

Quote from ryecoaaron

Can you post the output of the Check button on the Files tab for this compose file?

Hello,

I have 2 redis volumes for nextcloud and onlyoffice that don't save to a compose stack. The plugin detects a comment # SKIP_BACKUP therefore the skip but no such comment is present. Moreover, even when adding # BACKUP, the backup skips the volume.

Attached: the stack compose and the output of the backup

EDIT : I confirm there is no connection between the VM and the problem

I will try to edit /etc/default/networking :

# Configuration for networking init script being run during
# the boot sequence

# Set to 'no' to skip interfaces configuration on boot
#CONFIGURE_INTERFACES=yes

# Don't configure these interfaces. Shell wildcards supported/
#EXCLUDE_INTERFACES=

# Set to 'yes' to enable additional verbosity
#VERBOSE=no

# Method to wait for the network to become online,
# for services that depend on a working network:
# - ifup: wait for ifup to have configured an interface. # TESTED = DIDN'T WORK
# - route: wait for a route to a given address to appear. # IN TEST
# - ping/ping6: wait for a host to respond to ping packets.
# - none: don't wait.
WAIT_ONLINE_METHOD=route

# Which interface to wait for.
# If none given, wait for all auto interfaces, or if there are none,
# wait for at least one hotplug interface.
#WAIT_ONLINE_IFACE=

# Which address to wait for for route, ping and ping6 methods.
# If none is given for route, it waits for a default gateway.
#WAIT_ONLINE_ADDRESS=

# Timeout in seconds for waiting for the network to come online.
#WAIT_ONLINE_TIMEOUT=300

Edit : I don't think there's a connection between the VM and the problem, it's just random

I tested this morning and no problem.

Edit, i see this log in systemctl -b

avril 24 08:00:11 nas systemd-networkd[515]: enp7s0: Could not set route: Nexthop has invalid gateway. Le réseau n'est pas accessible

Hello,

I have 2 pci-e network cards in my server. 1 for the general operation of my nas, the other (not configured in the openmediavault interfaces) but which I use to bridge my Windows Server VM with the KVM plugin. This vm is connected to a samba share. I use autoshutdown to put my server to sleep at night. It checks that no samba clients are connected by pinging (with the following options:

FORCE_NIC="enp7s0"
CHECK_SAMBA_CLIENTS="true"

My VM has a scheduled task to shut down.

When my vm exceeds the start of the autoshutdown plugin verifications time slot and shuts down, let's say 1 hour later, the plugin verification goes smoothly and my server goes to standby once the VM is shut down. But in this particular case, when my server comes out of standby, I lose my default gateway in my ip routes. I have to go to the openmediavault web interface locally, and re-enter my interface settings to recover my route (or add it by hand).

Quote from chente

Read here:

Thread

Guide - Custom cpu temp script for openmediavault-cputemp plugin

With the latest version of the cputemp plugin, additional cpu temp support can be added without changing the plugin.

Creation of a script that gets the temperature is required. The cputemp plugin by default does not support my Ryzen 3600. Here is how you can customize the plugin to work with the Ryzen. This will most likely not work work with other chips. You will need to ask for support on the forum to write a custom cpu-temp script for your system.

Make sure to install and configure the…

ryecoaaron

Jan 20th 2023

Thank you it's works

Hello,

I've installed the cpu-temp plugin but the temperature displayed never moves and doesn't seem to be the real temperature of my processor.

OK Tanks

Quote from Soma

Enable backports on the omv-extras GUI if you are using KVM plugin.

It found 15 updtaes 😂

They are all installed correctly

Thank you for your help

Can you just explain me what are the backports ? I'm not sure what it is.

For several weeks I've had 4 updates in my list of updates that won't install. I've tried rebooting, running the command: sudo apt-get update && apt-get upgrade but to no avail.

Output of the installation :

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be REMOVED:
  linux-image-6.1.0-31-amd64
The following packages have been kept back:
  openmediavault-kvm
0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
After this operation, 409 MB disk space will be freed.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 58585 files and directories currently installed.)
Removing linux-image-6.1.0-31-amd64 (6.1.128-1) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-31-amd64
/etc/kernel/postrm.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.12.12+bpo-amd64
Found initrd image: /boot/initrd.img-6.12.12+bpo-amd64
Found linux image: /boot/vmlinuz-6.12.9+bpo-amd64
Found initrd image: /boot/initrd.img-6.12.9+bpo-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

END OF LINE

Its normal ?

My server asked me to restart (something I had already tried to do to fix the problem) and it's been 2 days that the connection on port 443 is no longer detected and consequently my server shuts down as it should.

I don't know what could have caused the problem in the first place.