Failed to boot to DSM after update to rr 24.6.4

[StatCombo]

After update all (from 24.5.6 to 24.6.4) system stop booting up in DSM.... i am already try change (Priority to USE official drivers false\true) but it's not helping! please help find the way!
CPU: i3 8100
RAM: 32gb ddr4
All ethernet cards available with ip address but the DSM won't boot!
find.synology.com same not find!
i am try to use 24.6.3 and it works fine!, please recheck all about 24.6.4 best regards!

[yunzhongci]

我也是退回24.6.3才正常

[wjz304]

请填写以下信息.
Please fill in the following information.

Install ENV: (You can find it in the boot interface.)

• DMI:
• CPU:
• NIC: (pid & vid)

RR version: (You can find it in the update menu.)

• RR:
• addons:
• modules:
• lkms:

DSM:

• model:
• version:

Issue:

logs:

(请先看一下#173、#175、#226的内容)
(Plz review the content of #173, #175, #226 first)
...

... 如果你提供不了详细信息，那就等有缘人吧!
... If you can't provide detailed information, then wait for someone who is destined!

[StatCombo]

Install ENV: Baremetal UEFi x64

DMI: Filled by O.E.M ASRock Z370M-itx/ac
CPU: Intel core i3 8100
NIC: (can't view pid/vid right Now, but in my mobo built in 2x Ethernet i211AT and i219V)
RR version: (24.6.4)

RR: 26.6.4
addons: 24.6.0
modules: 24.6.1
lkms: 24.5.0

DSM
model: DS918+
version: 7.2.1 u5

Boot logs can make later!

[wjz304]

rp-lkms-24.5.0.zip

Used RR v24.6.4

curl -kL https://github.com/user-attachments/files/15858868/rp-lkms-24.5.0.zip -o /tmp/rp-lkms-24.5.0.zip
export DEBUG=1
menu.sh

Update menu ->Update LKMs

rebuild
reboot

[StatCombo]

Ok I try this later

[StatCombo]

rp-lkms-24.5.0.zip

Used RR v24.6.4

curl -kL https://github.com/user-attachments/files/15858868/rp-lkms-24.5.0.zip -o /tmp/rp-lkms-24.5.0.zip
export DEBUG=1
menu.sh

Update menu ->Update LKMs

rebuild reboot

In my system LKMs updated to 24.5.0 with 24.6.4 rr automatically... But it's not working... Rr works fine, but can't boot to DSM!, or try again update to 24.6.4rr and update lkms manually?

[nillebor]

In my system LKMs updated to 24.5.0 with 24.6.4 rr automatically... But it's not working... Rr works fine, but can't boot to DSM!, or try again update to 24.6.4rr and update lkms manually?

You can activate "direct boot" in advanced Settings. I also had the problem since 24.5.2+. Your problem looks very similar.

#963 (comment)

[StatCombo]

In my system LKMs updated to 24.5.0 with 24.6.4 rr automatically... But it's not working... Rr works fine, but can't boot to DSM!, or try again update to 24.6.4rr and update lkms manually?

You can activate "direct boot" in advanced Settings. I also had the problem since 24.5.2+. Your problem looks very similar.

#963 (comment)

It's stranger, because 24.6.3 RR works perfectly without direct boot...

[wjz304]

try 24.6.5

[yunzhongci]

尝试 24.6.5

更新到24.6.5还是无法启动
但是按照上面的 在高级设置中激活“直接启动” 设置之后，就能启动进入群晖了

[StatCombo]

I think something wrong, 6.3 works perfectly without any directboot options!

[wjz304]

I think something wrong, 6.3 works perfectly without any directboot options!

Get the logs (get the logs that can't be boot)

[StatCombo]

I think something wrong, 6.3 works perfectly without any directboot options!

Get the logs (get the logs that can't be boot)

Ok I try

[wjz304]

try https://github.com/RROrg/rr/releases/tag/24.6.6

[yunzhongci]

try https://github.com/RROrg/rr/releases/tag/24.6.6

还是需要在高级设置中激活 直接启动才行

[wjz304]

try https://github.com/RROrg/rr/releases/tag/24.6.6

还是需要在高级设置中激活 直接启动才行

没有任何日志，能猜到可能的原因点 都回退了，

[yunzhongci]

try https://github.com/RROrg/rr/releases/tag/24.6.6

还是需要在高级设置中激活 直接启动才行

没有任何日志，能猜到可能的原因点 都回退了，

如何查看日志记录？
编译之后，启动，启动不了，需要重启用键盘选项进入arpl，这种情况，日志在哪里查看？
我可以等晚上再测试找一下日志

[wjz304]

(请先看一下https://github.com/RROrg/rr/issues/173、https://github.com/RROrg/rr/issues/175、#226的内容)
(Plz review the content of #173, #175, #226 first)

[StatCombo]

(请先看一下https://github.com/RROrg/rr/issues/173、https://github.com/RROrg/rr/issues/175、#226的内容) (Plz review the content of #173, #175, #226 first)

So i try to get logs.... added addon dbgutils and rebuild RR. And i am wait 10min.
After 10min no logs folder in p1 volume....
May be you have more method to get the logs for debug the problem?