Meraki Ms390 "boot: failed to load ms-rpboot.17.09.03m2.SPA.pkg

neompx
New here

Meraki Ms390 "boot: failed to load ms-rpboot.17.09.03m2.SPA.pkg

I have a meraki ms390, today when the device automatically updated the firmware and when restarting, I got this error, and the device kept rebooting, unable to work.
I need help ,
thank you

 

=====

Initializing Hardware......

System Bootstrap, Version 17.5.8r, RELEASE SOFTWARE (P)
Compiled Tue 05/11/2021 9:10:01.17 by rel

Current ROMMON image : Primary
Last reset cause : PowerOn
MS390-48UX platform with 8388608 Kbytes of main memory


BOOT target available .. clear bkup rmonvar if any

boot is : [ boot flash:packages.conf ]
boot: attempting to boot from [flash:packages.conf]
boot: reading file packages.conf
#
################################################################################ ################################################################################ ################################################################################ ################################################################################ ################################################################################ ###########################################################

 

Signature verification failed for key# 1
MCU 802.3bt mode supported: True, BT mod e: True

Both links down, not waiting for other switches
Switch number is 1
Jun 28 0 5:59:26.791: %INSTALL-5-INSTALL_AUTO_ABORT: R0/0: rollback_timer_helper: Install auto abort timer expired: initiating abort

Restricted Rights Legend

Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

Cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

 

Cisco IOS Software [Cupertino], Catalyst L3 Switch Software (CAT9K_IOSXE), Versi on 17.9.2bprd1, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2023 by Cisco Systems, Inc.
Compiled Wed 18-Jan-23 12:48 by mcpre

 

PLEASE READ THE FOLLOWING TERMS CAREFULLY. INSTALLING THE LICENSE OR
LICENSE KEY PROVIDED FOR ANY CISCO SOFTWARE PRODUCT, PRODUCT FEATURE,
AND/OR SUBSEQUENTLY PROVIDED SOFTWARE FEATURES (COLLECTIVELY, THE
"SOFTWARE"), AND/OR USING SUCH SOFTWARE CONSTITUTES YOUR FULL
ACCEPTANCE OF THE FOLLOWING TERMS. YOU MUST NOT PROCEED FURTHER IF YOU
ARE NOT WILLING TO BE BOUND BY ALL THE TERMS SET FORTH HEREIN.

Your use of the Software is subject to the Cisco End User License Agreement
(EULA) and any relevant supplemental terms (SEULA) found at
http://www.cisco.com/c/en/us/about/legal/cloud-and-software/software-terms.html.

You hereby acknowledge and agree that certain Software and/or features are
licensed for a particular term, that the license to such Software and/or
features is valid only for the applicable term and that such Software and/or
features may be shut down or otherwise terminated by Cisco after expiration
of the applicable license term (e.g., 90-day trial period). Cisco reserves
the right to terminate any such Software feature electronically or by any
other means available. While Cisco may provide alerts, it is your sole
responsibility to monitor your usage of any such term Software feature to
ensure that your systems and networks are prepared for a shutdown of the
Software feature.


Jun 28 05:59:31.699: %INSTALL-5-INSTALL_START_INFO: R0/0: install_engine: Starte d install abort

FIPS: Flash Key Check : Key Not Found, FIPS Mode Not Enabled
cisco MS390-48UX (X86) processor with 2331615K/6147K bytes of memory.
Processor board ID Q3EH-8UTE-S22Y
2048K bytes of non-volatile configuration memory.
8388608K bytes of physical memory.
1638400K bytes of Crash Files at crashinfo:.
11264000K bytes of Flash at flash:.

Base Ethernet MAC Address : 38:84:79:22:46:00
Motherboard Assembly Number : 73-19483-01
Motherboard Serial Number : FOC242734V0
Model Revision Number : C0
Motherboard Revision Number : B0
Model Number : MS390-48UX
System Serial Number : xxxxxxxxxxxxxx
CLEI Code Number :


