TerraMaster Forum

I have trouble connecting the NAS to a Active Directory Domain.

When i try to configure it it gives an error at check network Port 389 cannot be connected!.
I validated from the shell of TOS and the port is reachable.

rob44 wrote: ↑07 Jul 2026, 01:35

Please verify that the domain configuration information and authentication information are correct.
You can reach the port from the shell, but if you cannot connect through the web page, the issue is typically related to authentication settings or network connectivity.
If you have confirmed that everything is correct, please visit the link below and schedule a remote session with online customer support:

https://salesiq.zohopublic.com/signatur ... 97d0be8892

MikeZhang wrote: ↑25 Jun 2026, 18:10

Lex wrote: ↑25 Jun 2026, 16:48

Manual installation: https://we.tl/t-wPMOgeVv9kTBTHgb

Hi, plz give me this file. I can't installed qbittorrent(( because he used to php 7.4. I try to install 7.4.33.12 php, but not success (
99% of them show up for 5 minutes and then it's no success.
tos 7.0.0777

Konstantin wrote: ↑09 Jul 2026, 09:06

We need to check this issue remotely. Please contact the online technical support personnel via the following link to schedule a remote technical support service, and attach the forum link and your forum ID:
https://salesiq.zohopublic.com/signatur ... 97d0be8892

Hi everyone. I have a F4-421.

After the update, my NAS didn't restart. After some hours, I powercycled it. Nothing. Tried to remove all HDD. No installation welcome wizard.
Connected monitor and keyboard. It was stuck in "Boot form INIT". So rebooted, went to bios (my version is ending with 21, updated when I had the auto-start bug), tried to manually select the internal disk as boot, then "Booting form RAID"... and it started. Now is doing the permission conversion.

So... as I understand, my bios is locked to use the internal USB stick. So the update of the stick went bad? I've found images only until TOS6... is there a way to install the TOS7 init image? Or there is an option to tell my bios to always start from the RAID (I don't think I've found one, but when my NAS started, I will not be able to reboot and check until the permission thing ends). Or there is an updated BIOS image?

Thank you!

Alby87 wrote: ↑14 Jul 2026, 02:17 Hi everyone. I have a F4-421.

After the update, my NAS didn't restart. After some hours, I powercycled it. Nothing. Tried to remove all HDD. No installation welcome wizard.
Connected monitor and keyboard. It was stuck in "Boot form INIT". So rebooted, went to bios (my version is ending with 21, updated when I had the auto-start bug), tried to manually select the internal disk as boot, then "Booting form RAID"... and it started. Now is doing the permission conversion.

So... as I understand, my bios is locked to use the internal USB stick. So the update of the stick went bad? I've found images only until TOS6... is there a way to install the TOS7 init image? Or there is an option to tell my bios to always start from the RAID (I don't think I've found one, but when my NAS started, I will not be able to reboot and check until the permission thing ends). Or there is an updated BIOS image?

Thank you!

Thank you for providing the detailed information.

Based on your description, the NAS booting into the USB initialization environment may indicate that the system detected an issue with a previous system version remaining on one of the hard drives, preventing the NAS from booting normally from the current system.

Please follow the steps below to check:

1. After entering the TOS 7 desktop, go to:

Storage Manager → Disk → System Disk

2. Check the system disk list:

Please check whether there are any system disks that are not the currently active system disk, or any abnormal system partitions.

3. Remove the abnormal system disk:

If you find an abnormal system disk, please select it and remove it from the System Disk page.

This operation only removes the system partition and will not affect your personal files stored in the data partition.

Important:

For data safety, please make sure you perform this operation only from the System Disk page.

Do not delete disks, initialize, or format drives from other pages in Storage Manager, as this may affect your data.

After removing the abnormal system partition, please reboot the NAS and check whether it can boot normally from the HDD system.

If the issue persists, please provide a screenshot of the System Disk page for further analysis.

Felix wrote: ↑15 Jul 2026, 14:26 Based on your description, the NAS booting into the USB initialization environment may indicate that the system detected an issue with a previous system version remaining on one of the hard drives, preventing the NAS from booting normally from the current system.

No, I've the opposite problem: if there are no HDD present, nothing happens: I've no USB initialization enviroinment. I've connected the NAS directly to LAN and searched with your client software, nothing.

The same happens when I re-install the disks.

The only way to start it is to manually select the harddisk as boot device, and it will start TOS7, not initialization enviroinment.

Alby87 wrote: ↑15 Jul 2026, 14:40

Felix wrote: ↑15 Jul 2026, 14:26 Based on your description, the NAS booting into the USB initialization environment may indicate that the system detected an issue with a previous system version remaining on one of the hard drives, preventing the NAS from booting normally from the current system.

No, I've the opposite problem: if there are no HDD present, nothing happens: I've no USB initialization enviroinment. I've connected the NAS directly to LAN and searched with your client software, nothing.

The same happens when I re-install the disks.

The only way to start it is to manually select the harddisk as boot device, and it will start TOS7, not initialization enviroinment.

We need to check this issue remotely. Please contact the online technical support personnel via the following link to schedule a remote technical support service, and attach the forum link and your forum ID:
https://salesiq.zohopublic.com/signatur ... 97d0be8892

Hello,

After upgrading from TOS 7.0.0601 to TOS 7.0.0746, several TOS management API endpoints started returning 502 Bad Gateway, including storage-volume, disk-speed, and external-storage requests. Other endpoints continued working.

The internal nginx error is:
At first, StorageManager.service was inactive. Starting it manually recreated the socket and restored the affected UI/API calls.

However, App Center also had package-operation problems. I attempted to reinstall Storage Manager through App Center; it failed with Error State=2. After that failure, the Storage Manager package is now absent:
The NAS remains reachable. Existing Btrfs volumes are mounted, Btrfs device error counters are zero, and Docker workloads continue running normally. I have not rebooted, reset, initialized, deleted, or modified any disks or pools.

What is the supported recovery procedure to restore all affected TOS management services, especially the missing StorageManager system package, without touching existing Btrfs data volumes? Is updating or reapplying TOS 7.0.0765/7.0.0780 safe and appropriate in this package state, or should this be handled by remote support?

A bit more details:

NAS model: TerraMaster F4-425 Plus
TOS version/build: TOS_X642.0_7.0.0746
Upgrade path: TOS 7.0.0601 -> TOS 7.0.0746
System volume layout: Btrfs Volume 1 and Volume 2
Storage Manager package version before failure: 1.0.047

Felix wrote: ↑15 Jul 2026, 17:56 We need to check this issue remotely. Please contact the online technical support personnel via the following link to schedule a remote technical support service, and attach the forum link and your forum ID:
https://salesiq.zohopublic.com/signatur ... 97d0be8892

Ok! After a quick chat, I got the InitBoot image, flashed it and now works flawlessly. Thanks