BUG SA6400 Custom Kernel (N100/i226) - LVM Volumes not auto-mounting on boot

[vuminhtuanhvtc]

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

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

• DMI: Default string (Generic/DIY Mainboard)
• CPU: Intel N100
• NIC: Intel i226 (igc driver)

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

• RR: 25.12.0
• addons: 25.12.0
• modules: Default (25.11.0)
• lkms: Default (25.11.0)

DSM:

• model: SA6400
• version: DSM 7.2 (72806u4)

Issue:
After updating to RR 25.12.0 and switching to "Custom Kernel" on SA6400 (Intel N100), the DSM boots up but all storage pools/volumes are in "Crashed" status.

Troubleshooting details:

1. cat /proc/mdstat shows RAID is healthy/active (logs below).
2. ls -l /dev/mapper shows volume groups (vg1, vg2, vg3) exist but are NOT active.
3. The LVM does not auto-activate during boot.
4. I have to manually run mount /dev/mapper/vgX /volumeX via SSH to mount them, but File Station still does not show files (likely due to share links missing).
5. Attempted to use Task Scheduler (triggered on Boot-up) to run vgchange -ay and mount commands, but the task fails to execute or has no effect.

I am reverting to the Official Kernel for now due to this instability.

logs:

root@nas:~# cat /proc/mdstat

Personalities : [raid1] [raid0] [raid6] [raid5] [raid4] [raidF1]
md2 : active raid5 sata2p3[3] sata3p3[4] sata1p3[6]
      7792588416 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]

md4 : active raid1 sata4p5[0]
      11708154880 blocks super 1.2 [1/1] [U]

md3 : active raid0 nvme0n1p3[0] nvme1n1p3[1]
      978766464 blocks super 1.2 64k chunks [2/2] [UU]

md1 : active raid1 sata2p2[0] sata1p2[27] sata3p2[28] sata4p2[26]
      2096128 blocks super 1.2 [26/4] [UUUU______________________]

md0 : active raid1 sata2p1[0] sata1p1[27] sata4p1[26] sata3p1[1]
      8387584 blocks super 1.2 [26/4] [UUUU______________________]

unused devices: <none>
root@nas:~# ls -l /dev/mapper

Plaintext

total 0
crw------- 1 root root  10, 236 Dec 19 00:12 control
brw------- 1 root root 250,   2 Dec 19 00:12 vg1-syno_vg_reserved_area
brw------- 1 root root 250,   3 Dec 19 00:12 vg1-volume_1
brw------- 1 root root 250,   4 Dec 19 00:12 vg2-syno_vg_reserved_area
brw------- 1 root root 250,   5 Dec 19 00:12 vg2-volume_2
brw------- 1 root root 250,   0 Dec 19 00:12 vg3-syno_vg_reserved_area
brw------- 1 root root 250,   1 Dec 19 00:12 vg3-volume_3

[vuminhtuanhvtc]

Update: Critical Network Issue when reverting to Official Kernel

I attempted to switch back to the Official Kernel to see if it resolves the "Volume Crashed" issue mentioned above, but I ran into a severe network isolation problem.

Scenario:

1. In RR Loader menu, I switched Kernel from custom to official.
2. Rebuilt loader and rebooted.

Symptoms:

• The router's DHCP server assigns IPs correctly to the NAS (I can see DHCPACK logs in my router for the Real MAC addresses).
• However, the NAS is completely unreachable:
  • NO Ping response from any of the assigned IPs.
  • NO Web UI access (Port 5000).
  • Synology Assistant cannot find the device.

Comparison:

• On Custom Kernel: Network works perfectly (i226 NICs detected native as eth0~eth3), but Volumes fail to mount automatically (Crashed).
• On Official Kernel: Network is physically up (DHCP works) but logically blocked (cannot access DSM), likely due to interface mapping mismatch or ghost bond configurations conflicting with the injected drivers for N100.

Current Deadlock:
I am currently stuck. I cannot use the Official Kernel because of network lockout, and I cannot use the Custom Kernel comfortably because of the manual volume mounting requirement on every boot.

Is there a recommended way to force a clean network reset when switching to Official Kernel without reinstalling DSM? Or is there a fix for the LVM auto-mount on Custom Kernel coming soon?

[wjz304]

建议先回退到 official with 7.2

[vuminhtuanhvtc]

I followed your advice and reverted the bootloader to Official Kernel with DSM 7.2, but the issue persists. I am now completely locked out of the NAS due to network isolation.

Environment:

