MikroTik

Should I be afraid of it?

Thats quite a .... big number

This is a known bug, where the sector writes shows incorrect. Netinstall with the v5.21 from the webpage will fix it.

Which version will fix the known bug that products announced for end of september are released in december? On that note, are there any plans as to in which version CCR price will get announced?

Which version will fix the known bug that products announced for end of september are released in december? On that note, are there any plans as to in which version CCR price will get announced?

Thanks for reporting to many v6 problems We have plenty of software issues to fix, so that the CCR has stable software. This is much better than having problems because nobody reported anything.

But why fixing bugs has to offset the price of CCR so much?

When we announce the price, peoeple will want to order it very much Why tease anybody with good prices, when we can't deliver? We will release price when device can be ordered.

...not that writing a post like that isn't a mother of all teases :>

This is a known bug, where the sector writes shows incorrect. Netinstall with the v5.21 from the webpage will fix it.

Unfortunately it didn't help in my case.

I have 951-2n, operational from november 2012 (with 5.21). it is performing quite well, and currenlty it is working with 5.22 firmware.

I had processed with netinstall (5.22), but write-sect-total is still extra large.
It is not growing rapidly (normally i believe), so the most important thing was solved, but how to force my 951-2n to show the correct amount of total written sectors or clear it to the initial value ?

You can find my current resource status below, how to solve this issue ?

[admin@951-2n] /system> resource print
uptime: 19m
version: 5.22
free-memory: 16780KiB
total-memory: 29696KiB
cpu: MIPS 24Kc V7.4
cpu-count: 1
cpu-frequency: 360MHz
cpu-load: 2%
free-hdd-space: 30060KiB
total-hdd-space: 61440KiB
write-sect-since-reboot: 539
write-sect-total: 3465660650889648
bad-blocks: 0%
architecture-name: mipsbe

I can physically access this unit not very often, because it is installed on remote site, and for next three days i will be able to perform additional steps, so please advice what to do,
or inform that i have to deal with this enormous number of written sectors.

Best Regards, m80211

I had same problem with RB951, Netinstall 5.22 didn't help.
I sent it back to distributor for RMA.

Regards,

upgrade to the latest firmware and reinstall with a netinstall then it should be showing correctly.

upgrade to the latest firmware and reinstall with a netinstall then it should be showing correctly.

Firstly i have to say that, i had deinstalled 951-2n from remote site, and took it back with me, so i have more time to solve/abandon this issue.

Like Uldis suggested, I made the procedure once again, and still no success ;/

[admin@MikroTik] > /system resource print
uptime: 1m54s
version: 5.22
free-memory: 18708KiB
total-memory: 29696KiB
cpu: MIPS 24Kc V7.4
cpu-count: 1
cpu-frequency: 360MHz
cpu-load: 1%
free-hdd-space: 30516KiB
total-hdd-space: 61440KiB
write-sect-since-reboot: 1843
write-sect-total: 3465660650920377
bad-blocks: 0%
architecture-name: mipsbe
board-name: RB951-2n
platform: MikroTik

I've used 5.22, and even 6.0rc6, netinstall didn't solve this problem at all.

Any other clues ? otherwise i will have to use RMA because it looks like this unit is faulty.

Regards, m80211

upgrade to the latest firmware and reinstall with a netinstall then it should be showing correctly.

I did it, latest RouterBOOT (3.02) and Netinstall with ROS 5.22, but still the same .
So I sent this RB for RMA.

Regards,

upgrade to the latest firmware and reinstall with a netinstall then it should be showing correctly.

It didn't help me either.

Any other clues ? or should i process with RMA ?

m80211

or should i process with RMA ?

IMHO, RMA is an only option for you.

Regards,

I've same problem on two RB951. Tried all Netinstall from 5.16 to 5.22, none of them helped. Firmware changes from 2.39 to 3.0 also no effect. Any other suggestions before RMA?

I've same problem on two RB951. Tried all Netinstall from 5.16 to 5.22, none of them helped. Firmware changes from 2.39 to 3.0 also no effect. Any other suggestions before RMA?

No any fancy methods helped so I've given up, and used RMA.

Regards, m80211

Interestingly one of my RB951-2n after netinstalling from ROS 5.22 step-by-step every version down to 5.16 and then from ROS 5.16 immediately to ROS 5.20 back returned to normal sector counting. The second one had problem after same process of netinstalls. But after n-time of netinstalling, succeeded too. I think it is some counter overflow occured and then counter returned to normal range. Experimenting with different versions of ROS on RB951-2n routerboot not always updated successfully, even it is already fixed in 5.19 (according to changelog).

I've same problem on two RB951. Tried all Netinstall from 5.16 to 5.22, none of them helped. Firmware changes from 2.39 to 3.0 also no effect. Any other suggestions before RMA?

No any fancy methods helped so I've given up, and used RMA.

Regards, m80211

Hmm Mikrotik is like Windows, time to time you need to netinstall it ..

no matter you have board installed on the site which is hard to reach, no matter you have 5000+ client devices, it's common and well problem, just netinstall it .. universal advice

sorry, but I need let steam off, 15x RB2011 on sites and we just upgrade it on 5.22 and guess what, magic nuber appears ...

Bump.. this NEED to be fixed... i dont want replace all our boards (50+). Netinstall does not work (5.14, 5.17, 5.22, 6.0rc7..), firmware upgrade/downgrade neither. Thanks.

If you upgrade to the latest firmware and do a netinstall then it should should start showing correct sector writes. If after both actions you still see that problem, make a support output file and send it to support@mikrotik.com

Hi all, i have same problem, but its not start on 5.xx, i have 951Ui with 6.11, and usermanager on it (less 100 users), and it can write 50k sectors in 30mins!!! its bug or Usermanager really harm my flash? Any solves?