[Help] booting time ver very long F4-210

[antocara]

Hi,
I have F4-210 with four 8tb hard disk (total 32 TB).

I'm pretty happy with it. the only negative thing it that normally it takes very long time to boot and to load TOS (or to gain ssh access). Generally It takes about 30 min. I think that this time is because It checks Hd and the filesystems evrery time.

Today it is about 4 hours that is booting. I can see the four green leds on that somtime becomes orange and hear the hard disk spinning.

I have open a terminal to log in vis ssh but ssh in not repleyng anything since four hours. Also I cannot access Tos.

I do not think it is normal. What I have to do ?

Regards

[CursaYang]

Hello, the boot lag may be caused by high system resource usage or potential hard drive failure.

Please try restarting the NAS and check if you can access the TOS desktop. If so, kindly collect a system report and send it to us for analysis.

If you cannot log into the TOS desktop after restarting, please power off the NAS, remove all the hard drives, and power it on again. Listen for any beeping sounds and note how many you hear.

[ErnestosKon]

A boot time of several hours is not normal, even with large drives. It may indicate a filesystem check that got stuck or a disk beginning to fail. Before forcing a shutdown, have you checked whether any drive shows warning LEDs or unusual noises? If nothing changes, contacting TerraMaster support might be the safest option.

[AlAleksiev]

Once booted, you can validate few things before to start rebooting and waiting again...

- Login via SSH - to port 22 or 9222 depending from the TOS version
- Verify the RAID state - "sudo cat /proc/mdstat" from the CLI and share the output here
- Verify all block devices - "sudo lsblk -do +VENDOR,MODEL,SERIAL" from the CLI and share the output here
- Verify the SMART on each disk - "sudo smartctl -a /dev/sdX" from the CLI (replace X with the actual letter) and share the output here
- See the diagnostic messages - "sudo dmesg" and share the output here

Most likely the above will reveal the reason for the slow boot.

Cheers

Alex

[TMnight]

Thank you for your assistance! It should be noted that in the actual operation process, not every command to be executed requires the addition of sudo. After completing the SSH login, you can directly execute the sudo -i command to switch to the root user privileges, and then proceed with executing the relevant operation instructions.

[AlAleksiev]

It depends from many things actually - on an unknown in details distribution, where you have sudo access, it's better to go with it to avoid lack of information.
Besides that in the above commands, most likely only smartctl will require always root access for execution.
It's not a good practice to switch to root and to stay longer like that - too much power and too much bad scenarios from my 30 years practice on unix and later linux a simple wrong paste in a wrong window can create a disaster as a root.
BTW, "sudo -i" has also few synonyms ("sudo su" and "sudo -E -s" for example)... however, I'm always trying to avoid that "god mode"..

The focus here is to help the user though... how the commands will be used is not so important - the analysis of the output after that is.

Cheers

[TMnight]

Thank you very much for such a detailed and professional share. Your experiences and suggestions are of immense value to me