Hardware: SA6400 (Intel N100) with 4x Intel i226 NICs.

Network Config: Standard default setup (DHCP), no special configurations.

Symptoms:

Physical: NIC LEDs are blinking active.

DHCP Success: My router logs confirm that it successfully assigns IPs to the NAS MAC addresses.

Network Failure:

Cannot Ping: All assigned IPs return "Request Timed Out".

No Web UI: Port 5000 is unreachable.

Discovery Failed: Synology Assistant and finds.synology.com cannot find the device.

Observation:

When using Custom Kernel: The network works perfectly (native driver).

When using Official Kernel: The network stack seems broken. It handles DHCP requests but drops all other traffic.

Is there a specific boot argument or module I need to check for i226 support on the Official Kernel?

---

感谢回复。我按照您的建议回退到了 Official Kernel (官方内核) + DSM 7.2，但现在因为网络中断，完全无法连接 NAS。

环境信息：

硬件： SA6400 (Intel N100)，配备 4个 Intel i226 网口。

网络配置： 标准默认设置 (DHCP)，无任何特殊配置。

故障现象：

物理层： 网口指示灯闪烁正常。

DHCP 成功： 路由器日志显示已成功给设备分配了 IP 地址。

网络不通：

无法 Ping 通： 所有分配的 IP 均无响应。

无法访问 Web： 端口 5000 无法连接。

无法发现设备： Synology Assistant 和 finds.synology.com 均搜不到设备。

观察对比：

使用 Custom Kernel 时：网络完全正常（原生驱动）。

使用 Official Kernel 时：网络协议栈似乎有问题，能完成 DHCP 握手，但拒绝/丢失其他所有流量。

请问针对 N100 的 i226 网卡在 Official 内核下是否需要特殊的启动参数或驱动模块配置？

[wjz304]

没出现过这种情况，你如果对 linux 比较了解，可以通过 'Boot Recovery' 挂载 /dev/md0， 查看DSM 的日志有没有异常

[vuminhtuanhvtc]

** THIS IS FULL DEBUG LOGS (Split into 4 parts due to size limit):**

Part 1/4: https://pastebin.com/CUGcdntR
Part 2/4: https://pastebin.com/fHvn1wR0
Part 3/4: https://pastebin.com/0bA5fQ8V
Part 4/4: https://pastebin.com/YFPaHkNd

I hope these logs can help identify the issue. Please let me know if you need any additional information.

Thank you for your time and for maintaining this excellent project!

[wjz304]

2025-12-20T20:07:39+07:00 nas nmbd[8780]: SYSTEM:	Last message 'net_lnx_get_v6ip.c:6' repeated 71 times, suppressed by syslog-ng on nas
2025-12-20T20:07:39+07:00 nas kernel: [154668.399794] scemd[18352]: segfault at 8 ip 000055d6cddefdab sp 00007ff0f5883730 error 4 in scemd[55d6cddd7000+31000]
2025-12-20T20:07:39+07:00 nas kernel: [154668.411639] Code: 8b 3d 01 38 03 00 48 85 ff 0f 84 30 01 00 00 48 83 3d 88 37 03 00 00 0f 84 22 01 00 00 4c 8b 05 03 38 03 00 48 8b 47 28 31 d2 <48> 8b 78 08 8b 70 10 48 8d 4f 04 85 f6 0f 84 97 05 00 00 66 90 8b
2025-12-20T20:07:39+07:00 nas coredump[18360]: Process scemd[11460](/usr/syno/bin/scemd) dumped core on signal [11]. Core file [/var/crash/@scemd.synology_epyc7002_sa6400.72806.core.gz]. Cmdline [/usr/syno/bin/scemd ]
2025-12-20T20:07:39+07:00 nas nmbd[21359]: net_lnx_get_v6ip.c:65 Fail to open [/proc/net/if_inet6], errno=[2/No such file or directory]
2025-12-20T20:07:39+07:00 nas nmbd[21359]: net_lnx_get_v6ip.c:65 Fail to open [/proc/net/if_inet6], errno=[2/No such file or directory]
2025-12-20T20:07:39+07:00 nas nmbd[21359]: net_lnx_get_v6ip.c:65 Fail to open [/proc/net/if_inet6], errno=[2/No such file or directory]
2025-12-20T20:07:39+07:00 nas nmbd[8780]: SYSTEM:	Last message 'net_lnx_get_v6ip.c:6' repeated 3 times, suppressed by syslog-ng on nas
2025-12-20T20:07:39+07:00 nas coredump[18360]: Core file [/var/crash/@scemd.synology_epyc7002_sa6400.72806.core.gz] size [1231871]
2025-12-20T20:07:39+07:00 nas nmbd[21359]: net_lnx_get_v6ip.c:65 Fail to open [/proc/net/if_inet6], errno=[2/No such file or directory]
2025-12-20T20:07:39+07:00 nas nmbd[21359]: net_lnx_get_v6ip.c:65 Fail to open [/proc/net/if_inet6], errno=[2/No such file or directory]
2025-12-20T20:07:39+07:00 nas nmbd[21359]: net_lnx_get_v6ip.c:65 Fail to open [/proc/net/if_inet6], errno=[2/No such file or directory]

