cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
372
Views
0
Helpful
2
Replies
PK99
Beginner

Is there a way to format harddisk, disk0, etc in Rommon on a ASR9001

We have an ASR-9001 and it was running 5.1 and we attempted to turboboot unit to 6.4.1. Then this happened.

 

RP/0/RSP0/CPU0:Apr 19 08:04:04.410 : cfgmgr-rp[158]: %MGBL-CONFIG-0-INIT_FAILURE : Configuration Manager was unable to initialize the Admin Commit Database module. Error: 'No such file or directory'. Initialization will be tried again after 60 seconds.
RP/0/RSP0/CPU0:Apr 19 08:04:19.749 : shelfmgr[377]: %PLATFORM-SHELFMGR-3-FSMTIMEOUT_RESET : Node 0/0/CPU0 is reset due to failed bootup. Node state was: 1 Timeout ID: 10
RP/0/RSP0/CPU0:Apr 19 08:04:30.096 : obflmgr[78]: %OS-OBFLMGR-3-RECORD_TOO_SHORT : Too short record size:0 for harddisk:/temp_static_data record at offset:0. The file contents might be corrupted.
RP/0/RSP0/CPU0:Apr 19 08:04:30.098 : obflmgr[78]: %OS-OBFLMGR-3-RECORD_TOO_SHORT : Too short record size:0 for harddisk:/volt_static_data record at offset:0. The file contents might be corrupted.
RP/0/RSP0/CPU0:Apr 19 08:04:32.119 : obflmgr[78]: %OS-OBFLMGR-3-RECORD_TOO_SHORT : Too short record size:0 for harddisk:/temp_cont record at offset:0. The file contents might be corrupted.
RP/0/RSP0/CPU0:Apr 19 08:04:36.238 : obflmgr[78]: %OS-OBFLMGR-3-RECORD_TOO_SHORT : Too short record size:0 for harddisk:/volt_cont record at offset:0. The file contents might be corrupted.
RP/0/RSP0/CPU0:Apr 19 08:05:04.412 : cfgmgr-rp[158]: %MGBL-CONFIG-0-INIT_FAILURE : Configuration Manager was unable to initialize the Admin Commit Database module. Error: 'No such file or directory'. Initialization will be tried again after 60 seconds.

 

***************

Then once IOS boots the following happens

 

This (D)RP Node is not ready or active for login /configuration
RP/0/RSP0/CPU0:Apr 19 08:10:04.422 : cfgmgr-rp[158]: %MGBL-CONFIG-0-INIT_FAILURE : Configuration Manager was unable to initialize the Admin Commit Database module. Error: 'No such file or directory'. Initialization will be tried again after 60 seconds.
Apr 19 08:10:22.255 : TURBOBOOT: Failed: Admin configuration still not done after 595 seconds. Giving up...
Apr 19 08:10:22.258 : TURBOBOOT: Admin Config completed
Apr 19 08:10:22.271 : TURBOBOOT: Resetting TURBOBOOT rommon variable to (TURBOBOOT=).
Apr 19 08:10:22.302 : TURBOBOOT: Setting config-register to NOT autoboot the router and NOT disable send break.
Apr 19 08:10:22.359 : TURBOBOOT: Turboboot failed: the system may be in an inconsistent state. THE ROUTER WILL NOT BE REBOOTED.


Apr 19 08:10:22.361 : TURBOBOOT: Exiting with 2952343552: 'Turboboot' detected the 'fatal' condition 'The admin configuration was not completed'


ios con0/RSP0/CPU0 is now available

 

 

Press RETURN to get started.

RP/0/RSP0/CPU0:Apr 19 08:11:04.425 : cfgmgr-rp[158]: %MGBL-CONFIG-0-INIT_FAILURE : Configuration Manager was unable to initialize the Admin Commit Database module. Error: 'No such file or directory'. Initialization will be tried again after 60 seconds.
RP/0/RSP0/CPU0:Apr 19 08:12:04.427 : cfgmgr-rp[158]: %MGBL-CONFIG-0-INIT_FAILURE : Configuration Manager was unable to initialize the Admin Commit Database module. Error: 'No such file or directory'. Initialization will be tried again after 60 seconds.
RP/0/RSP0/CPU0:Apr 19 08:13:04.429 : cfgmgr-rp[158]: %MGBL-CONFIG-0-INIT_FAILURE : Configuration Manager was unable to initialize the Admin Commit Database module. Error: 'No such file or directory'. Initialization will be tried again after 60 seconds.
RP/0/RSP0/CPU0:Apr 19 08:14:04.431 : cfgmgr-rp[158]: %MGBL-CONFIG-0-INIT_FAILURE : Configuration Manager was unable to initialize the Admin Commit Database module. Error: 'No such file or directory'. Initialization will be tried again after 60 seconds.

******************

The this happens

 

!!!!!!!!!!!!!!!!!!!! NO root-system username is configured. Need to configure root-system username. !!!!!!!!!!!!!!!!!!!!

--- Administrative User Dialog ---


Enter root-system username:

% Entry must not be null.

Enter root-system username:

% Entry must not be null.

Enter root-system username:

% Entry must not be null.

Enter root-system username: RP/0/RSP0/CPU0:Apr 19 08:15:04.433 : cfgmgr-rp[158]: %MGBL-CONFIG-0-INIT_FAILURE : Configuration Manager was unable to initialize the Admin Commit Database module. Error: 'No such file or directory'. Initialization will be tried again after 60 seconds.


% Entry must not be null.

Enter root-system username:

% Entry must not be null.

