Constant disk activity after ADM update to 3.4.5.RBJ3

[dbkelly]

After the reboot upon installing this update I am getting constant disk activity, what is it doing? synchronizing again?
I have checked the logs, and running processes and it shows most everything is sleeping, it it giving me no indication of what it is doing.

[orion]

Did you use Settings -> Hardware -> Diagnostic tool?

[dbkelly]

No after the upgrade it rebooted and started contstant disk grinding for several hours now.

[dbkelly]

I have a 2 disk mirror setup.

[orion]

You should try diagnostic tool to find which process does disk accesses.

By the way, you can check the link here viewtopic.php?f=63&t=10694 (although it looks like that your issue is different from this one.)

[wonderbread]

I powered down my AS5034T after two days of constant heavy disk activity by "Watch_Storage", whatever that is. If it was just creating thumbnails I don't think it would take so long?

After powering back up things seemed to have calmed down. Maybe there's a bug causing the process to never terminate after completion?

[Sistemi TELL]

I powered down my AS5034T after two days of constant heavy disk activity by "Watch_Storage", whatever that is. If it was just creating thumbnails I don't think it would take so long?

After powering back up things seemed to have calmed down. Maybe there's a bug causing the process to never terminate after completion?

Tried, but CPU jumped back immediately to 90-99%. How much disk is taken by documents? and how much taken by photos?

[Sistemi TELL]

The release has been pulled form repositories and now my second NAS no longer shown "upgrade needed".

So we can assume that there IS some very serious issue

Pulling silently and upgrade is not a correct and ethical behaviour

https://www.asustor.com/en/service/down ... duct_id=45

[orion]

I think asustor should be trying to find a solution after got our reports. That's a good sign for me.

[Mr.Crowley]

The release has been pulled form repositories and now my second NAS no longer shown "upgrade needed".

So we can assume that there IS some very serious issue

Pulling silently and upgrade is not a correct and ethical behaviour

https://www.asustor.com/en/service/down ... duct_id=45

Definitely not a good behaviour, especially when the update removed was supposed to fix a vulnerability...