Symptom

The system will not come up . It will go into a continuous loop. The following log was seen. Jun 15 06:30:37.362: Install Setup: This node was booted with an incorrect MBI v ersion (/bootflash/disk0/asr9k-os-mbi-4.3.4.CSCum70202-1.0.0/0x100000/mbiasr9k-r p.vm) and will now reset to boot with the correct MBI (/bootflash/disk0/asr9k-os -mbi-4.3.4.CSCup10546-1.0.0/0x100000/mbiasr9k-rp.vm) Spawning instdir_show_ltrace -r failed. : No such file or directory Spawning instdir_show_ltrace -Z -r failed. : No such file or directory Spawning inst_rds_show_ltrace -r failed. : No such file or directory [0x11c6f703d] Record Reboot History, reboot cause = 0x4000048, descr = Cause: dS C booted with incorrect MBI Process: in stsetup Traceback: 4ba5d248 4ba5drebooting Jun 15 07:11:13.225: Install Setup: Booting with software activated by previous install operation Jun 15 07:12:07.884: Install Setup: Failed to update the package file system: (2 ) No such file or directory Jun 15 07:12:07.884: Install Setup: Install Setup (pid 356384) has failed to pre pare this node successfully and will now exit: (2) No such file or directory Jun 15 07:12:41.113: Install Setup: Booting with software activated by previous install operation Jun 15 07:13:35.780: Install Setup: Failed to update the package file system: (2 ) No such file or directory Jun 15 07:13:35.780: Install Setup: Install Setup (pid 602144) has failed to pre pare this node successfully and will now exit: (2) No such file or directory Failed to rename debug file, 18, src: /nvram:/sysmgr.log.timeout.Z, target: /nvr am:/prev.sysmgr.log.timeout.Z Jun 15 07:14:04.382 : SYSMGR_LITE: Saving init logs in /nvram:/sysmgr.log.timeou t.Z ... Jun 15 07:14:08.924: Install Setup: Booting with software activated by previous install operation This (D)RP Node is not ready or active for login /configuration Jun 15 07:15:03.534: Install Setup: Failed to update the package file system: (2 ) No such file or directory Jun 15 07:15:03.535: Install Setup: Install Setup (pid 847904) has failed to pre pare this node successfully and will now exit: (2) No such file or directory Active processes: proc/boot/procnto-booke-smp-instr Thread ID 0 on cpu 0 Active processes: asr9k-os-4.3.4.CSCup10546-1.0.0/0x100000/bin/init Thread ID 1 on cpu 1 Active processes: pkg/bin/devb-umass Thread ID 7 on cpu 2 Active processes: pkg/bin/pkgfs Thread ID 2 on cpu 3 [0x550cba66f] Record Reboot History, reboot cause = 0x2c000007, descr = Cause: I NIT: respawn 'instsetup' disabled, exit_code 256, INIT_MAX_SPAWN reached Process : init Traceba ck: 4b8c0248 4[0x551a98a0b] Record crashinfo [0x551c8d123] Record Syslog Starting Initialization of FMAN0 Starting Initialization of FMAN1 MAC link is up. Mgt LAN 0 interface is selected MLAN init done: ready to connect to the network 2015-06-15 07:16:34.933 NOTE: This is NOT a Kernel Crash. This crash was triggered by the process 'init', by calling reboot API. Crash Reason: Cause: INIT: respawn 'instsetup' disabled, exit_code 256, INIT_MAX _SPAWN reached Process: init Traceback: 4b8c0248 4b8c06b8 4b8c0a1c 40008968 4b812400 0 (Cause Code: 0x2c000007) Exception at 0x4b8c0764 signal 5 c=1 f=3 Active process(s): proc/boot/procnto-booke-smp-instr Thread ID 0 on cpu 0 asr9k-os-4.3.4.CSCup10546-1.0.0/0x100000/bin/init Thread ID 1 on cpu 1 pkg/bin/devb-umass Thread ID 7 on cpu 2 pkg/bin/pkgfs Thread ID 2 on cpu 3 REGISTER INFO r0 r1 r2 r3 R0 4b8c0760 3ff7ef00 5000f310 00000003 r4 r5 r6 r7 R4 28000007 50019844 3ff7eed8 00000000 r8 r9 r10 r11 R8 273d4800 00000000 378d3100 ec00656c r12 r13 r14 r15 R12 4b8f3c54 5000f310 00000000 00000000 r16

Conditions

ASR9001 4.3.4/PIE/SMU --> 4.3.4 SMU Occurs when 4.x.x (not 4.3.4) packages are present in the system. It is recommended to remove all 4.x.x packages before activating any smu or pie.

Workaround

No workaround. If system goes for a reload and is stuck then only option is to turbo boot. If activation of a smu/pie fails then please try to remove older version packages using install remove.

Further Problem Description