*ANOTHER* constant disk activity thread

[orion]

So, to Asustor it is normal to 1) have Volume 1 never, ever stop reading/writing and 2) to wear down Volume 2 in 10 months to the point of needing a replacement?

I believe it should be investigated more deeper (regarding to Load_Cycle_Count). Somebodies prove that Seagate HDDs perform this behavior by intention (at least some models).

[vitosx]

@danchees
You have exactly the same HDD model I have (ST4000VN008) and already described as problematic in viewtopic.php?f=28&t=9246

The disk activity is not coming from operating system, it is an internal firmware issue in this 4TB IronWolf drive. When I installed mine in computer temporarily, it also generated this weird head seeking and parking noise. I contacted Seagate support about this behavior and got unsatisfactory answer "it's normal, don't worry" - which I quoted in my thread.

I just can't recommend 4TB IronWolf at this point for anyone expecting low operating noise and reasonable HDD life.

If you don't want to buy another HDDs, I described how to modify HDD behavior using hdparm tool (the drawback is hibernation must be disabled, if was used). I am still using this fix myself.

[danchees]

Hey, Vitosx, thank you for taking the time to respond. I have actually seen your thread, but the solution seems a bit over my capabilities - for example, I don't know how to create scripts.
I was kinda hoping that a more recent and easier solution was found.
What is interesting here is that I have two identical disks, bought at the same time in the same store and they behave radically different. Actually, they have same model number but different serial numbers - don't know if serial is drive-unique or batch-unique.
For future reference, I can also confirm that disk activity leading to abnormal Load_Cycle_Count is probably not initiated by the OS. Load_Cycle_Count seems to increase even when NAS reads the disk as in hibernation (?!?) - I will do some more testing to confirm this tonight. And open my own ticket to Seagate, specifically asking if they will replace the disk once the SMART fails (and it will very soon, now it is on 3% for that metric).

I am looking at this problem now separately from my other problem where OS is brutalizing my Volume 1 by absolutely constant reads/writes that never ever stop, now for months. Will update on that again with any new info.

[colaker]

hello guys,
i've also problem with hibernation. i've 1002 with one 3tb disk. when i bought for the first time it only wakes when i reach it on web ui or samba share but now it wakes a lot in a day and its not periodic wakes.

first it set for 30 mins to hibernate. and i've download center active for 2a.m. to 8a.m. and i dont reach it outside too much in a day but mobile app notify me a few times in a day.
the diagnostic tool says 2 process read and the screenshot here.


edit: one thing forget to mention, i have android tv installed kodi and it has access to nas via samba. (android tv never sleeps and may be kodi try to reach it but idk)

[orion]

"lighttpd" is ADM web server. If you still connected to NAS using browser during detecting period, you should see this process to access disk. Did you close browser, then wait 30 minutes or more, then login to ADM web to get the report?

[colaker]

"lighttpd" is ADM web server. If you still connected to NAS using browser during detecting period, you should see this process to access disk. Did you close browser, then wait 30 minutes or more, then login to ADM web to get the report?

thank you. will try and post it here again

[psychoboy]

danchees,

I too have the same problem with the same device AS1002T, my 2 drives are brand new WD Reds that were on their approved list. My Linux skills are probably only marginally better than yours, but I have found a bunch of stuff while googling about this in my case. I see in the "tool" that MDADM is the culprit for me. And, although I did not get this far earlier in the process were I could check it then, I think that this has been a problem since v3 of the OS was released. I don't think that Asustor is addressing this problem because of maybe two reasons, it is only affecting our devices or they don't know what is going on. I found some examples where it was related to the ARM platform and some other manufactures are experiencing it also. Although, I was hoping for a solution, I see none in sight. At this point I may just jump ship and call it a day with Asustor products, as I have gotten no response from tickets I have filed. It sucks, but I don't want to see my drives ruined by this device as I paid more for them than the NAS. I am also not happy with the security of this thing after the v3 update. It wants to hit all kinds of servers all day long even though I am not running any apps, I have posted about that in other threads. I have isolated it with my firewall so that it can not hit those servers, but I don't see why if I have the "cloud" turned off that it needs to go there still. My 2 cents...

Good Luck!

[Marco@ASUSTOR]

What is your ticket number?

[Asprine]

Same here thing Won't stay down.