Page 1 of 1

[Help] F4-421 Pre 2020. TOS 5.1.145 Crashing

Posted: 12 May 2026, 21:01
by rmistry22
Hi all,

Have an old, F5-421, been advised it cannot be upgraded beyond 5.1.145, it had been working OK for sometime in Isolation mode, now I keep losing access every few days and have to manually force a shutdown and restart.

The device responds to pings, but none of the shares, webpage or SSH connectivity works.

Any help appreciated on how I can fix this.
Thanks
R
F4-220 (died)
F5-421 - not upgradable!!!!

Re: [Help] F4-421 Pre 2020. TOS 5.1.145 Crashing

Posted: 13 May 2026, 14:30
by MikeZhang
rmistry22 wrote: 12 May 2026, 21:01
Based on the information you have provided, there is no SSH connectivity, you may check if there is HDMI port on the back, then plug one HDMI monitor and keyboard to the NAS, observe if there is any output and send us pictures from monitor

Re: [Help] F4-421 Pre 2020. TOS 5.1.145 Crashing

Posted: 14 May 2026, 20:27
by rmistry22
Thanks, I will try that next time it crashes, currently manually restarting daily

Re: [Help] F4-421 Pre 2020. TOS 5.1.145 Crashing

Posted: 29 May 2026, 18:53
by rmistry22
Hi,
It crashed again, managed to capture a screenshot of the output on a monitor.

Image

Appreciate any help.
Thanks in advance.
R

Re: [Help] F4-421 Pre 2020. TOS 5.1.145 Crashing

Posted: 30 May 2026, 14:59
by EriChan
rmistry22 wrote: 29 May 2026, 18:53
Thank you for providing the screenshot. Regarding the issue you are experiencing, we have carefully reviewed your actual screen logs, and here is the detailed explanation and troubleshooting suggestions:

Your kernel logs show severe SATA Link Exception and Wake-up Failure:
ata3.00: waking up from sleep
ata3: hard resetting link
retrying FLUSH 0xea...

Fault Details:
Your TNAS is encountering a classic HDD Hibernation/Sleep Deadlock.
After several days of uptime, your hard drives (ata2, ata3, ata4) will enter power-saving sleep mode. When the system attempts to wake them up to process a request, the drives or the SATA controller fail to respond in a timely manner. The Linux kernel will then attempt a hard reset on the SATA links and get stuck in an error-handling loop.

Since the storage volume becomes completely unresponsive, all higher-level services (Web management interface, SSH remote access, SMB file sharing) will freeze immediately. However, as the motherboard and network chip remain powered on, the device can still respond to ping requests.

Troubleshooting Steps:
1. Disable HDD Hibernation (Primary First Step)
After force-restarting the NAS and successfully logging into the web management interface, please navigate to:
Control Panel > Hardware & Power > Hard Drive Hibernation > Set the standby timer to "Never".
Keep the drives spinning continuously, then observe whether this specific freezing issue persists.

2. Check Hard Drive Health
Generally, hard drive failures can also easily cause wake-up failures in NAS hardware and software environments. It is recommended to go to the TOS system interface > Control Panel > Storage Management > Disks > S.M.A.R.T. to create a quick detection task to check the health status of your hard drives.

Please try disabling HDD hibernation first, then observe whether the system stabilizes.