关于 "启动" 后无法找到DSM -- About not find DSM after "boot the loader"

[wjz304]

当启动后 提示的IP无法访问，或者 find.synology.com 也无法查找到设备的问题.

首先这是一个复杂的问题，并不一定是网卡驱动的问题,大概率是kernel崩溃掉了. 引起kernel崩溃的问题就很复杂了. 还有这个界面就应该是卡死的状态, 橙色提示下光标不应该闪烁，如果一直闪烁可能是硬件与kexec不兼容，这种情况建议切换到"直接启动 或者 内核的切换方式".

如果你无法定位是否kernel崩溃（需要串口）只能尝试进行以下操作:

1. 尝试切换 "LKM 版本", 目前没有统一的标准，有些硬件prod好使，有些硬件只能用dev.
2. 空盘有概率第一次会kernel崩溃,重启会好. (23.10.1 后 崩溃会自动重启)
3. 尝试切换 "直接启动" 或者 "内核的切换方式"，如果是概率性的进不去，切换直接启动大部分会有所缓解.
4. DT型号目前不兼容HBA扩展卡, 如果有会在启动时kernel崩溃，或者识别不到HBA上的硬盘.
5. CPU性能不同，不同得型号首次启动等待时间也略有不同，请耐心等待，(J3455 安装DS920+ 有15分钟的先例.)
6. 存在不兼容的模块也可能导致内核崩溃或者无法获取到有效IP，尝试取消无关的模块.
7. 尝试编译其他型号。

(另外虚拟环境可修改虚拟网卡型号，物理环境可附加USB网卡或者取日志(#173)，来确定是不是网卡驱动的问题)

---

After boot the loader, the IP indicated cannot be accessed, or find.synology.com cannot find the device.

First of all, this is a complicated problem. It is not necessarily a problem with the network card driver. The high probability is that the kernel has crashed. The problem that caused the kernel crash is very complicated. And this interface should be in a stuck state, and the orange prompt The cursor should not blink. If it keeps blinking, it may be that the hardware is not compatible with kexec. In this case, it is recommended to switch to "direct boot or kernel switching method".

If you can't locate whether the kernel crashes (requires a serial port), you can only try the following:

1. Try to switch "LKM version", currently there is no unified standard, some hardware works well the prod, and some hardware can only be used the dev.
2. The empty disk has a probability that the kernel will crash for the first time, and it will be fine after reboot. (After 23.10.1, the crash will automatically reboot.)
3. Try to switch "direct boot" or "kernel switching mode", if this is probabilistic, switching to direct boot will mostly alleviate it.
4. The DT model is currently not compatible with the HBA expansion card, if there is one, the kernel will crash at boot the loader, Or unable to recognize the hard drive on the HBA.
5. The performance of the CPU is different, and the waiting time for the first startup of different models is also slightly different, please wait patiently, (J3455 has a precedent of 15 -30 minutes.)
6. The existence of incompatible modules may also cause the kernel to crash or fail to obtain a valid IP, try to cancel irrelevant modules.
7. Try to compile other models.

(In addition, the virtual network card model can be modified in the virtual environment, and the physical environment can be attached with a USB network card or take the log (#173) to determine whether it is a problem with the network card driver.)

[wjz304]

黑群晖引导成功或引导之后搜索不到机器ip解决方法
https://www.mi-d.cn/8116

[wjz304]

About NIC timeout

1. boot arpl show timeout
   ifconfig to check if IP has been obtained,
   ping 1.1.1.1 to check network connectivity.
   If a valid IP is returned, please ignore this error. Because the initialization process cannot wait endlessly for IP acquisition.

2. boot dsm show timeout
   Please confirm if there is an IP address on the router side and check if it is pinged.
   Adjust the time improvement of "Advanced menu" -> "Timeout of get ip in boot:"
   If a valid IP is returned, please ignore this error. Because the initialization process cannot wait endlessly for IP acquisition.

Both IP addresses are for reference only and do not fully represent the actual situation.