Leaderboard

As title, successfull fresh installation with loader 1.03b patfile DS3617_xs-6.2.3-25426 and extra.lzma for loader 1.03b ds3617 DSM 6.2.3 v0.11.1_test without any other network card except Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) used only for ISCSI

I believe you do not need to be concerned. The design of Linux in general is to manage log files in a way that does not exhaust the storage available. Spurious data in logs does use up space, but I did not suggest there was a crash problem solely due to log utilization. Logging is a good thing; zeroing log files is an unnecessary and forensically destructive practice. In DSM, syslog events are logged by default to /var/log/messages. Each Linux installation has syslog rules that split off certain logs to other files. There are also multiple ingress points. Kernel events, for instance, are independently logged to the kernel log and the syslog default. There are a number of unimpactful, essentially useless, and unmanageable error logs due to unsupported system events in XPEnology. My intention was solely to improve the signal to noise ratio in the log files (make them more useful) by suppressing those types of logs.

use the extra/extra2 from the 1st post? if you come from a former version containing jun's extra/extra2 an his i915 driver this driver will not work with the kernel from 6.2.3 and the driver will also prevent the new one from synology to be loaded also in the 1st post is a list of supported pid's from synology's driver, 0412 is in that list there should be no i915.ko in /usr/lib/modules/update/

Выбор не велик, Synology Drive или Nextcloud, оба хороши, для Nextcloud есть очень большая поддержка от сообщества, очень много плагинов и различных сервисов. Nextcloud в отличии от Synology Drive более кропотлива в настройках, Nextcloud лучше ставить через Docker, по установке и настройки Nextcloud можете почитать мою инструкцию на 4PDA.

Hi @hellbound not sure I can help with the memory issue but I'm pretty sure your networking issue is the OVS (Open vSwitch) - this needs to be turned off before you install VirtualBox but since your network is still working perhaps you can just turn it off - it will conflicting with vboxdrvs's own network switch. Please ignore the fact that this says it can't be disabled, that's just because the machine I took the screen cao from is an i7 machine I have VMM running on at work! Back to you memory issue, @nemesis122 was suggesting you look at the grub edit is the post he referenced: That may help, sorry I've not tried to run with that much memory! although the i7 at work is running 8G fine! Best of luck!

maybe you can give a try i dont know if this working but its easy to test generate a new loader with his disable_mtrr

Is there a blog/manual available. I desperately want a new docker version on my 1010+ as well using DSM 6.2+