Hi
That's correct, because kernel backports were enabled by default with OMV. If available you will get a backport version instead of the original, release kernel...
If you are noticing problems with the backport kernel, you can install the older release kernel. For Debian Bookworm it's the 6.1.x kernel... Debian Trixie will use the 6.12.x kernel as release version...
Best regards
prtigger
By the way, you are not using the stable
Bookworm 6.1.x kernel! You are using the
coming up 6.12.x backport kernel (Trixie)!
But you found the problem and don't
need to try the 6.1.x kernel... 
Best regards
prtigger
Hi
Just for a test:
- You can try to uninstall flashmemory plugin. It´s not recommended for using a USB flash device, but i guess, for a test it´s OK.
- You can install the latest stable 6.1.x Kernel: apt-get install linux-image-amd64=6.1.140-1
Best regards
prtigger
Hi Aaron
Today the problem is coming back with kernel 6.12.22. I can say, there is no relation to your flashmemory plugin.
Because it´s not installed anymore!
In this case today i was removing an older stable kernel with your plugin and after this i was initiating a shutdown from web-gui.
Same failed message and then heavy load on a disk (Access light is permanently on with very little flicker).
I guess , it may be the system disk.
Today, i wait more than 10 minutes... No change... No shutdown... I press and hold power button.
During next boot i got 'reverting journal' message, same like the first time i reported the failure.
Best regards
prtigger
If you've got any useful informations, links how to report kernel problems on the official way, please let me know...
I'm not familiar with it...
Best regards
prtigger
In my opinion, people with older Intel CPUs will get a lot of problems with Debian 13 and the upcoming 6.12 kernel...
If nobody takes care about it...
Best regards
prtigger
By the way... Take a look at swapping behavior!
I noticed strange use of swapping (with default vm.swappiness = 1).
Workaround... Set vm.swappiness = 0
This started with the bpo-kernel 6.12.12
At this time, i had no time to compare with 6.12.22 version...
No problems with 6.1.x!
Hi
I guess, this behavior should be reported to the kernel/driver development. But i've no idea, what's the correct way for bug reporting...
I'm struggling with a tainted kernel with 6.11.x, 6.12.x, 6.14.x... related to old Intel Atom CPU...
OMV development can't support this issues, because they are not maintaining Debian or kernel stuff...
Best regards
prtigger1
Hi
You can try UEFI CSM (Compatibility Support Module). This may be available with your system...
Best regards
prtigger
Hi i would guess, primary a kernel problem... I uninstalled the flashmemory plugin, too. Not happend anymore, till now... If you want it stable, don't use the 6.12.x kernel at this time. This kernel will coming up with Debian 13 (Trixie) for everybody, as default. Up to this point, you could stay with 6.1.x kernel, if it's working with your hardware...
Best regards
prtigger
if you have pve packages installed, I would remove the pve repo. otherwise, you don't get updates.
Hi Aaron
Thanks for your comments.
You know, i'm not an expert like you...
Do you have a short description how to remove the PVE repository?
Best regards
prtigger
Hi Aaron
A short question:
I disabled backports and installed PVE Kernel 6.14 and 6.11 with your kernel plugin, for testing CPU boot warnings with these kernels..
Absolut the same, like Debian 6.12.x bpo kernel... Bad stuff...
Now i want to cleanup the APT repository from PVE and Debian bpo stuff inside... (Still have PVE GRUB version installed...).
Do you know an easy way, or should i reinstall OMV from scratch?
Best regards
prtigger
Hi pro´s
After uninstalling the stable flashmemory plugin, the problem with failed starting of 'logrotate.service', from server
powerless bootup state, is solved...
It may depend on a timing or race condition, because a shutdown and reboot of the system after failed
'logrotate.service' start message, is showing no failure anymore...
root@pr-srv-01:~# journalctl -u logrotate.service
Apr 28 18:35:20 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...
Apr 28 18:35:21 pr-srv-01 systemd[1]: logrotate.service: Deactivated successfully.
Apr 28 18:35:21 pr-srv-01 systemd[1]: Finished logrotate.service - Rotate log files.
-- Boot 24a45e54cf5445f7ade617c9cb22aba9 --
Apr 29 20:44:07 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...
Apr 29 20:44:07 pr-srv-01 systemd[1]: logrotate.service: Deactivated successfully.
Apr 29 20:44:07 pr-srv-01 systemd[1]: Finished logrotate.service - Rotate log files.
root@pr-srv-01:~#A solution could be:
Starting 'logrotate.service' when OMV system is full up.... (later, than configured now!)
Best regards
prtigger
That's tough...
Because i can't confirm a general problem with Samba on OMV 7...
But i'm speaking only for my old hardware..
Ok, thanks..
I'll keeping my eyes on!
What i still not understand is:
What is running parallel when logrotate.service tries to startup during the first boot (reading the log i posted, status is locked)?
And why is everything fine when i shutdown the system after this and boot again??
Why should a start of logrotate.service every boot help (just more compressed files)?
Best regards
prtigger
Hi
Do you set SMB3 as minimal protocol?
That's what i set...
Best regards
prtigger
I just checked the whole output of
journalctl (3500 lines). There are no errors or warnings i had never seen before, after boot.
Only the part i described here in this case.
May be a stupid question:
What about the logs outside of the journal?
What is happening with them?
Thanks for your help
prtigger
It´s not long ago i done the commands from #6
Here the output:
root@pr-srv-01:~# du -h /var/log/journal/
142M /var/log/journal/21bdaa7233734a9491a6b4852adf96b0
142M /var/log/journal/
root@pr-srv-01:~# ls -ahlS /var/log
insgesamt 168K
-rw-r--r-- 1 root root 8,2K 20. Mär 16:57 dpkg.log.12.gz
drwxr-xr-x 13 root root 4,0K 20. Mär 16:57 ..
-rw-r--r-- 1 root root 3,2K 20. Mär 17:57 dpkg.log.10.gz
-rw-rw-r-- 1 root utmp 1,5K 21. Apr 08:35 wtmp
drwxr-xr-x 14 root root 1,3K 21. Apr 08:15 .
-rw-r--r-- 1 root root 1,2K 20. Apr 17:46 dpkg.log.1
drwxr-xr-x 2 root root 580 20. Apr 17:49 apt
drwxr-x--- 3 root adm 540 21. Apr 08:13 samba
drwxr-xr-x 2 root adm 520 21. Apr 08:13 nginx
-rw-r--r-- 1 root root 429 31. Mär 20:12 dpkg.log.9.gz
-rw-r--r-- 1 root root 385 13. Apr 17:57 dpkg.log.5.gz
-rw-r--r-- 1 root root 367 20. Mär 17:14 dpkg.log.11.gz
-rw-r--r-- 1 root root 367 5. Apr 07:55 dpkg.log.7.gz
drwxr-x--- 2 root adm 340 21. Apr 08:15 unattended-upgrades
-rw-r--r-- 1 root root 336 1. Apr 18:19 dpkg.log.8.gz
-rw-rw-r-- 1 root utmp 292 21. Apr 08:35 lastlog
-rw-r--r-- 1 root root 290 6. Apr 18:11 dpkg.log.6.gz
-rw-r--r-- 1 root root 273 14. Apr 20:24 dpkg.log.2.gz
-rw-r--r-- 1 root root 250 13. Apr 18:22 dpkg.log.3.gz
-rw-r--r-- 1 root root 249 13. Apr 18:17 dpkg.log.4.gz
-rw-r--r-- 1 root root 208 21. Apr 08:15 alternatives.log.1
drwxr-xr-x 3 root root 180 17. Mär 21:09 installer
-rw------- 1 root root 140 21. Apr 08:15 php8.2-fpm.log.6.gz
-rw-r--r-- 1 root root 138 14. Apr 21:08 alternatives.log.11.gz
-rw-r--r-- 1 root root 138 21. Apr 08:03 alternatives.log.2.gz
-rw-r--r-- 1 root root 138 20. Apr 17:50 alternatives.log.3.gz
-rw-r--r-- 1 root root 138 20. Apr 17:45 alternatives.log.4.gz
-rw-r--r-- 1 root root 138 18. Apr 16:32 alternatives.log.5.gz
-rw-r--r-- 1 root root 138 18. Apr 16:21 alternatives.log.6.gz
-rw-r--r-- 1 root root 138 17. Apr 07:23 alternatives.log.7.gz
-rw-r--r-- 1 root root 138 16. Apr 21:09 alternatives.log.8.gz
-rw-r--r-- 1 root root 138 16. Apr 21:01 alternatives.log.9.gz
-rw-r--r-- 1 root root 136 16. Apr 20:36 alternatives.log.10.gz
-rw-r--r-- 1 root root 135 14. Apr 20:48 alternatives.log.12.gz
-rw------- 1 root root 117 21. Apr 08:13 php8.2-fpm.log.7.gz
drwxr-xr-x 2 minidlna minidlna 80 20. Mär 17:58 minidlna
-rw------- 1 root root 76 21. Apr 08:03 php8.2-fpm.log.10.gz
-rw------- 1 root root 76 21. Apr 08:03 php8.2-fpm.log.11.gz
-rw------- 1 root root 76 21. Apr 08:03 php8.2-fpm.log.12.gz
-rw------- 1 root root 76 21. Apr 08:15 php8.2-fpm.log.2.gz
-rw------- 1 root root 76 21. Apr 08:15 php8.2-fpm.log.3.gz
-rw------- 1 root root 76 21. Apr 08:15 php8.2-fpm.log.4.gz
-rw------- 1 root root 76 21. Apr 08:15 php8.2-fpm.log.5.gz
-rw------- 1 root root 76 21. Apr 08:03 php8.2-fpm.log.8.gz
-rw------- 1 root root 76 21. Apr 08:03 php8.2-fpm.log.9.gz
drwxr-sr-x+ 3 root systemd-journal 60 17. Mär 21:11 journal
drwxr-xr-x 3 root root 60 17. Mär 20:57 runit
drwxr-xr-x 2 root root 60 17. Mär 20:57 salt
-rw------- 1 root root 56 21. Apr 08:15 php8.2-fpm.log
-rw------- 1 root root 56 21. Apr 08:15 php8.2-fpm.log.1
drwxr-x--- 2 _chrony _chrony 40 17. Mär 21:11 chrony
drwxr-xr-x 2 root root 40 16. Dez 09:36 openmediavault
drwx------ 2 root root 40 23. Dez 14:38 private
lrwxrwxrwx 1 root root 39 17. Mär 20:57 README -> ../../usr/share/doc/systemd/README.logs
-rw-r--r-- 1 root root 0 21. Apr 08:15 alternatives.log
-rw-r--r-- 1 root root 0 23. Dez 14:38 bootstrap.log
-rw-rw---- 1 root utmp 0 21. Apr 08:15 btmp
-rw-rw---- 1 root utmp 0 21. Apr 08:15 btmp.1
-rw-r--r-- 1 root root 0 20. Apr 17:49 dpkg.log
-rw-r--r-- 1 root root 0 23. Dez 14:38 faillog
-rw-r--r-- 1 root root 0 23. Dez 14:38 fontconfig.log
-rw-r----- 1 root adm 0 23. Dez 14:38 monit.log
-rw-r--r-- 1 root root 0 23. Dez 14:38 tallylog
-rw-rw-r-- 1 root utmp 0 21. Apr 08:15 wtmp.1
root@pr-srv-01:~#