F4-424 Pro Not Recognizing HDD

[jdj211]

Hello,
I just got my new F4-424 Pro. I installed one 1TB NVME SSD to host the OS and apps, and four 18TB HDD. However the NAS fails to recognize the HDD, it will only see the NVME SSD. The unit beeps when they are in, but all 4 lights are solid green. I have confirmed that the ST18000NE000 are on the compatibility list. Are there any suggestions for troubleshooting steps? I am unsure if the HDD are defective, the NAS is defective, or if there is a compatibility issue. I don’t want to try replacing one of these units if it is not at fault. I only have mini PCs at the moment, and they don’t support a 3.5” drive for testing that way.

[Gremlin]

Which Tos version was installed? Were the HDD in the device when Tos was installed?

[jdj211]

I grabbed the latest from the download page this morning. It asked for the bootloader and I used version 5.1.48 and then 5.1.145 for TOS. Yes the drives were in before I first powered it on. I still haven’t completed the install at this point since I didn’t want to add the NVME to the storage pool and that is the only available drive in that selection.

[TMnick]

I grabbed the latest from the download page this morning. It asked for the bootloader and I used version 5.1.48 and then 5.1.145 for TOS. Yes the drives were in before I first powered it on. I still haven’t completed the install at this point since I didn’t want to add the NVME to the storage pool and that is the only available drive in that selection.

Hello, based on your description, we infer that there may be two potential causes: 1. There is an issue with your hard drive, and while other methods are needed to detect whether there are problems with the hard drive, it seems your current conditions do not permit it (you only have mini PCs at the moment, and they don't support a 3.5” drive for such testing). 2. There could be an issue with the backplane of the device, although this probability is quite low. Do you have other models of hard drives? If so, you can try to see if they can be recognized.
Next, we will also re-verify this hard drive model, and we will notify you at the first opportunity once we have results. We apologize for any inconvenience caused to you.

[TMnick]

Hello,
I just got my new F4-424 Pro. I installed one 1TB NVME SSD to host the OS and apps, and four 18TB HDD. However the NAS fails to recognize the HDD, it will only see the NVME SSD. The unit beeps when they are in, but all 4 lights are solid green. I have confirmed that the ST18000NE000 are on the compatibility list. Are there any suggestions for troubleshooting steps? I am unsure if the HDD are defective, the NAS is defective, or if there is a compatibility issue. I don’t want to try replacing one of these units if it is not at fault. I only have mini PCs at the moment, and they don’t support a 3.5” drive for testing that way.

Have you already installed the operating system on an SSD? If so, you can use an SSH tool to log in to the terminal and input the following commands to check the recognition status of the HDD.
dmesg | grep ata
ls /dev/sd*
ls -ail /sys/block/sd*
The default login credentials are root for the username and admin for the password.

[jdj211]

I grabbed the latest from the download page this morning. It asked for the bootloader and I used version 5.1.48 and then 5.1.145 for TOS. Yes the drives were in before I first powered it on. I still haven’t completed the install at this point since I didn’t want to add the NVME to the storage pool and that is the only available drive in that selection.

Hello, based on your description, we infer that there may be two potential causes: 1. There is an issue with your hard drive, and while other methods are needed to detect whether there are problems with the hard drive, it seems your current conditions do not permit it (you only have mini PCs at the moment, and they don't support a 3.5” drive for such testing). 2. There could be an issue with the backplane of the device, although this probability is quite low. Do you have other models of hard drives? If so, you can try to see if they can be recognized.
Next, we will also re-verify this hard drive model, and we will notify you at the first opportunity once we have results. We apologize for any inconvenience caused to you.

I now have a SATA to USB converter, so I can test the drive independently from the NAS. If you have a suggested test to perform, please let me know.

[jdj211]

Hello,
I just got my new F4-424 Pro. I installed one 1TB NVME SSD to host the OS and apps, and four 18TB HDD. However the NAS fails to recognize the HDD, it will only see the NVME SSD. The unit beeps when they are in, but all 4 lights are solid green. I have confirmed that the ST18000NE000 are on the compatibility list. Are there any suggestions for troubleshooting steps? I am unsure if the HDD are defective, the NAS is defective, or if there is a compatibility issue. I don’t want to try replacing one of these units if it is not at fault. I only have mini PCs at the moment, and they don’t support a 3.5” drive for testing that way.

Have you already installed the operating system on an SSD? If so, you can use an SSH tool to log in to the terminal and input the following commands to check the recognition status of the HDD.
dmesg | grep ata
ls /dev/sd*
ls -ail /sys/block/sd*
The default login credentials are root for the username and admin for the password.

Please see the command responses below:

Welcome to TNAS!
[jdj211@TNAS-FEB8 ~]# dmesg | grep ata
[ 0.000000] BIOS-e820: [mem 0x0000000073144000-0x0000000073210fff] ACPI data
[ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000009dfff] usable
[ 0.000000] reserve setup_data: [mem 0x000000000009e000-0x000000000009efff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] usable
[ 0.000000] reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x00000000426fcfff] usable
[ 0.000000] reserve setup_data: [mem 0x00000000426fd000-0x00000000426fdfff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000426fe000-0x0000000043140fff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000043141000-0x0000000043141fff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000043142000-0x000000006bdb0017] usable
[ 0.000000] reserve setup_data: [mem 0x000000006bdb0018-0x000000006bdb9457] usable
[ 0.000000] reserve setup_data: [mem 0x000000006bdb9458-0x0000000070043fff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000070044000-0x0000000073143fff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000073144000-0x0000000073210fff] ACPI data
[ 0.000000] reserve setup_data: [mem 0x0000000073211000-0x00000000732d0fff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x00000000732d1000-0x0000000073efefff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000073eff000-0x0000000073efffff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000073f00000-0x0000000079ffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000007aa00000-0x000000007abfffff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000007b000000-0x00000000803fffff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000100000000-0x000000047fbfffff] usable
[ 0.089531] Memory: 15944348K/16510852K available (20499K kernel code, 4115K rwdata, 6788K rodata, 45008K init, 3592K bss, 566244K reserved, 0K cma-reserved)
[ 0.095087] Spectre V2 : WARNING: Unprivileged eBPF is enabled with eIBRS on, data leaks possible via Spectre v2 BHB attacks!
[ 0.371421] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
[ 0.371431] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
[ 0.436758] libata version 3.00 loaded.
[ 0.616370] ata1: SATA max UDMA/133 abar m2048@0x80802000 port 0x80802100 irq 126
[ 0.616373] ata2: SATA max UDMA/133 abar m2048@0x80802000 port 0x80802180 irq 126
[ 0.616764] ata3: SATA max UDMA/133 abar m512@0x80510000 port 0x80510100 irq 127
[ 0.616767] ata4: SATA max UDMA/133 abar m512@0x80510000 port 0x80510180 irq 127
[ 0.922220] ata1: SATA link down (SStatus 0 SControl 300)
[ 0.922225] ata3: SATA link down (SStatus 0 SControl 300)
[ 0.922242] ata2: SATA link down (SStatus 0 SControl 300)
[ 1.148410] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 1.234328] ata4: SATA link down (SStatus 0 SControl 300)
[ 1.243058] Write protecting the kernel read-only data: 30720k
[ 1.243405] Freeing unused kernel image (text/rodata gap) memory: 2028K
[ 1.243599] Freeing unused kernel image (rodata/data gap) memory: 1404K
[ 1.283572] EXT4-fs (md9): mounted filesystem with ordered data mode. Opts: commit=5,data=ordered. Quota mode: none.
[ 109.307089] ata1: link is slow to respond, please be patient (ready=0)
[ 113.571090] ata1: COMRESET failed (errno=-16)
[ 119.338089] ata1: link is slow to respond, please be patient (ready=0)
[ 123.602089] ata1: COMRESET failed (errno=-16)
[ 129.370086] ata1: link is slow to respond, please be patient (ready=0)
[ 158.648087] ata1: COMRESET failed (errno=-16)
[ 158.648109] ata1: limiting SATA link speed to 3.0 Gbps
[ 163.490087] ata2: link is slow to respond, please be patient (ready=0)
[ 163.682087] ata1: COMRESET failed (errno=-16)
[ 163.682098] ata1: reset failed, giving up
[ 167.755086] ata2: COMRESET failed (errno=-16)
[ 170.743450] ata3: softreset failed (1st FIS failed)
[ 173.524086] ata2: link is slow to respond, please be patient (ready=0)
[ 175.319293] ata4: softreset failed (1st FIS failed)
[ 177.789091] ata2: COMRESET failed (errno=-16)
[ 180.743217] ata3: softreset failed (1st FIS failed)
[ 183.555084] ata2: link is slow to respond, please be patient (ready=0)
[ 185.319521] ata4: softreset failed (1st FIS failed)
[ 212.840085] ata2: COMRESET failed (errno=-16)
[ 212.840106] ata2: limiting SATA link speed to 3.0 Gbps
[ 215.743101] ata3: softreset failed (1st FIS failed)
[ 215.743110] ata3: limiting SATA link speed to 3.0 Gbps
[ 217.875084] ata2: COMRESET failed (errno=-16)
[ 217.875106] ata2: reset failed, giving up
[ 220.319852] ata4: softreset failed (1st FIS failed)
[ 220.319861] ata4: limiting SATA link speed to 3.0 Gbps
[ 220.933094] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 220.933104] ata3.00: link online but device misclassified
[ 220.933106] ata3: link online but 1 devices misclassified, device detection might fail
[ 225.509095] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
[ 225.509115] ata4.00: link online but device misclassified
[ 225.509116] ata4: link online but 1 devices misclassified, device detection might fail
[31692.116482] ata1: SATA link down (SStatus 0 SControl 300)
[31801.656465] ata1: link is slow to respond, please be patient (ready=0)
[31805.921464] ata1: COMRESET failed (errno=-16)
[31811.688463] ata1: link is slow to respond, please be patient (ready=0)
[31815.952463] ata1: COMRESET failed (errno=-16)
[31821.720463] ata1: link is slow to respond, please be patient (ready=0)
[31850.997463] ata1: COMRESET failed (errno=-16)
[31850.997484] ata1: limiting SATA link speed to 3.0 Gbps
[31856.032462] ata1: COMRESET failed (errno=-16)
[31856.032482] ata1: reset failed, giving up
[72521.557477] BTRFS info (device dm-0): flagging fs with big metadata feature

[jdj211@TNAS-FEB8 ~]# ls /dev/sd*
/dev/sdza /dev/sdza1 /dev/sdza2 /dev/sdza3 /dev/sdza4

[jdj211@TNAS-FEB8 ~]# ls -ail /sys/block/sd*
26935 lrwxrwxrwx 1 jdj211 jdj211 0 Nov 30 18:13 /sys/block/sdza -> ../devices/pci0000:00/0000:00:1d.0/0000:04:00.0/nvme/nvme0/sdza

[jdj211]

I am searching online for similar issues with drives not being recognized and I am seeing discussion about 3.3V power disable pins. Does the TerraMaster SATA connector support this feature? I would assume it is compatible with my HDD since it is explicitly on the compatibility list (ST18000NE000)

[Gremlin]

The dmesg output looks bad to me. Too many COMRESET and Sata Link speed is off (3Gbps instead of 6Gbps) where it is shown.
Maybe bad contact(s) between drives and backplane. You could try removing all the hdd and (if possible & able) clean the connectors. Re-insert one drive and test again. (change drives with system off.)

[Gremlin]

FYI:
Output from a working Tos5.1.145 system: (on F5-221, no nvme)

Code: Select all

Prompt#: dmesg | grep "ata"
[    0.149275] Memory: 9981976K/10328788K available (20499K kernel code, 4115K rwdata, 6788K rodata, 45008K init, 3592K bss, 346552K reserved, 0K cma-reserved)
[    0.350976] libata version 3.00 loaded.
[    0.943450] ata1: SATA max UDMA/133 abar m2048@0x91417000 port 0x91417100 irq 124
[    0.943547] ata2: SATA max UDMA/133 abar m2048@0x91417000 port 0x91417180 irq 124
[    0.956224] ata3: SATA max UDMA/133 abar m512@0x91200000 port 0x91200100 irq 125
[    0.956318] ata4: SATA max UDMA/133 abar m512@0x91200000 port 0x91200180 irq 125
[    0.963044] ata5: SATA max UDMA/133 abar m512@0x91100000 port 0x91100100 irq 126
[    0.963139] ata6: SATA max UDMA/133 abar m512@0x91100000 port 0x91100180 irq 126
[    1.275835] ata5: SATA link down (SStatus 0 SControl 300)
[    1.413698] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.413814] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.415981] ata2.00: ATA-10: ST4000VN006-3CW104, SC60, max UDMA/133
[    1.416082] ata1.00: ATA-10: ST4000VN006-3CW104, SC60, max UDMA/133
[    1.416177] ata2.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.416271] ata1.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.418126] ata2.00: configured for UDMA/133
[    1.418238] ata1.00: configured for UDMA/133
[    1.421619] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.423734] ata3.00: ATA-10: ST4000VN006-3CW104, SC60, max UDMA/133
[    1.423904] ata3.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.425690] ata3.00: configured for UDMA/133
[    1.569689] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    1.893839] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.895981] ata4.00: ATA-8: Hitachi HDS723030ALA640, MKAOAA10, max UDMA/133
[    1.896785] ata4.00: ATA Identify Device Log not supported
[    1.896894] ata4.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 32), AA
[    1.899662] ata4.00: ATA Identify Device Log not supported
[    1.899781] ata4.00: configured for UDMA/133
[    2.212912] ata6: SATA link down (SStatus 0 SControl 300)
[    2.232349] Write protecting the kernel read-only data: 30720k
[    2.234116] Freeing unused kernel image (text/rodata gap) memory: 2028K
[    2.235090] Freeing unused kernel image (rodata/data gap) memory: 1404K
[    2.780434] EXT4-fs (md9): mounted filesystem with ordered data mode. Opts: commit=5,data=ordered. Quota mode: none.
[   76.469797] BTRFS info (device dm-0): flagging fs with big metadata feature
[   93.195044] BTRFS info (device dm-1): flagging fs with big metadata feature
[  102.560328] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: data=ordered,user_xattr,acl,usrjquota=quota.user,grpjquota=quota.group,jqfmt=vfsv1. Quota mode: journalled.

3 HDD are Ironwolf. 1 HDD is Hitachi. Slot 5 is empty