This is a possible PSA: I have not confirmed that File Station 5 update was what actually caused the NAS to reboot. It just happened that after the update, like an hour or so later the NAS rebooted out of the blue. I have opened a ticket with support to see if they can review the logs and see if it was the issue or something else happened.
This was File Station 5 5.5.6.5208_20260310 on QUTS 5.2.8.3359 firmware
Our TVS-1688x has occasionally rebooted for a while. I have swapped the ram with another NAS (both Kingston server ram-about as good as it gets. One batch had Micron and the other Hynex). I never did a ticket because it was so occasional, I thought it would be hard to isolate.and support would run me ragged trying stuff such as ram tests when I know iti is not the ram.
in many cases defective/incompatible RAM has caused reboots, so not necessarily a bad guess for troubleshooting. (Most NAS also do not use ECC RAM either)
Normally the NAS is up 24x7 for months at a time. I usually only bring it down to do firmware updates and the process i follow is update - asks to reboot which i say yes, update and boot up, shutdown and remove power for 30 seconds and restart up.
Not normal issue for my system to just reboot out of the blue like this. only error reported in qulog is Warning 2026-03-16 13:19:25 — — localhost — Power NAS Power Status [Power] The system was not shutdown properly last time.
Support got back to me and they said doesn’t seem to be due to the file station update as the reboot happened 3 hours later. They are working on doing a root cause analysis.
For now disregard my PSA about the File Station update.
If they figure it out, let me know.
So support got back to me, it was not software, but some kind of hardware
Below is their analysis for your records on this matter:
BERT-style analysis:
The system experienced a host reset triggered by a TCO (watchdog) timeout, meaning the CPU/core became unresponsive for a prolonged period (did not respond to SMI interrupts).
There are PCIe / controller-level errors:
Receiver Error (Port0) → indicates signal integrity or hardware communication issue.
Replay Timer Timeout (Port2) → suggests packet retransmission failure / link instability.
Due to these combined issues, the system determined it was in a critical, unrecoverable state, leading to:
Platform crash
Crash log generation
This is a hardware-level instability issue, most likely related to:
PCIe device / controller problems
Possible faulty cable, slot, or device
Firmware or driver instability (less likely but possible)
In short:
System hang → PCIe errors → watchdog timeout → forced host reset → crash log generated.Note: We may need to monitor this system by disabling Watchdog timer if issue reappears. Please let us know if this is reoccurring.
I think my KVM switch i had setup to share a montitor/keyboard on NAS and mini pc was causing the hardware issue. The KVM was causing the mini pc to lockup and blue screen. Once I took the video off the KVM the mini pc was fine. So in my case the external KVM seems to be bad.
TVS-h1688X After years of this occasionally happening, it only happens when using the HDMI port.