TerraMaster Forum

RyanYang wrote: ↑25 Jun 2026, 14:39

Could you confirm the version of PHP that is installed via the "Official Release" (7.0.0747)?

Gremlin wrote: ↑25 Jun 2026, 14:49

RyanYang wrote: ↑25 Jun 2026, 14:39

Could you confirm the version of PHP that is installed via the "Official Release" (7.0.0747)?

The current latest version is PHP 7.4.33.9.

kowei13 wrote: ↑24 Jun 2026, 22:42

From the screenshot, the issue may be caused by abnormal media indexing. Please restart your device again, then disable media indexing, and download the debug logs and send them to us as per the method mentioned in our previous reply.

kowei13 wrote: ↑24 Jun 2026, 22:42

This issue is caused by the Linux OOM (Out of Memory) deadlock mechanism.

Why do web pages fail to load?
When both physical memory and swap space are exhausted, the system enters a state of severe thrashing. At this point, the kernel consumes all CPU time slices swapping memory pages in and out between RAM and the hard drive (you can observe this in the `PAG` line of the `atop` utility, where `swin`/`swout` values ​​typically turn red).

This extreme I/O congestion leads to the following:
Web services (such as Nginx, TOSDaemon, etc.) are unable to allocate new socket buffers or memory pages, resulting in rejected connections or request timeouts.

When the OOM mechanism is triggered, the kernel issues `SIGKILL` signals to memory-intensive processes to free up space. During this process, the system experiences intense thrashing; the massive volume of page swapping and process context cleanup causes extreme congestion in the host's I/O queues and CPU scheduling—which is the root cause of the web services (pages) becoming unresponsive.

In this situation, please be patient. Once the kernel terminates the high-resource processes and reclaims anonymous memory pages, the I/O load will drop precipitously, allowing web daemons (like Nginx or TOSDaemon) to reacquire memory resources and resume responding.

RyanYang wrote: ↑25 Jun 2026, 14:37

kuzan wrote: ↑25 Jun 2026, 05:32

Have you ever modified the BIOS boot order before? It seems like the USB boot on your motherboard may have an issue, causing the system to prioritize booting from the USB device at startup. If that's the case, you can enter the BIOS, press F3 to restore the default boot order, then press F4 to save and exit, and reboot. Alternatively, you can try booting without any disks connected, or unplug the USB boot device before powering on. What BIOS version does your TOS update module display? Also, you can refer to this method to create a new USB boot drive: viewtopic.php?t=6433

No, I didn't change the BIOS boot order before. I had to create a new USB boot drive to restore the NAS, since it wasn't booting after the update. Now I have the TOS 6.0.794 again and it's working, but if I update to 7, I get the same issue.
I have 180GB free on my disks, and I added a new RAM module in the past. I updated the system from 4 to 6 following all the intermediate steps and I had no issues at all.
My BIOS version is the last available, MAPL0304V22.
Thanks.

kuzan wrote: ↑25 Jun 2026, 15:19

Root Cause and Perfect Solution for Getting Stuck at the "initboot" Screen After Upgrading to TOS 7

Why does it get stuck at "initboot"?
Upon upgrading to TOS 7, the system's underlying partition table and boot mechanism were restructured. Getting stuck at "initboot" usually occurs because:

Multi-drive boot conflict: Another hard drive in your system may still contain remnants of the old system's boot data or old Btrfs volume labels (UUIDs), which conflict with the boot configuration established after reflashing to TOS 7. When the bootloader scans the drives, it cannot distinguish which system partition to read, resulting in a mount deadlock.

To resolve this boot deadlock, we need to:

First, unplug one of the hard drives. If the system boots into TOS 7, plug the other hard drive back in while the system is running.
To prevent getting stuck at the "initboot" screen again after future restarts:
Please click the link below to schedule a remote support session so we can resolve this for you.
https://salesiq.zohopublic.com/signatur ... 97d0be8892

If the system boots into the old TOS instead, shut it down, swap to the other hard drive to boot, and then perform the steps mentioned above.

RyanYang wrote: ↑25 Jun 2026, 14:39

installed from appcenter, also reinstalled php 7.4 and qbit

elfirwhite wrote: ↑25 Jun 2026, 16:32

Please restart your TNAS and observe if it fixes

MikeZhang wrote: ↑25 Jun 2026, 16:50

nothing changed

elfirwhite wrote: ↑25 Jun 2026, 17:10

Please click below link to schedule remote session and we will fix it for you remotely
https://salesiq.zohopublic.com/signatur ... 97d0be8892
Note: session is available at 10AM, 11AM, 2PM to 5PM from Monday to Friday UTC+8