Page 4 of 5
Re: TOS 7.0.1105 (x86) Official Release Update
Posted: 08 Aug 2026, 20:27
by TMzethar
Claus wrote: ↑08 Aug 2026, 20:09
Hi, I manually updated from version V804. Now I have the GlobalSearch problem too. After a restart, things look very good for a short while. However, after about 10 minutes, the process's resource usage keeps climbing higher and higher.
Hardware: F4-424 Max.
We are currently working on a fix. Please wait for a future version update.
Re: TOS 7.0.1105 (x86) Official Release Update
Posted: 08 Aug 2026, 23:56
by Claus
Thanks for the personal reply. Don't stress about it. Regards.
Re: TOS 7.0.1105 (x86) Official Release Update
Posted: 09 Aug 2026, 09:14
by nitzer71
Additional observation:
After restarting the globalsearch service with:
the CPU usage immediately returns to normal and has remained normal since then.
So far, the high CPU behaviour seems to occur after a
full NAS reboot. A restart of the
globalsearch service itself appears to clear the issue without it returning during subsequent uptime.
This may indicate that the infinite loop is being triggered during the
GlobalSearch startup/initialisation process after a NAS reboot.
Re: TOS 7.0.1105 (x86) Official Release Update
Posted: 09 Aug 2026, 18:27
by Pe6yc
F5-422 (bios MAPL0304V22)
after update TOS one of the volumes in D8 Hybrid is corrupted. Corresponding Storage pool after reboot wasn't mounted automatically.
I mounted it manually and Storage pull shows normal state but Volume still corrupted. The disk in D8 in normal state shows green.
Can I mount the volume by command line or make the volume back in normal state?
UPD: Reboot twice has fixed the problem. the volume is in working state
Re: TOS 7.0.1105 (x86) Official Release Update
Posted: 10 Aug 2026, 03:32
by snapsh0t
Pe6yc wrote: ↑09 Aug 2026, 18:27
F5-422 (bios MAPL0304V22)
after update TOS one of the volumes in D8 Hybrid is corrupted. Corresponding Storage pool after reboot wasn't mounted automatically.
I mounted it manually and Storage pull shows normal state but Volume still corrupted. The disk in D8 in normal state shows green.
Can I mount the volume by command line or make the volume back in normal state?
UPD: Reboot twice has fixed the problem. the volume is in working state
This may be an example of needing to leave the NAS alone for a few minutes after the update reboot as it needs time to get everything running. We've seen this reported here more than once recently.
Re: TOS 7.0.1105 (x86) Official Release Update
Posted: 10 Aug 2026, 04:44
by rfbjr
Been away all week. Just updated all three devices, no issues. About all I'm going to do for the rest of today. I'll slowly check things out for the next few days.
Re: TOS 7.0.1105 (x86) Official Release Update
Posted: 10 Aug 2026, 06:22
by rfbjr
Does Phase 1 actually fix what's listed in the announcement or does that happen in Phase 2?
Just trying to follow along, still in vacation mode.
Re: TOS 7.0.1105 (x86) Official Release Update
Posted: 10 Aug 2026, 14:27
by EriChan
Thanks for your feedback. We are actively working on a fix and will include it in a future version update
Re: TOS 7.0.1105 (x86) Official Release Update
Posted: 10 Aug 2026, 15:21
by EriChan
rfbjr wrote: ↑10 Aug 2026, 06:22
Yes, Phase 1 includes all the fixes and features listed in the announcement!
The only difference between the two phases is the distribution method:
- Phase 1: All fixes are included right now. You can manually download the update package from the forum and install it immediately.
- Phase 2: The exact same update will be pushed automatically as an online OTA notification in your TOS in about a week.
Enjoy the rest of your vacation!
Re: TOS 7.0.1105 (x86) Official Release Update
Posted: 10 Aug 2026, 15:44
by EriChan
Pe6yc wrote: ↑09 Aug 2026, 18:27
This kind of behavior is typically related to a disk array mounting issue during system startup. To help us pinpoint the root cause and prevent it from happening again, we recommend enabling Debug Mode:
Enable Debug Mode: Go to TOS Web UI > Help & Support > Debug Mode and turn it on so the system can record detailed logs during abnormal events.
If the issue reoccurs:
- Restart the device first.
- Download the debug logs and send them to our technical support team at [email protected] and attach the forum link and your forum ID as well.
- If possible, please note the exact timestamp when the issue occurred, as this will greatly assist our team in troubleshooting.
Note on Log Downloads: The debug package contains three files (kern.log, syslog, and atop_log). Due to their file formats, your web browser might block them. If you notice any missing files after downloading, please check your browser's download manager to allow and complete the download.