cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
36703
Views
130
Helpful
22
Replies
Beginner

ISR 4331 does not boot to the image specified

New to IOS-XE but I have a ISR 4331 with two images on the flash. I've changed the configuration register to 0x2102 and I have the "boot system flash:isrxxx" in the startup config. The new image is listed before the old image in the config - but every time the router boots to the old image. Any thoughts?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Hall of Fame Community Legend

boot system flash:isr4300

boot system flash:isr4300-universalk9.03.13.04.S.154-3.S4-ext.SPA.bin

I think this syntax is incorrect.  

Can you try the following: 

config t
no boot system flash:isr4300-universalk9.03.13.04.S.154-3.S4-ext.SPA.bin
boot system flash bootflash:isr4300-universalk9.03.13.04.S.154-3.S4-ext.SPA.bin
end
wr

View solution in original post

Everyone's tags (2)
22 REPLIES 22
Hall of Fame Community Legend

Post the entire bootup

Post the entire bootup process.

Beginner

Here she be

Here she be

Thank you for replying

Hall of Fame Community Legend

boot: unsupported boot device

boot: unsupported boot device "flash"

This one came up.

no valid BOOT image found
Final autoboot attempt from default boot device...
File size is 0x0000001e
Located throughput_monitor_params 
Image size 30 inode num 12, bks cnt 1 blk size 8*512
#
Boot image size = 30 (0x1e) bytes

Unsigned package found,  aborting ...
File size is 0x000001e0
Located tracelogs.189 
Image size 480 inode num 13, bks cnt 1 blk size 8*512

Boot image size = 480 (0x1e0) bytes

Unknown image structure
File size is 0x1bf1afa0
Located isr4300-universalk9.03.16.01a.S.155-3.S1a-ext.SPA.bin 
Image size 468823968 inode num 14, bks cnt 114459 blk size 8*512

And then this.  The error message sounds like the IOS you wanted the appliance to boot is either corrupt or not available. 

Can you please compare the MD5 hash value of the file you've downloaded against the MD5 hash value found in the Cisco website?  Make sure they match.  

Run the command "verify /md5 bootflash:filename.bin" to determine the MD5 hash value is.  Alternatively, if go to the Cisco website and copy the MD5 hash value, go to the router and run use the command "verify /md5 bootflash:filename.bin <MD5 hash value from the Cisco website>".  If the MD5 hash value matches, you should see "Verified!" at the end.

Beginner

Hey Leo,

Hey Leo,

I ran the md5 Verification and it did match what is on Cisco's website. (bafa359295bf28329dbc57bb0ae92c9f) Just to be thorough I also put on a much older image and told the boot system to go with that one. It too, failed

Hall of Fame Community Legend

Hmmmm ... May I ask if you

Hmmmm ... May I ask if you can provide the complete output to the following commands: 

1. sh version; 

2. dir; and

3.  sh run b | i boot

Beginner

Yes Sir

Yes Sir

Highlighted
Hall of Fame Community Legend

boot system flash:isr4300

boot system flash:isr4300-universalk9.03.13.04.S.154-3.S4-ext.SPA.bin

I think this syntax is incorrect.  

Can you try the following: 

config t
no boot system flash:isr4300-universalk9.03.13.04.S.154-3.S4-ext.SPA.bin
boot system flash bootflash:isr4300-universalk9.03.13.04.S.154-3.S4-ext.SPA.bin
end
wr

View solution in original post

Everyone's tags (2)
Beginner

Thank you Leo! You were right

Thank you Leo! You were right - IOS XE wants "bootflash" not just "flash." Everything works fabulous now. 

Hall of Fame Community Legend

Thank you very much for

Thank you very much for providing the feedback and ratings.  :)

Hall of Fame Community Legend

Oh, I forgot to ask:  If you

Oh, I forgot to ask:  If you've upgraded the IOS, did you also upgrade the bootstrap?

Beginner

I had the same problem and

I had the same problem and was simply missing bootflash. Thanks!

Hall of Fame Community Legend

Thanks for the feedback &

Thanks for the feedback & please don't forget to rate our post(s).  

Beginner

Providing bootflash: in the

Providing bootflash: in the filename fixed this issue.  This just seems like an extra step for no reason to me, very...ridiculous to say the least.

Hall of Fame Community Legend

Providing bootflash: in the

Providing bootflash: in the filename fixed this issue.  This just seems like an extra step for no reason to me, very...ridiculous to say the least.

Cisco appliances, particularly routers and supervisor line cards, have their CF partitioned in different ways.  Some use bootflash:, some use flash:.  At the end of the day, without the "bootflash:" (and just using "flash:") instructs the system to look into a partition called "flash" and boot the file there.  Since there is no partition called "flash", then the appliance goes into ROMmon. 

CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards