[Help] F4-210 NAS Fails to Boot with Multiple Independent Disks

[antocara]

Dear Terramaster Support,

I am experiencing a critical issue with my Terramaster F4-210 NAS. My configuration consists of 4 × 8TB HDDs, all independent.

The problem is as follows:

The NAS boots successfully with any single disk inserted.

When all the disks are inserted, the system emits the normal boot beep after about 30 min but then becomes completely unresponsive. I cannot access the web interface, SSL, or shared folders from my network. I have wait more than 24 hours, and all lthe hdd lights are green and cannot see any disk activity.

The issue occurs regardless of which combination of disks is inserted.

All disks have been tested individually and are in good health (SMART status is fine).

I have not made any modifications that could affect the disks or configuration.

Could you please advise:

How to safely troubleshoot this issue without risking data loss.

Whether there are known firmware updates or settings that could resolve this problem.

Any recommended steps to restore full functionality with all disks inserted.

Thank you very much for your prompt assistance.

Best regards,

[TMzethar]

Hi. Based on the available information, it is not yet sufficient to locate the problem.
We need to confirm this clearly.
You mentioned that a single arbitrary disk can be successfully booted, but would there be issues when booting with two or more disks?
Were all the disks inserted before powering on the NAS?

Please generate and download the system report package in TOS Desktop > Technical Support > Report Issues, then download and send it to our support team email for inspection.

Additionally, please log in to the terminal and execute the following command:

Code: Select all

dmesg -w >> /mnt/md0/public/dmesgw.log

How to log in Terminal: viewtopic.php?t=2350

Keep the terminal running to continuously record kernel information, and do not allow the PC/Mac to enter sleep mode as it may affect the operation. When encountering the problem again during the execution of this command, it may record relevant information.
Please download this file from the public directory and send it to our support team email when you next access TOS.

[antocara]

You mentioned that a single arbitrary disk can be successfully booted, but would there be issues when booting with two or more disks?

Did not tried with two or three disk. I tried to boot one disk only at time and it started ok with each disk but it was not working when starting with all disk inserted before power it on

Were all the disks inserted before powering on the NAS?

Yes of course but it did not started

Please generate and download the system report package in TOS Desktop

The report attached is with one disk inserted only at start. After system booting I have inserted the other three . Obviously the other three disk ar not seen by the system as far as file concernig because are not mounted automatically.

Please download this file from the public directory and send it to our support team email when you next access TOS.

Please see the log attached. The log have been started several hours after the system boot. Please let me know I I can do more to help with your diagnosis.
Regards

[TMzethar]

Regarding the dmesgw.log, you have not followed the requirements. You should keep it until 30 minutes after the abnormality (complete unresponsiveness) occurs, and then retrieve it upon the next startup.

Currently, you are running the system and storage on a single disk with 3 HDDs inserted. You can try opening the terminal in this scenario and entering this command to automatically adjust the system partition and storage pool:

Code: Select all

/etc/tos/scripts/mntdata

The reason for asking you to try inserting 2 or 3 discs is to confirm whether the issue is caused by insufficient power supply. May I ask if you are using the original power adapter? What is its output current?

[antocara]

Thank you for your replay

Regarding the dmesgw.log, you have not followed the requirements. You should keep it until 30 minutes after the abnormality (complete unresponsiveness) occurs, and then retrieve it upon the next startup.

I'm sorry. If I understood your request correctly to do what you are asking I need to insert the "dmesg -w >> /mnt/md0/public/dmesgw.log" command in a script to start automatically as an init script.The script need to check weather *.log file exists and rename it in this case to avoid the overwrite at next start. Please remenber that I cannot access the NAS via ssh when it starts with the 4 hdd inserted. In this case the system appears with all led green but does not respond even if i keep the power button pressed. To turn it off I need to disconnect the power. I can provide the log starting it with one disk as soon as ssh is operative, then insert the other 3 disks an try to mount them as you suggested if this is what you meant. If I boot it with one disk and then I insert all the other the system never becomes irresponsiveveness.

The reason for asking you to try inserting 2 or 3 discs is to confirm whether the issue is caused by insufficient power supply. May I ask if you are using the original power adapter? What is its output current?

Yestserday I tried with 3 disk inserted. This morning after about 12 hour all led are green but I cannot access the nas. Later on I'll try with 2 disks.
The power supply is the original one. I have not changed it. I have another one 12V 5A. shall I try with it ?

[antocara]

Below the log of "/etc/tos/scripts/mntdata" It started ok with disk 1 and 2 inserted then I added 3 and 4 and execute the commad

Code: Select all

