TerraMaster Forum

TMRyan wrote: ↑27 Feb 2025, 09:25

rfbjr wrote: ↑26 Feb 2025, 20:12 Running fine on both (F2/F4-223) iSCSI running fine and attached LUNs, no issues.
Actively working with support on the F4 why the RAID5 disk activity is busy for ~2hr after any type of restart.
Even the reboot after applying the 648 update has the disks going.

When you notice your disk is busy, you can go to the "Processes" section in the Control Panel to check which processes are using the hardware resources.

Yes I know and this info has been emailed to support (open case ongoing)
Linux 6.1.58+ (Forge) 02/25/25 _x86_64_ (2 CPU)

07:42:11 UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command
07:42:12 0 26 152079.21 0.00 0.00 0 kworker/1:1-kcopyd
07:42:12 0 113 125718.81 0.00 0.00 0 kworker/0:3-kcopyd

07:42:12 UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command
07:42:13 0 26 73728.00 0.00 0.00 0 kworker/1:1-kcopyd
07:42:13 0 113 133120.00 0.00 0.00 0 kworker/0:3-kcopyd

The programming to turn off the nas still does not work for me

rfbjr wrote: ↑27 Feb 2025, 20:29

Please be patient! Our technical support engineers will respond to your email as soon as possible.

addx972 wrote: ↑27 Feb 2025, 22:36

Hello! Could you please provide more details about the issue you're experiencing?

viewtopic.php?p=43783#p43783

Basically any shutdown or reboot (the one for 648) both my F2/F4 have some sort of disk activity. On the F4-223 it's aprrox 2 hours after the system is brought back up. The GUI for volume/storage pool shows nothing like sync is progress, everything normal.

updated, no issues noted so far, it was a nice touch to get the email update to say its been updated to the new version

TMbuddy wrote: ↑27 Feb 2025, 23:32

addx972 wrote: ↑27 Feb 2025, 22:36

Hello! Could you please provide more details about the issue you're experiencing?

I have programmed the NAS to turn off at scheduled times, but it doesn't work. I have to turn it off myself. However, the scheduled power on works.

Firstly, thank you to all the TerraMaster staff who worked on this release. I understand you are probably understaffed and have a lot of work. Please know my following comments relate to the company and not you personally.

Disappointed this release did not fix the following BUG

viewtopic.php?p=44013#p44013

Or add the small requested FEATURE:

viewtopic.php?p=44012#p44012

Not entirely sure why we wait months and don't have any movement on community submitted bugs and small features. ALL releases should include at least some improvements submitted by the community!

As a NAS beginner, I only used to store files and make backups, even so, it has no problem moving large files such as photos, 4K videos and so on. TOS was updated to its 6th version in August 2024 and since then they have mitigated virtually all the problems that could give. I followed up with an update to 6.0.500, in my case I have only detected on one occasion of my F4-424 that the remote access was lost but after a couple of minutes it was operational again. Now I successfully upgraded to 6.0.648 with the help of TerraMaster online customer service, I think it is intuitive, simple and complete, with a multitude of apps for both beginners and more technical users.

CodeTheFuture wrote: ↑28 Feb 2025, 10:28 Firstly, thank you to all the TerraMaster staff who worked on this release. I understand you are probably understaffed and have a lot of work. Please know my following comments relate to the company and not you personally.

Disappointed this release did not fix the following BUG

viewtopic.php?p=44013#p44013

Or add the small requested FEATURE:

viewtopic.php?p=44012#p44012

Not entirely sure why we wait months and don't have any movement on community submitted bugs and small features. ALL releases should include at least some improvements submitted by the community!

For the already released versions of TOS, we generally do not add new features. New features will only be introduced in future major version updates, such as TOS 6.1 or TOS 7. For confirmed bugs, we will address them as soon as possible based on their priority and severity. If the cause of a bug you reported cannot be identified, we will continue to investigate and follow up. Please stay tuned for our update notifications.