We’ve recently had a number of flash-disks corrupt themselves on our mikortik units. When we took the unit back to the shop and ran check-disk it found some errors and corrected them. The unit did not catch the errors on the boot-up check-disk. So I guess my question is.. what does running check-disk do differently than from when it boots up and checks disk? Really, wouldn’t it be better to run the complete check-disk on bootup? Might take longer, but I’d rather that than the alternative.
What kind of experiences with bad flash disks have you people had?
the check disk sometimes gives out misleading messages, errors corrected often simply means that something had changed. We will improve it, meanwhile don’t worry about it
Do you know when work on check-disk will be completed?
The problem we have is that when we the flash card corrupts itself we normally lose the license as well. We’re just trying to mitigate corrupt flash cards and/or figure out why they happen and how we can fix them.
LILO 22.3.4 Loading System…
BIOS data check successful
/sbin/initKernel panic: Attempted to kill init!
: error while lo ading shared libraries: libmsg.so: cannot open shared object file: Input/output error
Heh! I was just searching the site to see if I could find some information on restoring an RB230 unit that had a handful of power glitches and ended up unable to boot. Our guys are standing at the bottom of the tower now, scratching their heads. It’s 20 meters up and 56 km horizontally to reach this gizmo, pretty typical for our network, so the sooner we can stop worrying, the better!
BTW, if we disable any and all logging to “disk” on units equipped w/CF cards, is it safe to assume we’ll have a lower chance of corruption if they are not halted properly?