Closed StatCombo closed 2 months ago
我也是退回24.6.3才正常
请填写以下信息.
Please fill in the following information.
Install ENV: (You can find it in the boot interface.)
RR version: (You can find it in the update menu.)
DSM:
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!
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!
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
Ok I try this later
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?
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.
https://github.com/RROrg/rr/issues/963#issuecomment-2155874296
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.
It's stranger, because 24.6.3 RR works perfectly without direct boot...
try 24.6.5
尝试 24.6.5
更新到24.6.5还是无法启动 但是按照上面的 在高级设置中激活“直接启动” 设置之后,就能启动进入群晖了
I think something wrong, 6.3 works perfectly without any directboot options!
I think something wrong, 6.3 works perfectly without any directboot options!
Get the logs (get the logs that can't be boot)
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
还是需要在高级设置中激活 直接启动才行
还是需要在高级设置中激活 直接启动才行
没有任何日志,能猜到可能的原因点 都回退了,
还是需要在高级设置中激活 直接启动才行
没有任何日志,能猜到可能的原因点 都回退了,
如何查看日志记录? 编译之后,启动,启动不了,需要重启用键盘选项进入arpl,这种情况,日志在哪里查看? 我可以等晚上再测试找一下日志
(请先看一下https://github.com/RROrg/rr/issues/173、https://github.com/RROrg/rr/issues/175、#226的内容) (Plz review the content of https://github.com/RROrg/rr/issues/173, https://github.com/RROrg/rr/issues/175, https://github.com/RROrg/rr/issues/226 first)
(请先看一下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?
If the kernel crashes or the boot disk cannot be recognized, the logs will not be get.
So? No way to understand why? Direct boot works perfectly... And 24.6.3 RR without Direct boot works fine. only 24.6.4 and upper not boot without direct mode...
The root cause should be Kernel crash.
If you want to solve it, you can only use the elimination method. But there are 20 or 30 changes, and it is impossible to exclude them one by one. If all are excluded, it will be the same as 24.6.3, so there is no need to upgrade.
But we need to find why the kernel is crashing in boot process... May be we can test your build of RR one by one with exclude changes? To find out one reason why the kernel is crash?
Yes, but it is a long process. The entire compilation process of modifying the kernel takes several hours. And it needs to be tested many times.
I will modify a few that may be related to startup and compile one.
Yes, but it is a long process. The entire compilation process of modifying the kernel takes several hours. And it needs to be tested many times.
I will modify a few that may be related to startup and compile one.
I am ready, I think we find it together.. I can test the build
https://github.com/RROrg/rr-build/actions/runs/9626756901 disable: CONFIG_LXT_PHY, CONFIG_INTEL_XWAY_PHY, CONFIG_INTEL_IOMMU_DEFAULT_ON
https://github.com/RROrg/rr-build/actions/runs/9626756901 disable: CONFIG_LXT_PHY, CONFIG_INTEL_XWAY_PHY, CONFIG_INTEL_IOMMU_DEFAULT_ON
same not boot... same problem! logs folder unavailable i checked it ... NEXT)))
https://github.com/RROrg/rr-build/actions/runs/9627637229 disable CONFIG_EFI_STUB, IOMMU_SVA
It takes about 3 hours to make a version. I will annotate them in batches. You can wait for more and test them together.
It takes about 3 hours to make a version. I will annotate them in batches. You can wait for more and test them together.
it's nevermind. i am download @disable CONFIG_EFI_STUB, IOMMU_SVA@ version! i am Very want to find ERROR! thnak you very much for supporting! but download speed is SLOW.... and i need only IMG variant!, may be build only one for testing? it's faster for downloading and checking... Best regards!
It takes about 3 hours to make a version. I will annotate them in batches. You can wait for more and test them together.
it's nevermind. i am download @disable CONFIG_EFI_STUB, IOMMU_SVA@ version! i am Very want to find ERROR! thnak you very much for supporting! but download speed is SLOW.... and i need only IMG variant!, may be build only one for testing? it's faster for downloading and checking... Best regards!
next
disable CONFIG_EFI_STUB, IOMMU_SVA
Not boot!....
24.6.3 - 24.6.4 All options for kernel modification
BR2_PACKAGE_QEMU=y 9634043573
BR2_PACKAGE_QEMU_TOOLS=y 9634043573
BR2_PACKAGE_QEMU_GUEST_AGENT=y 9634043573
CONFIG_VMWARE_BALLOON=m 9634043573 9632096082
CONFIG_ATL2=m 9634043573 9632096082
CONFIG_IAVF=m 9634043573 9632096082
CONFIG_LXT_PHY=m 9634043573 9632096082 9629339161 9628479717 9627637229 9626756901
CONFIG_INTEL_XWAY_PHY=m 9634043573 9632096082 9629339161 9628479717 9627637229 9626756901
CONFIG_USB_NET_RNDIS_WLAN=m 9634043573 9632096082 9629339161 9628479717
CONFIG_USB4_NET=m 9634043573 9632096082 9629339161
CONFIG_USB_OTG=y 9634043573 9632096082 9629339161
CONFIG_USB_XHCI_HCD=m 9634043573 9632096082 9629339161
CONFIG_USB_XHCI_PCI_RENESAS=m 9634043573 9632096082 9629339161
CONFIG_USB_XHCI_PLATFORM=m 9634043573 9632096082 9629339161
CONFIG_USB_EHCI_HCD=m 9634043573 9632096082 9629339161
CONFIG_USB_EHCI_ROOT_HUB_TT=y 9634043573 9632096082 9629339161
CONFIG_USB_EHCI_PCI=m 9634043573 9632096082 9629339161
CONFIG_USB_EHCI_FSL=m 9634043573 9632096082 9629339161
CONFIG_USB_EHCI_HCD_PLATFORM=m 9634043573 9632096082 9629339161
CONFIG_USB_OHCI_HCD=m 9634043573 9632096082 9629339161
CONFIG_USB_UHCI_HCD=m 9634043573 9632096082 9629339161
CONFIG_USB_SERIAL_CH341=m 9634043573 9632096082
CONFIG_USB_SERIAL_CP210X=m 9634043573 9632096082
CONFIG_USB_SERIAL_FTDI_SIO=m 9634043573 9632096082
CONFIG_USB_SERIAL_PL2303=m 9634043573 9632096082
CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y 9634043573 9632096082 9629339161 9628479717
CONFIG_IOMMU_SVA=y 9634043573 9632096082 9629339161 9628479717 9627637229
CONFIG_INTEL_IOMMU_SVM=y 9634043573 9632096082 9629339161 9628479717
CONFIG_INTEL_IOMMU_DEFAULT_ON=y 9634043573 9632096082 9629339161 9628479717 9627637229 9626756901
CONFIG_BCM_KONA_USB2_PHY=m 9634043573 9632096082 9629339161 9628479717
CONFIG_FORCEDETH=m 9634043573
CONFIG_SFC=m 9634043573
CONFIG_SFC_MCDI_MON=y 9634043573
CONFIG_SFC_SRIOV=y 9634043573
CONFIG_SFC_MCDI_LOGGING=y 9634043573
CONFIG_SFC_SIENA=m 9634043573
CONFIG_SFC_SIENA_MCDI_MON=y 9634043573
CONFIG_SFC_SIENA_SRIOV=y 9634043573
CONFIG_SFC_SIENA_MCDI_LOGGING=y 9634043573
CONFIG_VIA_RHINE=m 9634043573
CONFIG_VIA_RHINE_MMIO=y 9634043573
try to use 6.3 USB params
try to use 6.3 USB params
Is it easier to try booting using sata? That should eliminate the USB-related options.
Is it easier to try booting using sata? That should eliminate the USB-related options.
sorry but i can't use the SATA.... my NAS is fully assembled, i can use only USB boot method
Is it easier to try booting using sata? That should eliminate the USB-related options.
sorry but i can't use the SATA as boot drive.... my NAS is fully assembled, i can use only USB boot method
CONFIG_USB_XHCI_HCD=m CONFIG_USB_XHCI_PCI_RENESAS=m CONFIG_USB_XHCI_PLATFORM=m CONFIG_USB_EHCI_HCD=m CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_PCI=m CONFIG_USB_EHCI_FSL=m CONFIG_USB_EHCI_HCD_PLATFORM=m CONFIG_USB_OHCI_HCD=m CONFIG_USB_UHCI_HCD=m
somthing here i think...
24.6.3 - 24.6.4 All options for kernel modification
The same problem started with me from version 24.5.3. The last working version was 24.5.1. However, I have not tested the pre-release 24.5.2. You may still consider the changes from 24.5.1
USB is basically an extension of special models. In theory, non-specific devices will not be called. It is mainly virtualization and memory related options. compiling one version now, the next next version will try to remove USB*
same problem
i think it's not same problem... first i think we need to find difference beetwen 6.3 and 6.4 and after find difference beetwen 5.1 and 5.3
24.6.3 - 24.6.4 All options for kernel modification
The same problem started with me from version 24.5.3. The last working version was 24.5.1. However, I have not tested the pre-release 24.5.2. You may still consider the changes from 24.5.1
5.1 - 5.3 only delete DMRAID,What is your motherboard? Is raid enabled?
@wjz304 https://github.com/RROrg/rr/issues/963#issuecomment-2146186355
RAID ist disabled. I have tested all versions before and after. Direct boot solves the problem as well as @StatCombo. I can live with it if necessary. But the problem is deeper.
The hardest thing is that it only happens in certain circumstances.... :( The hardware I have is very limited.
The hardest thing is that it only happens in certain circumstances.... :( The hardware I have is very limited.
we FIND the way together. Now i go to sleep, and tomorrow i will check this topic for your messages! waht your time zone GMT? my is +3
+8 now
https://github.com/RROrg/rr-build/actions/runs/9628479717 disable BCM_KONA_USB2_PHY, INTEL_IOMMU_SVM, VIRTIO_MMIO_CMDLINE_DEVICES, USB_NET_RNDIS_WLAN
https://github.com/RROrg/rr-build/actions/runs/9629339161 CONFIG_USB4_NET CONFIG_USB_OTG CONFIG_USB_XHCI_HCD=m CONFIG_USB_XHCI_PCI_RENESAS=m CONFIG_USB_XHCI_PLATFORM=m CONFIG_USB_EHCI_HCD=m CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_PCI=m CONFIG_USB_EHCI_FSL=m CONFIG_USB_EHCI_HCD_PLATFORM=m CONFIG_USB_OHCI_HCD=m CONFIG_USB_UHCI_HCD=m
https://github.com/RROrg/rr-build/actions/runs/9629339161 CONFIG_USB4_NET CONFIG_USB_OTG CONFIG_USB_XHCI_HCD=m CONFIG_USB_XHCI_PCI_RENESAS=m CONFIG_USB_XHCI_PLATFORM=m CONFIG_USB_EHCI_HCD=m CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_PCI=m CONFIG_USB_EHCI_FSL= m CONFIG_USB_EHCI_HCD_PLATFORM=m CONFIG_USB_OHCI_HCD=m CONFIG_USB_UHCI_HCD=m
今天这两个,也都需要在高级设置中开启直接启动才可以
实际情况是,不开启直接启动,eth0超时,eth1显示有ip,ip为192.168.1.50,但是实际上无论在路由器还是用群晖的搜索都搜不到 而开启直接启动之后,eth0和eth1都有ip而且可以在路由器和搜索中找到。
我还怀疑了一下是不是我将两个网口设置了链路聚合的原因,刚才特别测试了一些 跟链路聚合设置无关
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!