Enter root-system username: root
Enter secret:
Enter secret again: RP/0/RSP0/CPU0:Apr 19 08:15:11.155 : exec[65581]: %MGBL-CONFIG-4-DB_DISK_FAILURE : Failed to create directory '/disk1:'. Error: 'No such file or directory'. Please check for problems with the boot device.

Could not commit admin config.
Enter root-system username: root
Enter secret:
Enter secret again: RP/0/RSP0/CPU0:Apr 19 08:15:29.270 : exec[65581]: %MGBL-CONFIG-4-DB_DISK_FAILURE : Failed to create directory '/disk1:'. Error: 'No such file or directory'. Please check for problems with the boot device.

Could not commit admin config.
Enter root-system username:

 

Keep in mind I had to boot iimage off USB (disk1)

 

Any suggestions?  I believe formating the harddisk or disk0 might fix this

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
PK99
Beginner

Solved it.  Turns out the USB drive had a license file.  Put image on different clean USB and boot off it and now it works.  I supposer the ASR was looking at that license file that was on the USB and didn't like it.  The License file was a back up of a license from a ASR920 so I guess it makes sense that the format/db was incorrect.  But I'm baffled that it was trying to read that.

 

View solution in original post

2 REPLIES 2
PK99
Beginner

Solved it.  Turns out the USB drive had a license file.  Put image on different clean USB and boot off it and now it works.  I supposer the ASR was looking at that license file that was on the USB and didn't like it.  The License file was a back up of a license from a ASR920 so I guess it makes sense that the format/db was incorrect.  But I'm baffled that it was trying to read that.

 

View solution in original post

smilstea
Cisco Employee

Yes you can format from rommon, just dont do a turboboot or password recovery at the same time

 

MEDIA_FORMAT=<device>,<fs_type>,<partition_op>

  • device := disk0:, disk0a:, harddisk:, etc
  • fs_type := fat16, fat32, qnx4, etc
  • partition_op := partition, unpartition, none

 

MBI validation sending request.
HIT CTRL-C to abort
 [CTRL-C]
 MBI Validation terminated prematurely
rommon 1 > set
PS1=rommon ! >
?=0
ACTIVE_FCD=1
BSI=0
BOOT=disk0:hfr-os-mbi-4.0.4/0x100008/mbihfr-rp-x86e.vm,1;
BOOT_DEV_SEQ_CONF=
BOOT_DEV_SEQ_OPER=
rommon 2 > MEDIA_FORMAT=disk0:,QNX4
rommon 3 > sync
rommon 4 > set
PS1=rommon ! >
?=0
ACTIVE_FCD=1
BSI=0
BOOT=disk0:hfr-os-mbi-4.0.4/0x100008/mbihfr-rp-x86e.vm,1;
BOOT_DEV_SEQ_CONF=
BOOT_DEV_SEQ_OPER=
MEDIA_FORMAT=disk0:,QNX4
rommon 5 > reset

Resetting .......

ZJF core processor watchdogs enabled
host board idprom: type=0x100009, pca version=0x4
KJF board idprom: 0x70012d
backplane nvram idprom i2c init not allowed on a SRP, or a bench setup
Satori board:0x100009 PCA Version:4, Revision:96
ZJF scratchpad_reg reset debug offset: 0x0,  total:5
    0 idx=0x0, addr=0xd5000000, val=0x7 - ZJF fpga_rev_reg
    1 idx=0x1, addr=0xd5000028, val=0x2 - ZJF reset_stat_reg
    2 idx=0x2, addr=0xd50000e8, val=0x0 - ZJF error_capture_reg
    3 idx=0x3, addr=0xd5000128, val=0x2 - ZJF prev_reset_stat1_reg
    4 idx=0x4, addr=0xd500012c, val=0x2 - ZJF prev_reset_stat2_reg

x86rmon_kensho_JF_P1_board_init
device B32:D0:F0 does not exist
device B32:D0:F0 10e78086 found
device B33:D0:F0 b33414e4 found
device B34:D0:F0 b33414e4 found
configure bcm unit:0 base addr:0xd0300000
configure bcm unit:1 base addr:0xd0400000
rommonSwitchInit() unit:0, mgmt_eth_vlan == default_vlan, 1
rommonSwitchInit() unit:1, mgmt_eth_vlan == default_vlan, 1
rommonSwitchInit(): MDK initialization OK
Image buffer base addr:0x65bbf010, image size:0x16800000
Total System RAM : 12288 MB
startable_processor_mask=0xf
Nirvana FPGA:
    rev_id: 0x2000d
    fw ready reg: 0x7ff0005
CPU chipset:
Jasper Forest: 1.0
Ibex Peak    : 6
Zen-JF FPGA:
    rev_id: 0x7
    host_status_reg: 0x7
    reset_stat_reg: 0x2
    pch_status_reg: 0xf75
    pwr_status_reg: 0x0
    jf_stat_reg: 0x0

Current image running: Boot ROMB

System Bootstrap, Version 2.06 (20110916:145933) [CRS ROMMON],
Copyright (c) 1994-2011 by Cisco Systems, Inc.

Reading confreg 0x102

..........
MBI validation start.
mbi_file_exist: file found.



<snip>



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 XR Software for the Cisco XR HFR, Version 4.0.4
Copyright (c) 2011 by Cisco Systems, Inc.
Format requested 'disk0:' 'QNX4'
Path=0 - Intel PCH AHCI
 target=0 lun=0     Direct-Access(0) -          STEC MACH8 SSD   Rev: 0698
 target=1 lun=0     Direct-Access(0) -          STEC MACH8 SSD   Rev: 0698
Media storage device /disk0: was formatted due to request.