FS6812X crash

[rrs]

Hello team,
Love your products (AS-606T, AS6704T(Stark below) and my most recent acquisition FS6812X(Drogon below)) but I think there is a bug with FS6812X where it just stops working.

It becomes unavailable via network (no ping, nothing), power button is lit but does nothing and only way to bring it back is unplug and plug DC power back in.
100% an issue on both 5.0.0.RCG1 and 5.0.0.REO2.

INFO 3/16/2025 4:00 SYSTEM [Rsync] BackupStarktoDrogon" job is finished."
INFO 3/16/2025 4:00 SYSTEM [Rsync] Start BackupStarktoDrogon" job."
INFO 3/16/2025 3:30 SYSTEM [Rsync] DrogonCFGtoStark" job is finished."
INFO 3/16/2025 3:30 SYSTEM [Rsync] Start DrogonCFGtoStark" job."
INFO 3/16/2025 3:20 SYSTEM [System Setting] Success to backup system setting.
INFO 3/16/2025 0:00 SYSTEM [Background Processing -> Schedule] Storage usage calculating is complete.
INFO 3/16/2025 0:00 SYSTEM [Background Processing -> Schedule] Started to calculate storage usage.
INFO 3/15/2025 12:30 SYSTEM [Regional Options] Successfully synced from the NTP server.
INFO 3/15/2025 4:00 SYSTEM [Rsync] BackupStarktoDrogon" job is finished."
INFO 3/15/2025 4:00 SYSTEM [Rsync] Start BackupStarktoDrogon" job."
INFO 3/15/2025 3:30 SYSTEM [Rsync] DrogonCFGtoStark" job is finished."
INFO 3/15/2025 3:30 SYSTEM [Rsync] Start DrogonCFGtoStark" job."
INFO 3/15/2025 3:20 SYSTEM [System Setting] Success to backup system setting.
INFO 3/15/2025 0:00 SYSTEM [Background Processing -> Schedule] Storage usage calculating is complete.
INFO 3/15/2025 0:00 SYSTEM [Background Processing -> Schedule] Started to calculate storage usage.
WARNING 3/14/2025 15:17 SYSTEM [System] The NAS did not shut down properly last time.
INFO 3/14/2025 15:17 SYSTEM [System] System starts.
INFO 3/14/2025 15:17 SYSTEM [Regional Options] Successfully synced from the NTP server.
INFO 3/14/2025 15:17 SYSTEM [Network] LAN2 was plugged in.
INFO 3/14/2025 15:17 SYSTEM [Network] LAN1 was unplugged.
INFO 3/14/2025 15:17 SYSTEM [Network] LAN2 was plugged in.
INFO 3/14/2025 15:17 SYSTEM [Network] LAN1 was unplugged.
INFO 3/14/2025 15:16 SYSTEM [Regional Options] Time zone setting was changed to Athens
INFO 3/14/2025 15:16 SYSTEM [Background Processing -> Schedule] Storage usage calculating is complete.
INFO 3/14/2025 15:16 SYSTEM [Background Processing -> Schedule] Started to calculate storage usage.
INFO 3/14/2025 15:16 SYSTEM [Regional Options] Successfully synced from the NTP server.
INFO 3/14/2025 12:30 SYSTEM [Regional Options] Successfully synced from the NTP server.
INFO 3/14/2025 4:00 SYSTEM [Rsync] BackupStarktoDrogon" job is finished."
INFO 3/14/2025 4:00 SYSTEM [Rsync] Start BackupStarktoDrogon" job."
INFO 3/14/2025 3:30 SYSTEM [Rsync] DrogonCFGtoStark" job is finished."
INFO 3/14/2025 3:30 SYSTEM [Rsync] Start DrogonCFGtoStark" job."
INFO 3/14/2025 3:20 SYSTEM [System Setting] Success to backup system setting.
INFO 3/14/2025 0:00 SYSTEM [Background Processing -> Schedule] Storage usage calculating is complete.
INFO 3/14/2025 0:00 SYSTEM [Background Processing -> Schedule] Started to calculate storage usage.
WARNING 3/13/2025 20:46 SYSTEM [System] The NAS did not shut down properly last time.
INFO 3/13/2025 20:46 SYSTEM [System] System starts.

