[Help] F4-424 unreachable every 48-72h (or less)

[EriChan]

Thank you for submitting the debug logs.

Could you please send me a private message (PM) with the email address you used to submit the report? This will help us quickly locate your logs and follow up on your case.

[newtyp3]

Thank you for submitting the debug logs.

Could you please send me a private message (PM) with the email address you used to submit the report? This will help us quickly locate your logs and follow up on your case.

I just sent you a PM, thanks.

[CursaYang]

Our engineer has replied to you by email. Please refer to the attachment guide in the email, and after updating the BIOS, observe whether the same issue recurs.

[newtyp3]

Just PM'ed you as I did not get the email.

[rgrg1]

Checking your debug logs, please wait for our solution

Hello there,

Still waiting for the solution. Today have another silent freeze on Sep 3 (23:14) after ~1 week uptime. Same signature — no kernel trace, no pstore, system fully healthy until the last atop sample 50s before death.

Since I don't use iSCSI at all, is there a safe, supported way to disable the scst / iscsi_scst out-of-tree modules so they don't load at boot? If these modules are the suspected cause of the VMA/memory corruption, disabling them entirely would be a useful test for those of us who don't need iSCSI.

Has the engineering team confirmed whether the scst modules can be blacklisted without breaking TOS?
Thank you

[CursaYang]

Could you please send me a private message (PM) with the email address you used to submit the report? This will help us quickly locate your logs and follow up on your case.

[CursaYang]

The email has been resent; please check for it.

[exqo]

Has there been a definitive resolution to this issue? I am still having the same issue every few days with my F4-424 Max. I just submitted debug logs today.

On my side,aAfter several exchanges with the support team, including testing a few beta kernel builds to try to pin down the root cause, we weren't able to resolve it on the F4-424 itself.
In the end, I requested a machine exchange rather than continuing to troubleshoot indefinitely.

I returned the F4-424 and have been running a F4-425 Plus (N95) since yesterday. Migration went smoothly (same drives, same data, containers all came back up fine), so fingers crossed the issue doesn't show up again on the new unit. I'll report back here if anything comes up.

A detailed positive experience is available here about the exchange: viewtopic.php?p=60220#p60220

[NavinKanus]

TM team, I have the exact same issue on my F4-424. It used to happen every other week before TOS 7 now it happens everyday. I cannot keep using my TNAS like this. Has there been any solution to this problem at all?

[CursaYang]

TM team, I have the exact same issue on my F4-424. It used to happen every other week before TOS 7 now it happens everyday. I cannot keep using my TNAS like this. Has there been any solution to this problem at all?

We sincerely apologize for the inconvenience this has caused you.

Please enable Debug mode. If the issue occurs again, wait until the device restarts, then download the debug logs and send them to our technical support email address [support(at)terra-master.com]. Please also include a link to this forum post in the body of your email.

If possible, please note down the exact timestamp when the issue occurs, as this will be of great help to our troubleshooting process.

The debug logs consist of three files: kern.log, syslog, and atop_log. Please check if the download is blocked by your browser when retrieving these files.