Constant disc activity after reboot

[magnus4ever]

Today i noticed (again) some strange behaviour of my F4-424.

I have 2x4TB drives in a TRAID pool. I did a reboot today, and after starting up i noticed a lot of drive activity. Checking process monitor tells me the array is constantly reading/writing. however, theres no indication anywhere what is causing this. All cloudsync tasks and connections are deactivated, there's no file transfer from any system in the network, nothing.

Is this some kind of resync? Storage Manager says everything is normal.

[TMzethar]

Hi. You can open Terminal and enter the following command to observe which process is continuously reading and writing:

Code: Select all

pidstat -d 3

[magnus4ever]

Thanks for pointing this out. Here's what I found:

Processes that cause Read/Write activity are kworker/3:2 kcopyd for read and TOSDaemon for write.

Kcopyd is for copying sectors, does that mean the pool is resyncing?

[sergio]

Maybe you need do some screenshot of these persistent read and write processes for analyze....

[TMzethar]

This might be related to reading and writing cache operations. Are you using the SSD Hyper Cache feature? If so, please let us know which Hyper Cache mode you are using.

[rfbjr]

I had support connect to my NAS a new days ago. Yes the issue was directly related to Hyper Cache. Mine is set to balanced mode.

Here was the response from support:
The inspection is complete. As previously suspected, the issue is related to the SSD Hyper Cache. We have identified the cause of the problem and are currently discussing relevant countermeasures.

We apologize for the inconvenience this issue has caused you. We will address it and release a new TOS update. Please keep an eye out for the update notification.

[luismartin]

More than a year has passed and with a new version of TOS7, the problem of that disk activity remains the same.

[MikeZhang]

The problem of a NAS's hard drive remaining constantly busy after a reboot is indeed a headache. The most effective approach is to use the `pidstat -d 3` command to pinpoint which specific processes are continuously reading and writing to the hard drive.

[luismartin]

The problem is always relative when Hyper Cache is enabled. Hyper Cache synchronizes the cache with the disks every boot, and there are read/write operations between the 1GB M.2 drive where Hyper Cache is located and the hard drives.

But I don't understand Terramaster's hypercache method of synchronization. I've had other NAS devices, and they worked very well without generating this disk wear and noise.
The only solution is to not use hypercache and forget that it exists.

[TMzethar]

We will continue to monitor and attempt to reproduce the abnormal situation you mentioned.