TerraMaster Forum

rafaqs wrote: ↑12 Apr 2026, 22:29 Hi TMzethar,

Thank you very much for providing such a detailed guide. I truly appreciate the team's commitment and effort to help me resolve this. It's great to see this level of technical support.

I will proceed with all the steps you mentioned—including the CMOS reset, using the original RAM module, and isolating the motherboard—and I will record the entire process as requested to provide the necessary evidence.

Regarding the files (videos and photos), what is the best way to share them with you? Would it be okay if I post a Google Drive link directly here in the forum? Or would you prefer me to send them via email? If so, please let me know which address I should use.

I’ll get back to you with the results very soon (it's going to be another long day here!).

Thanks again for your dedication!

Thank you for your understanding and support. You can upload the video to Google Drive and then send the sharing link to our technical support email ([email protected]), and we will analyze it.

Hi everyone, especially the support team and @TMzethar,

I wanted to provide a final update and express my immense gratitude for all the assistance. I took a couple of days to respond because I wanted to be 100% sure that the system was stable before declaring success.

After a long and challenging troubleshooting process, the 'miracle' solution was indeed a deep CMOS reset. Removing the motherboard battery for about 10-15 minutes finally forced the hardware to 'wake up'.

I can't describe how happy I was when I ran the terminal command and finally saw the system recognizing both controllers after they had been 'missing' for so long. Here is the output that confirmed the fix:

root@Nas1:~# lspci | grep -i ethernet
03:00.0 Ethernet controller: Aquantia Corp. AQC113C NBase-T/IEEE 802.3an Ethernet Controller [Marvell Scalable mGig] (rev 03)
04:00.0 Ethernet controller: Aquantia Corp. AQC113C NBase-T/IEEE 802.3an Ethernet Controller [Marvell Scalable mGig] (rev 03)

Seeing those two lines instead of just one was the definitive proof that the hardware was back. I have been stress-testing the unit for over 48 hours now under Unraid, and both interfaces are rock solid, negotiating correct speeds (10GbE and 2.5GbE in my current setup) and maintaining healthy temperatures.

This journey, although difficult, actually reinforced my confidence in the brand. Seeing the hardware respond to a deep reset and perform so well after it came back to life proves I made the right choice with TerraMaster. I’m very happy with my F6-424 Max and I hope to enjoy this performance for many years to come!

Thank you again for not giving up on my case!

rafaqs wrote: ↑15 Apr 2026, 02:58 …

After a long and challenging troubleshooting process, the 'miracle' solution was indeed a deep CMOS reset. Removing the motherboard battery for about 10-15 minutes finally forced the hardware to 'wake up'.

…

So did TrueNAS or UNRAID manipulate UEFI to cause this issue, as that's what generally differs from any user with this TNAS running TOS not experiencing this disappearing NIC consequence?

Or could it be a poorly written open source driver with either of those, resulting in this problem under UEFI?

rafaqs wrote: ↑15 Apr 2026, 02:58 After a long and challenging troubleshooting process, the 'miracle' solution was indeed a deep CMOS reset. Removing the motherboard battery for about 10-15 minutes finally forced the hardware to 'wake up'.

Glad to hear the good news.
Perhaps the network card was disabled in the BIOS settings. Do you recall doing anything that might have caused this?

TMzethar wrote: ↑15 Apr 2026, 16:16

rafaqs wrote: ↑15 Apr 2026, 02:58 After a long and challenging troubleshooting process, the 'miracle' solution was indeed a deep CMOS reset. Removing the motherboard battery for about 10-15 minutes finally forced the hardware to 'wake up'.

Glad to hear the good news.
Perhaps the network card was disabled in the BIOS settings. Do you recall doing anything that might have caused this?

Hi, I'm sure that's not the case. I've looked at that screen in the BIOS dozens of times. Even right before removing the motherboard battery, both were active and only one worked when reinstalling TOS7 (for the third time). Again, thank you very much for your support

how to find mb battery on f6424?

jvenard wrote: ↑26 Apr 2026, 02:08

Power off the device, remove its casing, unscrew the screws on the back of the unit, then take out the main board and you will see the battery.