TOS 7 Is Now Out of Beta — Official Release

[elfirwhite]

/Volume1/@apps/qbittorrent/bin/qbittorrent-nox: error while loading shared libraries: libtorrent-rasterbar.so.2.0: cannot open shared object file: No such file or directory

[kowei13]

I have tried to disable Terra Photo and Media Indexing but issue remained.

What is the minimum RAM recommended for running TOS7? The RAM upgrade is on the way btw.

I have leaves the F2-223 running for more than 24 hours but the Web Daemons or other IP stacks does not recover. How long it might takes?

[RyanYang]

Have you sent your debug logs to the after-sales support team yet? We need to review the detailed log contents.
The recommended memory size should be determined based on your actual use case.

[kowei13]

Yes, already sent via email.

I have upgraded the RAM from 4GB to 20GB. So far, no more out of memory issue faced. The storage volume is synchronising with media index remain disabled. Once awhile noticed the Memory usage spike up to 5GB and reduced back to 1GB++. Will continue to monitor.

[kuzan]

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.

I installed TOS7 again and tried your instructions. The NAS didn't boot with any of the disks, I tried with both and also without any of them. Any other suggestion?

UPDATE: I found the boot override option in the BIOS, and I was able to boot in TOS7 by choosing the first HDD. However I scheduled a remote session, thanks.

[ORION]

After switching to tos 7.0.0747, I installed the VM app, but it only works with btrfs file systems and doesn't support ext4. The issue of disk overflow with chunks and metadata has returned (it didn't happen with ext4 and VirtualBox). I have a 256 GB SSD volume and a 200 GB virtual machine. The volume fills up 100% in 3 days, and the virtual machine stops. Does anyone else have such problems with btfrs, or am I the only one who is so "lucky")) is there any way to add ext4 support so that there is no overflow? I tested it last time and understood the reason for the overflow (I wrote to tech support, but there was no solution)

[EriChan]

What is the current version of your VMS application?

[davep1628]

Hi,

I have downloaded this file - TOS_X642.0_Update_7.0.0747_1247_2606171225.bz2, but when I attempt to upgrade my F4-423 TOS 6.0.794 system, I just see an "Operation Failed!" message. I have BIOS version 5.19 and the system is set to boot off the hard disks.

Any pointers to resolve the problem?

Regards,
Dave.

[Gremlin]

Try this: viewtopic.php?t=9417

[davep1628]

Yes, I've checked the Project Version and it is correct (T1509BGO) and I have set the Boot Order as per that guide, but it still comes up with the same "Operation Failed!" message.

Any other ideas?

Regards,
Dave.