Welcome to TNAS
root@TNAS-01573E:~# /etc/tos/scripts/mntdata
script mntdata get lock
dev.raid.speed_limit_max = 200000
dev.raid.speed_limit_min = 100000
mdadm: sdd2 does not appear to be a component of /dev/md9
mdadm: added /dev/sdd2
mdadm: sde2 does not appear to be a component of /dev/md9
mdadm: added /dev/sde2
mdadm: /dev/md9: no change requested
mdadm: sdd3 does not appear to be a component of /dev/md8
mdadm: added /dev/sdd3
mdadm: sde3 does not appear to be a component of /dev/md8
mdadm: added /dev/sde3
mdadm: /dev/md8: no change requested
mdadm: Fail create md1 when using /sys/module/md_mod/parameters/new_array
mdadm: /dev/md1 has been started with 1 drive.
mdadm: Fail create md3 when using /sys/module/md_mod/parameters/new_array
mdadm: /dev/md3 has been started with 1 drive.
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  WARNING: Duplicate VG name vg2: Existing fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd (created here) takes precedence over ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B
  WARNING: Duplicate VG name vg2: Existing ybiByD-BvZS-GNCt-1sy4-I7bf-Ibl3-BGGU9B (created here) takes precedence over fM4xku-XBc8-JsYY-0Gci-h14M-Bqdv-godwEd
  Volume group "vg2" successfully renamed to "gr3"
  Volume group "gr3" successfully renamed to "vg3"
check filesystem on /dev/vg1/lv1
  Reading all physical volumes.  This may take a while...
  Found volume group "vg3" using metadata type lvm2
  Found volume group "vg2" using metadata type lvm2
  Found volume group "vg1" using metadata type lvm2
  Found volume group "vg0" using metadata type lvm2
Starting Flashcache...
Waiting for udev to settle...
/sbin/flashcache_scan: line 16: /sbin/udevadm: not found
check filesystem on /dev/vg3/lv3
  Reading all physical volumes.  This may take a while...
  Found volume group "vg3" using metadata type lvm2
  Found volume group "vg2" using metadata type lvm2
  Found volume group "vg1" using metadata type lvm2
  Found volume group "vg0" using metadata type lvm2
Starting Flashcache...
Waiting for udev to settle...
/sbin/flashcache_scan: line 16: /sbin/udevadm: not found
public 1
appdata 1
F1Storica 1
Film-HD 1
Film-con-DVD 1
Film-senza-dvd-corto 1
Film_Famiglia 1
Formula1 1
Foto_Famiglia 1
Musica-Definitiva 1
SerieTV 1
Film-No-DVD 1
Archivio-Buckup-new 1
Video-Doppioni-Duplicati 1
Archivio 1
coresize=3072
swapsize=2048
fireware=https://download3.terra-master.com/TOS%20packages/TOS%20installation%20packages/4.2/arm%20realtek1296/TOS_A1.0_Install_ARM4.2_4.2.44_LTS23061206_2403260950.ins
md5=8821252485b99b357d145b972289a073
version=4.2.44

script mntdata put lock
root@TNAS-01573E:~#

[TMzethar]

12V5A may not be sufficient to power all disks. There is no need to attempt it.
You do not necessarily need to set up an automatic task. Please execute the command while the NAS is running, keep the terminal window open, and after 30 minutes, it may record information from the moment of the crash.
If your TOS version is outdated, you can try updating or resetting the system, which may resolve some software-level issues. (The latest version is 4.2.44)

[antocara]

Thank you for your replay.

You do not necessarily need to set up an automatic task. Please execute the command while the NAS is running, keep the terminal window open, and after 30 minutes, it may record information from the moment of the crash.

I'm sorry, probably I was not clear enough in my post. I'm not experiencing system crashes. When the system boots ok is on with no problems for days.

The issue is that lately the system does not boot correcltly when all disk are inserted at power. What I can tell is that after about 30 min from starting I can year the beep sound that generally indicates that the system is on and accessibleall leds are green, but I cannot access the system. It seem freezed. So in this condition I do not have any chances to run "dmesg -w >> /mnt/md0/public/dmesgw.log" .

Now the system is up and working with all disk inserted and I can have access to the whole archives, but I had to start it with one disk, getting access to it, insert the other tre disk, wai a couplle of minuts and run "/etc/tos/scripts/mntdata" to mount the other three disks.

So why is it like this ?

I have the latest TOS version I think: TOS 4.2.41-2203011629.

Regards

[TMzethar]

Understood clearly. Currently, it is not possible to easily log abnormal moments. After executing the automatic mount detection script, some changes may have occurred. Please try restarting or booting again with multiple HDDs installed. The latest version is 4.2.44. If you consider it feasible, you might want to reset the system to rule out some software-level issues.

[antocara]

Hi,
sometime I still have the issue after booting. I have hard time to understand why I have this issue. All the 4 hdd are in really good helth (all at 100%). I cannot find Tos version 4.2.44 . I have 4.2.41 which is the latest I can find in your download zone. Shall I try the update once you tell me where can I fand version 4.2.44 ?
Regards,