10-14-2020 09:14 PM
I've got a Cisco C881-K9 router. Older end of life model. Surplus equipment. I had plans to brush up on my IOS config skills. It appears to be stuck in IOS recovery mode by looking at the errors below:
boot: cannot determine first executable file name ondevice "flash:"
% No valid customer configuration file found
% Aborting loading of customer configuration
There is no running startup config. I've erased it and done a reload without success. I've attached the console log below.
Thanks in advance.
Solved! Go to Solution.
10-16-2020 12:59 AM
Hello,
thanks for the update. I don't like giving up on stuff, but the EoL date for this device is 2014, so chances are your router is >10 years old. Which most likely means that indeed it is broken.
10-15-2020 12:08 AM
Hello,
did you try the password recovery procedure (link below) ? I am afraid that is your last option, if that doesn't help, the router is most likely bricked...
https://www.cisco.com/c/en/us/support/docs/routers/800-series-routers/12065-pswdrec-827.html
10-15-2020 07:35 PM
Hi,
Thanks for the suggestion. I gave it a try and ended up with the same result. It appears the unit is bricked.
Thanks for your help anyhow.
10-16-2020 12:59 AM
Hello,
thanks for the update. I don't like giving up on stuff, but the EoL date for this device is 2014, so chances are your router is >10 years old. Which most likely means that indeed it is broken.
10-16-2020 02:32 AM
Reset Button pressed during boot up
if this is not your doing, then maybe the reset button is stuck?
10-16-2020 04:53 PM
Good suggestion! I thought that might have been it. I just push cycled the little button a few times. I can hear the clicking when I depress it so I'm pretty sure now the unit is bricked.
Thanks for the suggestion.
Shane
10-16-2020 04:52 PM
Yeah I hate to give up on this also. It was a given to me free but I suspect its bricked. I was hoping to use it to brush up on my IOS skills. It is a nice little fanless unit. Anyhow thanks for your help on this!
Shane
09-01-2021 05:41 AM
Just had this problem on an 886VA ... I was able to fix it by doing a "erase nvram:" twice ... after doing a "write" I could see that the nvram "startup-confg", which remained valid both on "reload" as well as power cycle ...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide