TerraMaster Forum

Posted: **01 Aug 2025, 00:53**

I have an F*SSDPLUS with 4x 4tb ssds that have previously been in other devices with out issue.
I placed then in my new F8 (6 months ago) and they perform well except for any one of them disconnecting randomly once a month. The device starts beeping and I silence the buzzer. I then reboot the drive and it finds the drive and starts validating the index.

actual message says.
"the array in storage pool 1 has been degraded: disk NVMe Disk3 has failed or detached from the array. ....."

sometimes it says disk2.... others disk 1.

The first time it did this I removed, cleaned with alcohol wipes and reseated the modules.
The modules are never really hot...118F at max.. in an 75F room.

Could this be an intermittent connection problem between the board and the m2 connector?
Has anyone else had a similar problem?

Posted: **01 Aug 2025, 09:14**

Hi.
Your guess is possible.
However, we should not rule out the possibility that the temperature may have been too high at the moment it happened. Did you add the heat sinks that came with the package?
If the problem occurs again, please generate and download the system report package in TOS Desktop > Technical Support > Report Issues, and then send it to us for inspection, before shutting down the NAS. This will allow us to accurately identify the problem.
We will provide solutions or after-sales service based on the results.

Posted: **09 Aug 2025, 05:30**

the unit does not report 1.4 memory modules temp correctly. 1.3 reports correctly. I think the auto fan logic stays low as the memory gets hot since it is reporting 118F no matter what. turned fan on high.... problem went away.

Posted: **10 Aug 2025, 15:28**

This behavior is unusual — 118°F (47.8°C) isn't considered a high-risk temperature threshold.

Posted: **07 Sep 2025, 18:13**

i am still having disconnect issues with this device. i was able to get the log file dump during the last episode and would like to know how to send it in for evaluation. currently all m2's have heatsinks paste bonded to them. I have ran the device without cover to monitor temperature. 135F is the highest temp I have recorded with a IR temp gun. I believe the unit is suffering from a poorly soldered m2 sockets. What is the process to have the unit replaced?

Posted: **11 Sep 2025, 15:20**

you did not mentioned what kind of m.2 SSD you installed in your nas. If you sure your nas device is defeative, we can provide you RMA service. BUT before doing this, please make sure the installation is well seat your SSD, and SSD is compatible, also try to a different socket.

Posted: **13 Sep 2025, 20:25**

I just came here to post the exact same problem for my F8 SSD (not Plus) and found this post.

August 23rd, a WD RED 1TB in slot 7 went offline:

Code: Select all

[Sat Aug 23 18:42:01 2025] nvme nvme0: I/O 334 (I/O Cmd) QID 4 timeout, aborting
[Sat Aug 23 18:42:01 2025] nvme nvme0: I/O 335 (I/O Cmd) QID 4 timeout, aborting
[Sat Aug 23 18:42:01 2025] nvme nvme0: I/O 336 (I/O Cmd) QID 4 timeout, aborting
[Sat Aug 23 18:42:01 2025] nvme nvme0: I/O 337 (I/O Cmd) QID 4 timeout, aborting
[Sat Aug 23 18:42:01 2025] nvme nvme0: I/O 338 (I/O Cmd) QID 4 timeout, aborting
[Sat Aug 23 18:42:31 2025] nvme nvme0: I/O 334 QID 4 timeout, reset controller
[Sat Aug 23 18:42:34 2025] nvme nvme0: I/O 9 QID 0 timeout, reset controller
[Sat Aug 23 18:43:44 2025] nvme nvme0: Device not ready; aborting reset, CSTS=0x1
[Sat Aug 23 18:43:44 2025] sdza: I/O Cmd(0x2) @ LBA 404237440, 144 blocks, I/O Error (sct 0x3 / sc 0x71)
[Sat Aug 23 18:43:44 2025] I/O error, dev sdza, sector 404237440 op 0x0:(READ) flags 0x80700 phys_seg 11 prio class 2
[Sat Aug 23 18:43:44 2025] sdza: I/O Cmd(0x2) @ LBA 404237592, 104 blocks, I/O Error (sct 0x3 / sc 0x71)
[Sat Aug 23 18:43:44 2025] I/O error, dev sdza, sector 404237592 op 0x0:(READ) flags 0x80700 phys_seg 7 prio class 2
[Sat Aug 23 18:43:44 2025] sdza: I/O Cmd(0x2) @ LBA 404238208, 128 blocks, I/O Error (sct 0x3 / sc 0x71)
[Sat Aug 23 18:43:44 2025] I/O error, dev sdza, sector 404238208 op 0x0:(READ) flags 0x80700 phys_seg 8 prio class 2
[Sat Aug 23 18:43:44 2025] sdza: I/O Cmd(0x2) @ LBA 404238464, 256 blocks, I/O Error (sct 0x3 / sc 0x71)
[Sat Aug 23 18:43:44 2025] I/O error, dev sdza, sector 404238464 op 0x0:(READ) flags 0x80700 phys_seg 16 prio class 2
[Sat Aug 23 18:43:44 2025] sdza: I/O Cmd(0x2) @ LBA 404237824, 384 blocks, I/O Error (sct 0x3 / sc 0x71)
[Sat Aug 23 18:43:44 2025] I/O error, dev sdza, sector 404237824 op 0x0:(READ) flags 0x80700 phys_seg 24 prio class 2
[Sat Aug 23 18:43:44 2025] sdza: I/O Cmd(0x2) @ LBA 404239328, 112 blocks, I/O Error (sct 0x3 / sc 0x71)
[Sat Aug 23 18:43:44 2025] I/O error, dev sdza, sector 404239328 op 0x0:(READ) flags 0x80700 phys_seg 7 prio class 2
[Sat Aug 23 18:43:44 2025] sdza: I/O Cmd(0x2) @ LBA 404238720, 256 blocks, I/O Error (sct 0x3 / sc 0x71)
[Sat Aug 23 18:43:44 2025] I/O error, dev sdza, sector 404238720 op 0x0:(READ) flags 0x80700 phys_seg 16 prio class 2
[Sat Aug 23 18:43:44 2025] sdza: I/O Cmd(0x2) @ LBA 404239104, 224 blocks, I/O Error (sct 0x3 / sc 0x71)
[Sat Aug 23 18:43:44 2025] I/O error, dev sdza, sector 404239104 op 0x0:(READ) flags 0x80700 phys_seg 14 prio class 2
[Sat Aug 23 18:43:44 2025] sdza: I/O Cmd(0x2) @ LBA 404235392, 384 blocks, I/O Error (sct 0x3 / sc 0x71)
[Sat Aug 23 18:43:44 2025] I/O error, dev sdza, sector 404235392 op 0x0:(READ) flags 0x80700 phys_seg 47 prio class 2
[Sat Aug 23 18:43:44 2025] sdza: I/O Cmd(0x2) @ LBA 404235904, 384 blocks, I/O Error (sct 0x3 / sc 0x71)
[Sat Aug 23 18:43:44 2025] I/O error, dev sdza, sector 404235904 op 0x0:(READ) flags 0x80700 phys_seg 48 prio class 2
[Sat Aug 23 18:43:44 2025] nvme nvme0: Abort status: 0x371
[Sat Aug 23 18:43:44 2025] nvme nvme0: Abort status: 0x371
[Sat Aug 23 18:43:44 2025] nvme nvme0: Abort status: 0x371
[Sat Aug 23 18:43:44 2025] nvme nvme0: Abort status: 0x371
[Sat Aug 23 18:43:44 2025] nvme nvme0: Abort status: 0x371
[Sat Aug 23 18:44:06 2025] nvme nvme0: Device not ready; aborting reset, CSTS=0x1
[Sat Aug 23 18:44:06 2025] nvme nvme0: Removing after probe failure status: -19
[Sat Aug 23 18:44:29 2025] nvme nvme0: Device not ready; aborting reset, CSTS=0x1
[Sat Aug 23 18:44:29 2025] sdza: detected capacity change from 1953525168 to 0
[Sat Aug 23 18:44:29 2025] md: super_written gets error=-5
[Sat Aug 23 18:44:29 2025] md/raid:md0: Disk failure on sdza4, disabling device.
[Sat Aug 23 18:44:29 2025] md/raid:md0: Operation continuing on 4 devices.

Today, a brand new Samsung 990 Pro 2TB in slot 2 went offline:

Code: Select all

