TerraMaster Forum

Hi TerraMaster Team,

I'm hoping someone can help investigate what appears to be a problem with the TOS 6 manual update process.

Hardware
Model: F4-425 Plus
BIOS: MTWL0101.V07
Current OS: TOS 6.0.794
Target version: TOS 7.0.0747
Storage:
2 × 6TB IronWolf (TRAID mirror / Volume1)
2 × NVMe SSDs (Volumes2 & 3)
The system is healthy:
RAID healthy
Docker healthy
SMART healthy
No storage errors

Since my BIOS is already MTWL0101.V07, I should not require any BIOS update before installing TOS 7.

Problem:

Using the TOS web interface:

Upload firmware
Verify
Click Update

The download reaches 100%. The next dialog displays: Unzipping the software package. Please wait!

The dialog never progresses. I waited over 5 hours on my first attempt. Today I repeated the process with SSH monitoring.

The NAS:

never rebooted
SSH remained connected
ping continued normally
Docker continued running

So the actual upgrade never started.

TOSDaemon log

Immediately after clicking Update, TOSDaemon logs:

POST /update/start
not found update package

No installer process is started afterwards.

Firmware file

The uploaded firmware is still present on disk after the failure:

/Volume1/.update_xxxxxxxxxxxxxxxxx/
TOS_X642.0_Update_7.0.0747_1247_2606171225.bz2

The file size is 788 MB

Linux reports: file TOS_X642.0_Update_7.0.0747_1247_2606171225.bz2

returns: gzip compressed data

The archive passes integrity testing: gzip -t TOS_X642.0_Update_7.0.0747_1247_2606171225.bz2
returns: 0

So the uploaded package appears to be intact.

Additional observations

During the "Unzipping..." screen:

SSH remains responsive
uptime continues increasing
no reboot occurs
no installer process appears
the firmware file still exists in the .update_* directory

The only backend error I can find is:

not found update package
Question

Has anyone seen this behaviour before?

Could this be:

• an issue with the TOS 6 updater losing track of the uploaded package?
  a known bug in TOS 6.0.794?
  something specific to build 7.0.0747?

Is there a recommended way to diagnose why /update/start cannot locate the uploaded package even though the firmware file is present and passes integrity checks?

Any guidance would be greatly appreciated.

Thank you.

PeteL wrote: ↑28 Jul 2026, 16:15

Thank you for the detailed description. To further investigate potential abnormalities in the TOS system, please reach out to our online technical support team via the link below to arrange a remote diagnostic session:
https://salesiq.zohopublic.com/signatur ... 97d0be8892

PeteL wrote: ↑28 Jul 2026, 16:15

You might be able to check the update log(s) in your home directory.