After the event I didn't see anything suspicious in the logs that would have pointed to an issue (apart from a Warning mentioning that last shutdown wasn't a clean shutdown). However, I enabled max verbose level and syslog, hopefully this will log all info.
What I can say for sure is it happens randomly (few hours to a week).
I know it's not much to go by but maybe there are other users affected.

[rrs]

Issue reoccurred with no user input.
Please see attached screenshots of switch LACP link down, switch logs and asustor logs.

[rrs]

More details below, some might be irrelevant:
Drives, slots and raid volumes:
1* PCIe Gen4x4, 1x 990 pro 2tb, Single
3* PCIe Gen4x2, 2x 990 evo 2tb, 1x 990 evo+ 2tb, RAID5
4* PCIe Gen4x1, 4x 970 evo+ 1tb, RAID10
1* PCIe Gen3x4, n/a
1* PCIe Gen3x2, n/a
2* PCIe Gen3x1 2x intel optane 16gb, RAID1 <--ADM Default Volume w/ 8.8gb free

Services:
Using iSCSI and NFS 24/7
RSync from&to another Asustor NAS(AS6704T) on a daily schedule.
SMB is enabled but never used
No VMs, no Apps installed.

Bios version 1.31
RAM default 16gb ECC
Sys temp 43*C
CPU temp 44*C
LAN1+2 in 802.3ad, dhcp client enabled, no vlan tag

Issue first occurred when I tried to snapshot an iSCSI volume, 25 Dec 2024.

Managed to move all data from it and will perform a factory reset today. If all goes well, my next post will be 2-3 weeks from now saying that the issue is no longer present.

[snapshot]

Do you have both Ethernet ports plugged in to the switch or just one? If it's two, try unplugging one and see if the fault re-occurs.

Your first attachment does not show anything readable. Is it supposed to be the ADM log?

[rrs]

Do you have both Ethernet ports plugged in to the switch or just one? If it's two, try unplugging one and see if the fault re-occurs.

Your first attachment does not show anything readable. Is it supposed to be the ADM log?

Yes and yes, but ADM log shows no faults just previously mentioned warning.
May I ask what is the logic behind plugging just one when using a bond?

[snapshot]

You're trying to find a networking problem so reducing the possible points of failure is a sensible place to start.

[rrs]

Sorry for the late reply, makes sense - and thank you for the assistance, really appreciate it.
Steps taken so far:
1. Migrated everything off from it again
2. Swapped those two intel optanes with a pair of SNS570 (my reason was those only 9GB free space)
3. Factory reset & disabled LACP on switch
4. minimal set up (2 volumes, vol1 is RAID1 with new drives, ports and certificates)
5. Soft reset (locked myself out due to invalid certificate)
6. Added Asustor 2.5 USB-C NIC - All 3 interfaces are in different subnets, GW set to Auto and using DNS from eth0 & 1

Crashed while moving some data - uptime was 6.5hrs
pwr led = blue, health led = green, network led = off, drive led = off

Would like to mention that even tho the last restart was recent the steps above were done few days before this crash - as in volumes we're already fully synced.
Also, is this a bug?

Screenshot 2025-04-06 085833.png

The backup job raising the CPU usage finished just after this screenshot was taken and the crash occurred in under 1minute of the job finishing.

[rrs]

You're trying to find a networking problem so reducing the possible points of failure is a sensible place to start.

Tagging you directly just as an FYI (maybe someone else will pop-up with identical symptoms in the future) - this issue isn't present in proxmox(debian) using the recompiled drivers(bug fix for Auto Negociation) so it is 100% a software issue.
Haven't tried changing the drivers in ADM yet and don't plan to anytime in the future.