[1467682.857543] nvme nvme3: I/O 438 (I/O Cmd) QID 4 timeout, aborting
[1467712.041542] nvme nvme3: I/O 8 QID 0 timeout, reset controller
[1467713.065542] nvme nvme3: I/O 459 (I/O Cmd) QID 2 timeout, aborting
[1467713.065578] nvme nvme3: I/O 438 QID 4 timeout, reset controller
[1467794.488889] nvme nvme3: Device not ready; aborting reset, CSTS=0x1
[1467794.494709] nvme nvme3: Abort status: 0x371
[1467794.494712] nvme nvme3: Abort status: 0x371
[1467815.007821] nvme nvme3: Device not ready; aborting reset, CSTS=0x1
[1467815.007835] nvme nvme3: Removing after probe failure status: -19
[1467835.515566] nvme nvme3: Device not ready; aborting reset, CSTS=0x1
[1467835.515730] sdzd: detected capacity change from 3907029168 to 0
[1467835.515736] md/raid1:md8: sdzd3: rescheduling sector 3988960
[1467835.515776] md: super_written gets error=-5
[1467835.515782] md/raid1:md9: Disk failure on sdzd2, disabling device.
                 md/raid1:md9: Operation continuing on 1 devices.
[1467835.515806] md/raid1:md9: sdzd2: rescheduling sector 2120384
[1467835.525328] md/raid1:md8: redirecting sector 3988960 to other mirror: sdzc3
[1467835.525340] md: super_written gets error=-5
[1467835.525350] md/raid1:md8: Disk failure on sdzd3, disabling device.
                 md/raid1:md8: Operation continuing on 1 devices.
[1467835.539718] md/raid1:md9: redirecting sector 2120384 to other mirror: sdzc2
[1467835.741619] md/raid:md0: Disk failure on sdzd4, disabling device.
[1467835.741628] md/raid:md0: Operation continuing on 4 devices.
[1467835.742291] md/raid:md1: Disk failure on sdzd5, disabling device.
[1467835.742299] md/raid:md1: Operation continuing on 2 devices.

Each time, shutting down the NAS (reboot does not help) and turning it on again, it came up 100% fine and rebuild the RAID.
The first time I still had 16GB Crucial in, immediately went back to the original RAM. But now I am seeing that was not the problem.

My NAS is cooled perfectly well was and under no load when it happened.

I have also updated the BIOS and firmware when I found the new version a few weeks ago.

NVMes were all reseated after the first incident, and the heat sink is installed on each of them.

Please help!

Posted: **13 Sep 2025, 20:33**

Firmware:

Code: Select all

# ./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

BIOS / OS:

Posted: **13 Sep 2025, 22:25**

athurdent wrote: ↑13 Sep 2025, 20:33

If RMA service is required, please provide the following information and send it to the email address: [email protected]:
Product Serial Number (SN)
Product order invoice details
Shipping address (for return/delivery)
Contact phone number

Posted: **13 Sep 2025, 23:11**

ColaChen wrote: ↑13 Sep 2025, 22:25
athurdent wrote: ↑13 Sep 2025, 20:33
If RMA service is required, please provide the following information and send it to the email address: [email protected]:
Product Serial Number (SN)
Product order invoice details
Shipping address (for return/delivery)
Contact phone number

OK, filed the RMA as requested.
So, this is a known issue with these devices then?
I guess I am going to get a revised motherboard for RMA?
It's odd, because the device is very new (bought it August 3rd).
Thanks!

TerraMaster Forum

[Discussion] F8 SSD Plus m2 drive disconnecting erratically

[Discussion] F8 SSD Plus m2 drive disconnecting erratically

Re: [Discussion] F8 SSD Plus m2 drive disconnecting erratically

Re: [Discussion] F8 SSD Plus m2 drive disconnecting erratically

Re: [Discussion] F8 SSD Plus m2 drive disconnecting erratically

Re: [Discussion] F8 SSD Plus m2 drive disconnecting erratically

Re: [Discussion] F8 SSD Plus m2 drive disconnecting erratically

Re: [Discussion] F8 SSD Plus m2 drive disconnecting erratically

Re: [Discussion] F8 SSD Plus m2 drive disconnecting erratically

Re: [Discussion] F8 SSD Plus m2 drive disconnecting erratically

Re: [Discussion] F8 SSD Plus m2 drive disconnecting erratically