[vuminhtuanhvtc]

Hi @wjz304,

Thank you for looking into the logs and identifying the scemd crash issue!

UPDATE:
After 2 days of troubleshooting, I managed to get the system working with Custom Kernel. Here's what happened:

1. I switched back to Custom Kernel in the bootloader
2. During boot, DSM prompted me to reinstall/rebuild (requiring PAT file upload)
3. After completing the rebuild process, the system now works smoothly on Custom Kernel

Current Status:
✅ Custom Kernel - Working perfectly
✅ All 4 i226 NICs detected and functional
✅ Volumes mount automatically
✅ All services running normally

It seems the reinstall/rebuild process resolved whatever configuration issue was preventing Custom Kernel from working properly before.

However, the Official Kernel network lockout issue still remains unresolved. If you have time to investigate that in the future, the debug logs I provided earlier might be helpful.

[wjz304]

不建议 custom <-> official 反复切换，虽然我修复了旧版本不能互相切换的bug, 但是反复切换依然可能造成某些软件的不兼容

[wjz304]

2025-12-20T20:07:39+07:00 nas nmbd[8780]: SYSTEM:	Last message 'net_lnx_get_v6ip.c:6' repeated 71 times, suppressed by syslog-ng on nas
2025-12-20T20:07:39+07:00 nas kernel: [154668.399794] scemd[18352]: segfault at 8 ip 000055d6cddefdab sp 00007ff0f5883730 error 4 in scemd[55d6cddd7000+31000]
2025-12-20T20:07:39+07:00 nas kernel: [154668.411639] Code: 8b 3d 01 38 03 00 48 85 ff 0f 84 30 01 00 00 48 83 3d 88 37 03 00 00 0f 84 22 01 00 00 4c 8b 05 03 38 03 00 48 8b 47 28 31 d2 <48> 8b 78 08 8b 70 10 48 8d 4f 04 85 f6 0f 84 97 05 00 00 66 90 8b
2025-12-20T20:07:39+07:00 nas coredump[18360]: Process scemd[11460](/usr/syno/bin/scemd) dumped core on signal [11]. Core file [/var/crash/@scemd.synology_epyc7002_sa6400.72806.core.gz]. Cmdline [/usr/syno/bin/scemd ]
2025-12-20T20:07:39+07:00 nas nmbd[21359]: net_lnx_get_v6ip.c:65 Fail to open [/proc/net/if_inet6], errno=[2/No such file or directory]
2025-12-20T20:07:39+07:00 nas nmbd[21359]: net_lnx_get_v6ip.c:65 Fail to open [/proc/net/if_inet6], errno=[2/No such file or directory]
2025-12-20T20:07:39+07:00 nas nmbd[21359]: net_lnx_get_v6ip.c:65 Fail to open [/proc/net/if_inet6], errno=[2/No such file or directory]
2025-12-20T20:07:39+07:00 nas nmbd[8780]: SYSTEM:	Last message 'net_lnx_get_v6ip.c:6' repeated 3 times, suppressed by syslog-ng on nas
2025-12-20T20:07:39+07:00 nas coredump[18360]: Core file [/var/crash/@scemd.synology_epyc7002_sa6400.72806.core.gz] size [1231871]
2025-12-20T20:07:39+07:00 nas nmbd[21359]: net_lnx_get_v6ip.c:65 Fail to open [/proc/net/if_inet6], errno=[2/No such file or directory]
2025-12-20T20:07:39+07:00 nas nmbd[21359]: net_lnx_get_v6ip.c:65 Fail to open [/proc/net/if_inet6], errno=[2/No such file or directory]
2025-12-20T20:07:39+07:00 nas nmbd[21359]: net_lnx_get_v6ip.c:65 Fail to open [/proc/net/if_inet6], errno=[2/No such file or directory]

很且怪，而且 ipv6 的驱动 自始至终我并没有动过