How to Resolve the Issue of F8 SSD Failing to Boot or Automatically Restarting After Installing a 3rd Party OS or TOS7

[kuenka123]

Exactly: ever since I tried to update the BIOS, I don't hear any beeps when booting up. In fact, I tried reseating the RAM yesterday; in one of my attempts, it wasn't plugged in properly and it did emit a series of repetitive beeps indicating an error, so the speaker definitely works .

I also tried removing and reinstalling the CMOS battery without success: when I try to boot it up again, there’s no beep, the screen doesn’t turn on (no HDMI signal), and there isn’t even power reaching the keyboard (for instance, the lights don't come on when pressing Caps Lock). I’ve already tested the monitor and keyboard on other devices and they work perfectly, just to rule that out and keep my sanity.

I’m afraid I’m running out of ideas. By the way, when I removed the battery, I tried booting with both the original USB and the one with the BIOS update, but nothing—neither of them works.

[CursaYang]

During the update process, did you experience any terminal or power failures? Based on your description, it seems that the device has become bricked. That is, the device cannot boot, there are no beeping sounds, no display output, and even the keyboard is unresponsive (as you described). Please send your purchase order information to our technical support email ([email protected]) and include the link to this post.

[kuenka123]

First of all, thank you so much for your help, Cursa.

As far as I know, I didn't experience any power surges or outages when I first attempted to update the firmware. In fact, as I mentioned before, I only tried the update because TerraMaster support suggested it as a potential fix for the NVMe drive disconnections—an issue I already had with a previous unit and was starting to experience again with this one.

I’ve been sending them follow-up emails for a few weeks now, but I will reach out again mentioning your advice and attaching the proof of purchase (invoice) to see how we can resolve this. I really want to get this sorted because the F8 SSD Plus is an amazing NAS when it's working properly, and I really rely on it for my work.

Thanks again for your support!

[TMzethar]

Before performing any operations on hardware, have you disconnected the power and taken anti-static precautions? If you have spare RAM modules of the same specifications (DDR5 non-ECC SODIMM), you can try replacing them for testing. Considering that both of your F8 SSD Plus units have experienced disk disconnection in Slot1, along with the previous issue of becoming bricked after a firmware update, we believe there is likely a specific cause that has adversely affected the F8 SSD Plus.

[kuenka123]

I’m afraid I don’t have another memory module to test. However, since the device beeps when the module is correctly inserted but does not beep when it isn't, I have the impression that the RAM is not the issue.
​Regarding the disk disconnection problems: I began performing these tests after asking support if the second unit I received was different from the first one (since I was experiencing the same issues), but I never received a response to that question. Regardless, to answer your other question about whether I tried swapping the disks: yes, I did, and I consistently experienced random disconnections in that specific slot.
​As for the power disconnection precautions before handling the RAM or disks, I have strictly followed them: I always work with the NAS unplugged from the power source and allow it to sit for a period of time before operating on it.
​Do you have any suggestions on how to proceed?

Thank you very much!

[CursaYang]

Hello, we have seen your email. We will arrange for a business colleague to follow up on this matter subsequently.

[tonzurakoite]

Are the referenced download links still the most recent BIOS images that I should use to try and address this issue? My F8 SSD Plus randomly crashes and reboots daily or sometimes more frequently, and based on the errors it looks like it's the same or similar BIOS issue. My system info and error log:

Hardware Model: F8 SSD Plus
TOS Version: 6.0.794-01324

/var/log# dmesg -T | grep -i error
[Thu Jan 29 03:16:46 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.TXHC.RHUB.SS01], AE_NOT_FOUND (20220331/dswload2-162)
[Thu Jan 29 03:16:46 2026] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
[Thu Jan 29 03:16:46 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.TXHC.RHUB.SS02], AE_NOT_FOUND (20220331/dswload2-162)
[Thu Jan 29 03:16:46 2026] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
[Thu Jan 29 03:16:46 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Thu Jan 29 03:16:46 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Thu Jan 29 03:16:46 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Thu Jan 29 03:16:46 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS02._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Thu Jan 29 03:16:46 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Thu Jan 29 03:16:46 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Thu Jan 29 03:16:46 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Thu Jan 29 03:16:46 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Thu Jan 29 03:16:46 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Thu Jan 29 03:16:46 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS02._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Thu Jan 29 03:16:46 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Thu Jan 29 03:16:46 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS02._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Thu Jan 29 03:16:46 2026] evm: Error registering secfs
[Thu Jan 29 03:16:46 2026] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[Thu Jan 29 03:16:46 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Thu Jan 29 03:16:46 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Thu Jan 29 03:16:46 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Thu Jan 29 03:16:46 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)

[TMzethar]

According to your description, it fits the situation mentioned on the first page.
You can try updating the firmware.

[tonzurakoite]

According to your description, it fits the situation mentioned on the first page.
You can try updating the firmware.

Hi there, I've updated the BIOS and confirmed the firmware is already up-to-date but this has not resolved my issue. The TNAS F8 SSD Plus still unexpectedly reboots 1 - 2 times a day (it's been doing this since I purchased it). In looking through other troubleshooting threads I've also disabled the VT-d setting in the BIOS but it's still rebooting. Help please.

- - - - - 8< - - - - -

Firmware info:
cd /Volume1/public/
chmod 755 218xfwdl
fuzzydustin@GilgaNAS:/Volume1/public# ./218xfwdl /s
Asmedia PCIe Gen3 Switch SPI ROM Update Linux Utility - Version 1.7.4.0
Found 1 Asmedia PCIe Gen3 Switch Upstream Port
[04:00.0] PCIe Switch 0: 24 08 21 40 00 00

Error info:
dmesg -T | grep -i error
[Sat Feb 7 00:07:29 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.TXHC.RHUB.SS01], AE_NOT_FOUND (20220331/dswload2-162)
[Sat Feb 7 00:07:29 2026] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
[Sat Feb 7 00:07:29 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.TXHC.RHUB.SS02], AE_NOT_FOUND (20220331/dswload2-162)
[Sat Feb 7 00:07:29 2026] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20220331/psobject-220)
[Sat Feb 7 00:07:29 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Sat Feb 7 00:07:29 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Sat Feb 7 00:07:29 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Sat Feb 7 00:07:29 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS02._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Sat Feb 7 00:07:29 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Sat Feb 7 00:07:29 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Sat Feb 7 00:07:29 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Sat Feb 7 00:07:29 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Sat Feb 7 00:07:29 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Sat Feb 7 00:07:29 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS02._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Sat Feb 7 00:07:29 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Sat Feb 7 00:07:29 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS02._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Sat Feb 7 00:07:29 2026] evm: Error registering secfs
[Sat Feb 7 00:07:29 2026] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[Sat Feb 7 00:07:29 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Sat Feb 7 00:07:29 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[Sat Feb 7 00:07:29 2026] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.UBTC.RUCC], AE_NOT_FOUND (20220331/psargs-332)
[Sat Feb 7 00:07:29 2026] ACPI Error: Aborting method \_SB.PC00.XHCI.RHUB.HS01._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)

[TMjack]

Based on the information you provided, the PCIe HUB chip (ASM2806) used in the F8 SSD product is already the latest version. Previously, we received feedback from some users indicating that certain M.2 SSDs caused device crashes or automatic restarts due to their own quality issues. To accurately identify the problem, we recommend that you test each M.2 SSD individually to isolate the faulty one. Additionally, please provide the brand and model information of the related M.2 SSDs.