Hi,

i just noticed, that i have about 1500 sector writes in 15 Minutes.

Should i worry about that? How can i find out, what might be causing such a high sector write?

Maybe some service is causing this and it might be better to write to an usb stick instead of the nand, but how to find out...

Reboot fixed the issue...

Same issue after upgraded to RouterOS 6.28 mipsbe.
Reboot can fix this issue on RB951G-2HnD, but make no effect on my RB751G-2HnD.
6 sector writes per second.

Also mipsbe here. Just checked again, a lot of sector writes here still after a while....

@eternal0: fyi, downgrade to 6.27 seems to fix the sector issue, will monitor that though...

Having the same trouble after updating one of my RB951G-2HnD to 6.28: around 2 sector writes per second. Reboot seems to help to make it stop.

After messing around, I discovered that once WinBox is closed, the counters are not growing anymore. In other words, you can disconnect WinBox, log in a few minutes later, and discover the same sector write count. It starts to grow again at the same pace when I open IP -> Firewall -> Filter/Mangle view in WinBox. Closing IP -> Firewall view still keeps the counters growing. Closing the WinBox session, and connecting again (IP -> Firewall view closed!) stops counters from growing. I would guess some background thingie that reads firewall stats is writing on disk.

I can confirm this at RB750G (mipsbe).
With 6.28 sector writes are increasing.
Downgrading to 6.27 fix the problem.

Looks to me like its Winbox3 - I get 2 writes/second using winbox and 0 when using the CLI (via SSH).

I also have the same problem on an RB951g running 6.28
2 write cycles continuously when logged on using winbox.

Can other users confirm that downgrading to 6.27 fixes
the issue?

got the same on rb2011 and 6.28
see this only after 3 days
as a result: 577 602 write sector per 3 days

I have the same problem too on an RB951Ui-2hD with 6.28
2 write cycles continuously when logged on using winbox

This will be fixed in 6.29. Install an 6.29rc20, if you don't want to use 6.27, it's already fixed out there.