SETUP: new interface Vlan1 placed in "shutdown" stateMM [1] MCU version 225 sw ver 224
MM [2] MCU version 225 sw ver 224


MCU UPGRADE IN PROGRESS... PLEASE DO NOT POWER CYCLE!!

Front-end Microcode IMG MGR: found 4 microcode images for 1 device.
Image for front-end 0: /tmp/microcode_update/front_end/fe_type_6_0 update needed: no
Image for front-end 0: /tmp/microcode_update/front_end/fe_type_6_1 update needed: yes
Image for front-end 0: /tmp/microcode_update/front_end/fe_type_6_2 update needed: yes
Image for front-end 0: /tmp/microcode_update/front_end/fe_type_6_3 update needed: no

Front-end Microcode IMG MGR: Preparing to program device microcode...
Front-end Microcode IMG MGR: Preparing to program device[0], index=0 ...594412 bytes.... Skipped[0].
Front-end Microcode IMG MGR: Preparing to program device[0], index=1 ...578240 bytes.
Front-end Microcode IMG MGR: Programming device 0...rwRrrrrrrw..0%...........................................................................................................10%..........................................................................................................20%............................................................................................................30%...........................................................................................................40%............................................................................................................50%...........................................................................................................60%............................................................................................................70%..........................................................................................................80%.............................................................................................................90%..........................................................................................................100%
Front-end Microcode IMG MGR: Preparing to program device[0], index=2 ...24506 bytes.
Front-end Microcode IMG MGR: Programming device 0...rrrrrrw..0%....10%....20%......30%...40%....50%......60%....70%.....80%....90%....100%w
Wating for MCU to come up .....Rr!
Front-end Microcode IMG MGR: Microcode programming complete for device 0.
Front-end Microcode IMG MGR: Preparing to program device[0], index=3 ...90974 bytes.... Skipped[3].
Front-end Microcode IMG MGR: Microcode programming complete in 380 seconds


MCU UPGRADE COMPLETED!!...
Chassis 1 reloading, reason - Reload command
Jun 28 06:07:02.044: %PMAN-5-EXITACTION: F0/0: pvp: Process manager is exiting: reload fp action requested
Jun 28 06:07:10.939: %PMAN-5-EXITACTION: R0/0: pvp: Process manager is exiting: rp processes exit with reload switch code

 

Initializing Hardware......

System Bootstrap, Version 17.5.8r, RELEASE SOFTWARE (P)
Compiled Tue 05/11/2021 9:10:01.17 by rel

Current ROMMON image : Primary
Last reset cause : SoftwareReload
MS390-48UX platform with 8388608 Kbytes of main memory


BOOT target available .. clear bkup rmonvar if any

boot is : [ boot flash:packages.conf ]
boot: attempting to boot from [flash:packages.conf]
boot: reading file packages.conf
#


boot: failed to load ms-rpboot.17.09.03m2.SPA.pkg
boot: failed to boot file flash:user/packages.conf
ERROR: failed to boot from flash:packages.conf (Not Found)
Please wait while the system restarts.

Initializing Hardware......

5 Replies 5
alemabrahao
Kind of a big deal
Kind of a big deal

This appears to be a hardware issue, you need to open a support case as you may need to RMA.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
neompx
New here

how ? i don't know open a support case , plese help me

alemabrahao
Kind of a big deal
Kind of a big deal

https://documentation.meraki.com/General_Administration/Support/Contacting_Support

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
GreenMan
Meraki Employee
Meraki Employee

You can find all the support options simply by typing 'support' in the search window in Dashboard.  In fact this approach, if you use a decent keyword, will help answer most things Meraki

PhilipDAth
Kind of a big deal
Kind of a big deal

As @alemabrahao said, I think you are going to need an RMA.

 

In desperation:

  • Try removing power from the unit for 30s and re-applying.
  • Try a factory reset.
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels