Firewall will not boot IOS automatically

ISRAdmin
ISRAdmin used Ask the Experts™
on
Hello,
I have a Cisco ASA 5500 series firewall. Last week the firewall lost it's IOS. I used my PC as a TFTP server and TFTP'd the IOS file from another 5500 that i have onto the firewall that dropped it's IOS. Now the only problem i have is that it will not boot to the IOS. It goes into ROMMON every time i reload. If i type "boot" in the ROMMON prompt it will boot just fine to the IOS. I have tried the "boot system flash:/asa722-k8.bin" command but it's still not working. I can see the file in a "sho flash" and if i do a "sho version" it says the system image file is "disk0:/asa722-k8.bin", which all seems right. Why wont this thing boot properly?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Istvan KalmarHead of IT Security Division
Top Expert 2010

Commented:
5505 or 5510 do you have?

Author

Commented:
It's a 5505.
can you provide the output of "show flash" and "show config | i boot" ?

my guess is that you have 2 OS versions in flash, and one is corrupted.  If you have 2 boot statements, it's likely that the bad image is being booted from power on, rather than the good one.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
Here you go, hope this helps.

fw-flightline# sho flash
--#--  --length--  -----date/time------  path
    2  2048        Apr 12 2010 07:37:52  log
    6  2048        Apr 12 2010 07:38:10  crypto_archive
   60  14635008    Apr 12 2010 09:21:52  asa722-k8.bin

fw-flightline# show config | i boot
boot system disk0:/asa722-k8.bin
boot system disk0:/flash

Commented:
try this:
conf t
no config-register
wr mem
reload
Commented:
I do not understand why there is a "boot system disk0: / flash".
Deleting this line should solve the problem.
fw-flightline#no boot system disk0:/flash

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial