Storage • Why does TNAS sometimes fail to start up?

Applicable Models
F2-220, F2-221, F2-223, F2-420, F2-422, F2-423, F2-424
F4-220, F4-221, F4-223, F4-420, F4-421, F4-422, F4-423, F4-424, F4-424 Pro, U4-111, U4-423
F5-220, F5-221, F5-420, F5-421, F5-422
T6-423
F8-421, F8-422, U8-111, U8-420, U8-423, U8-450, U8-322-9100, U8-522-9400, U8-722-2224
T9-423, T9-450
T12-423, T12-450, U12-420, U12-423, U12-322-9100, U12-722-2224
U16-420, U16-322-9100, U16-722-2224, U16-722-2288
U24-612, U24-722-2224

Applicable Versions
All TOS Versions

Fault Phenomena
During startup, the device fails to start successfully. After the first beep indicating the BIOS boot process, no further changes occur.
TNAS cannot be searched or accessed, and ping requests to TNAS fail.
When connecting TNAS to a display via HDMI, errors related to "UEFI" and "boot" may appear.

Cause Analysis
There is a probability of unsuccessful startup when TNAS is launched, and no further changes occur after the first beep sound.
If a hard drive's boot partition has missing or corrupted files, it can lead to intermittent startup failures.
This issue can be caused by installation errors, power failures, filesystem errors, or other reasons.

Resolution
1. Test and Identify the Abnormal Boot Partition Disk:
Start TNAS with only one hard drive installed.
If you can search for TNAS using the TNAS PC, the startup is successful. If not, or if you cannot ping TNAS, the startup failed.
Repeat this test for each hard drive.

2. Repair the Abnormal Boot Partition Disk:
Start TNAS without any hard drives installed.
Insert any hard drive with a normal boot partition.
Connect to TNAS via SSH and login: https://forum.terra-master.com/cn/viewt ... =87&t=1511
After successful SSH login, insert the hard drive with the abnormal boot partition.
Wait for 3 minutes, then run the following commands to repair the boot partition:3. Resume Normal Operation:
Insert all the hard drives back into TNAS.
Restart TNAS.

Statistics: Posted by TMzethar — Today, 09:09

---