I was entering in maintanance mode/maintenance/memory and this message appeared below these options:
un/mount flash
init flash
QuoteUnable to retrieve filesystem info (unmounted?)
what does it mean??
I was entering in maintanance mode/maintenance/memory and this message appeared below these options:
un/mount flash
init flash
QuoteUnable to retrieve filesystem info (unmounted?)
what does it mean??
What did you do there in maintenance mode?
After this, it'll give you an option to mount/not mount. Then when you repeat the step to check memory, it'll give you the same message.
Reason why this isn't mounted is after version 2.0, the Kemper OS underwent a major reboot, making it more stable. As a result, some of the maintenance functions were also removed from the reach of ordinary users.
Case in point: the procedure for flashing the Kemper's flash memory and other parameters is no longer required to be done when things go wrong.
I suggest you get out of there and quit screwing around
Display MoreAfter this, it'll give you an option to mount/not mount. Then when you repeat the step to check memory, it'll give you the same message.
Reason why this isn't mounted is after version 2.0, the Kemper OS underwent a major reboot, making it more stable. As a result, some of the maintenance functions were also removed from the reach of ordinary users.
Case in point: the procedure for flashing the Kemper's flash memory and other parameters is no longer required to be done when things go wrong.
I suggest you get out of there and quit screwing around
so, I should not be bothered at all? this is exactly the same message that appeared to you some time ago
topic: Input too hot after 2.1.1 update + Kemper unable to retrieve filesystem info
[Blocked Image: http://imagizer.imageshack.us/a/img11/9424/84tl.jpg]
In the past I already did flash init, format flash and system reset tricks when I first got the profiler, because the monitor out didn't make any sound
a quote from wikpa http://www.wikpa.org/Emergency! :
QuoteDisplay MoreThe initialization of the flash memory was only necessary after a bug in 1.0.5 where a memory corruption bug could also mess up the flash
memory organization. We've all heard about flash memory failures resulting from too many writes, but the Profiler’s flash can be definitely updated several
hundred times. In those cases when a flash memory reset is advisable, and the operation doesn’t bring the expected results, you can try and
update it more than once: the firmware flash has several partitions and the update process will try them one after another. Before you do that,
turn off the unit by leaving it on and pulling the power cord. Then wait1 minute. After that, connect the stick, press and hold the Page
buttons and turn the unit on.timo
That bug no longer exists. Mr CK said in that same thread, "DO NOT FLASH YOUR MEMORY REPEATEDLY". I'd advise other users against it too, reserve this step for absolutely critical fails when nothing else works. Even then, I don't think it has any effect after the changes were made from 2.0 onward.
That bug no longer exists. Mr CK said in that same thread, "DO NOT FLASH YOUR MEMORY REPEATEDLY". I'd advise other users against it too, reserve this step for absolutely critical fails when nothing else works. Even then, I don't think it has any effect after the changes were made from 2.0 onward.
Ok, so I hope that filesystem message is harmless
No more flash init and format flash operations! Thank you!
Yeah, it's harmless. Imagine, I saw that message within a week of getting my Kemper new and I was freaking out!