cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2114
Views
0
Helpful
5
Replies

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

PK99
Level 1
Level 1

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
Level 1
Level 1

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

5 Replies 5

PK99
Level 1
Level 1

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.

 

smilstea
Cisco Employee
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.

Dear smilstea,

Our ASR-9001 had a broken eUSB flash module, after replacing it with a 8Gbyte eUSB module and turbobooting onto disk0: we do not seem to get the 3rd partition called "harddisk". We seem to automatically get "disk0:" and "disk0a" but we do not seem to get "harddisk".

When trying to fix i see we lack "dnf" features in the "run" shell when booted into the device, what we want to try is to format the last partition and name it "harddisk".

#
# df -h
/dev/eusb00t77 3.4G 367M 3.0G 11% /dev/disk0:/
/dev/eusb00t78 880M 348K 880M 1% /disk0a:/
/dev/fs1p1 28M 23K 28M 1% /configflash:
/dev/fs0p1 43M 22M 21M 52% /bootflash:
/nvram: 219K 28K 191K 13%
/nvram:/classic-rom 219K 28K 191K 13%
/nvram-raw: 284K 0 284K 0%

#

We also tried your rommon variables in the hope it will create "harddisk",  but unfortunately it is not creating/formatting the harddisk:

 

 

rommon B4 > priv
You now have access to the full set of monitor commands.
Warning: some commands will allow you to destroy your
configuration and/or system images and could render
the machine unbootable.
rommon B5 > diswd
Watchdog Disabled
rommon B6 > MEDIA_FORMAT=harddisk:,qnx4,partition
rommon B8 > set
PS1=rommon ! >
IOX_ADMIN_CONFIG_FILE=
ACTIVE_FCD=1
IP_ADDRESS=172.19.1.2
IP_SUBNET_MASK=255.255.255.0
DEFAULT_GATEWAY=172.19.1.1
TFTP_RETRY_COUNT=4
TFTP_TIMEOUT=6000
TFTP_SERVER=172.19.1.1
TFTP_MGMT_INTF=1
TFTP_BLKSIZE=1400
TFTP_FILE=asr9k-mini-px.vm-6.6.3
MIRROR_ENABLE=
TURBOBOOT=
BSI=0
BOOT=disk0:asr9k-os-mbi-6.6.3/0x100000/mbiasr9k-rp.vm,1;
CLUSTER_NO_BOOT=
BOOT_DEV_SEQ_CONF=
BOOT_DEV_SEQ_OPER=
MEDIA_FORMAT=harddisk:,qnx4,partition
IOX_CONFIG_FILE=/harddisk:/no-config
?=0
rommon B9 >
rommon B9 >
rommon B9 >
rommon B9 > i
ÏKcãúcçëcgëóþ:N×ËãËãËçãsRÔ¤¨hUÍѵ½½ÑÍÑÉ
Á±²UÉÍ¥½¹r¢B¢ºÒÊJÚ5%ZõÕªêʪŠ©H¨hÔ
WÉ¥B¥ÊÊ¢j¢å¥Í½åÍѵͱJå¹jRÔ¤¨hÔ«
W«$­$¦SÉT¬)¤&M§M&H¬^H·Z²]ººa

Starting Initialization of FMAN0
***PPC PROCESSOR REV=2 load FMAN ucode***
Loading ucode for FMAN0, size: 6992, ver: 101.08.00
Starting Initialization of FMAN1
***PPC PROCESSOR REV=2 load FMAN ucode***
Loading ucode for FMAN1, size: 6992, ver: 101.08.00
Serdes Protocol: 0x10

CPU Reset Reason = 0x0001
Initializing GIGE SW...
PPC P40X0 (partnum 0x8023), Revision 02.00, (Core Version 02.00)

Sys Clock: 100 Mhz
Core Clock: 1500 Mhz
Plat Clock: 800 Mhz
LBC Clock: 25 Mhz
MEM Clock: 1300 Mhz

 

System Bootstrap, Version 2.04(20140227:092320) [ASR9K ROMMON],
Copyright (c) 1994-2014 by Cisco Systems, Inc.

Compiled Thu 27-Feb-14 14:53 by nidutta

Board Type: 0x100401
CPU Board => Rev: 0x3
=========
FPGA ver: 01.0f
CBC: 16.72


DTI programmed with latest image

TIMEX programmed with latest image
MLAN init done: ready to connect to the network
BCM5482PhyInit () : Port 0 --> SFP Not present
BCM5482PhyInit () : Port 1 --> SFP Not present

set_chassis_type: chassis_type=0xef0400 found=TRUE
ASR9001E (P40X0 PPC) RSP platform with 8192 Mb of main memory

program load complete, entry point: 0x100000, size: 0x2ac20
Set baud rate to: 9600
program load complete, entry point: 0x100000, size: 0x2ac20
Set baud rate to: 9600
MBI Candidate = disk0:asr9k-os-mbi-6.6.3/0x100000/mbiasr9k-rp.vm

CARD_SLOT_NUMBER: 0
CPU_INSTANCE: 1
MBI Validation starts ...

Disabling both Mgt LAN ports
Enabling Cluster Port 0 and disabling Port 1
BCM5482 cluster port-1 reset done !!
Port 0. SFP Not Ready (0:0). Init failed

dtsec_init_hw: configuring DTSEC (port for: 1GB, Full Duplex
Interface link changed state to UP.
Interface link state up.

MBI validation sending request.
HIT CTRL-C to abort
..........
No MBI confirmation received from dSC


CARD_SLOT_NUMBER: 0
CPU_INSTANCE: 1
MBI Validation starts ...
Enabling Cluster Port 1 and disabling Port 0
BCM5482 cluster port-0 reset done !!
Port 1. SFP Not Ready (0:0). Init failed

dtsec_init_hw: configuring DTSEC (port for: 1GB, Full Duplex
Interface link changed state to UP.
Interface link state up.

MBI validation sending request.
HIT CTRL-C to abort
.........
No MBI confirmation received from dSC

AUTOBOOT: Boot string = disk0:asr9k-os-mbi-6.6.3/0x100000/mbiasr9k-rp.vm,1;
AUTOBOOT: autobootstate=0, autobootcount=0, cmd=boot disk0:asr9k-os-mbi-6.6.3/0x100000/mbiasr9k-rp.vm

Boot Status 16
program load complete, entry point: 0x100000, size: 0x2ac20
Set baud rate to: 9600

MBI size from header = 22008220,Bootflash resident MBI filesize = 22008220
....................................................................................
program load complete, entry point: 0x2037e0, size: 0x14fc29c

Boot Status 17
Config = SMP, Running = SMP
Board type: 0x00100401
Card Capability = 0x00000000
###############################################################################################################
BSP: Board type : ASR9K-RSP-I
tracelogger: starting tracing in background ring mode
tracelogger running with args: -startring -F 1 -F 2
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 XR Software for the Cisco XR ASR9K, Version 6.6.3
Copyright (c) 2019 by Cisco Systems, Inc.
Format requested 'harddisk:' / partition option 'QNX4'
Sep 18 08:20:44.605: Install Setup: Booting with committed software
Initializing Punt-switch ...
Initializing Punt-switch ...
Set RP CPU Cluster port in DSA mode
Init STP group for Cluster ports forwarding state control done
Cluster: Boot Request Filter configured
Cluster: Control Link monitor proto filter configured
Successfully initialized punt-switch(26 ports).
SPP has connected to PAKMAN....
SPP registered CPU port 4 with DPAA
SPP Port Idx 0 MAC addr --> 00:70:72:00:00:08

Do you know how to fix this missing "harddisk" ? 

 

Many thanks in advance.

Tim Edsge Teenstra 

 

What do you mean you replaced the eUSB? It is not a field replaceable part. I also believe that there are two devices, one for disk0/1 and one for harddisk, they are on the same usb controller though.

 

Sam

 

Hi

Thanks for your answer! I really appreciate it. 

Our ASR-9001 router was not booting anymore, so we replaced the 8gbe eUSB module that is inside the router. It is replaceable just like the flash modules of the ISR4xxx series. 

Here I read  :  https://www.cisco.com/c/en/us/support/docs/routers/asr-9000-series-aggregation-services-routers/200135-Aggregation-Services-Router-9001-ASR-90.html#anc8

The ASR-9001 has one Embedded USB (eUSB) Flash device that is partitioned as disk0: (4 GB), disk0a: (1 GB) and harddisk: (3 GB). There is an option to have external USB that is mounted as disk1: when inserted. There is 2x64 MB NOR


When we installed the router we have turbobooted and fixed the router it is booting and the turboboot procedure "fixed" two out of three partitions (disk0,disk0a) 

Now the shell when running 32 bit XR 6.6.3 does not allow us to create the last partition (as a Juniper MX router shell would allow to to modify create and format partitions) 

Here is the eUSB module inside the ASR-9001 router that we replaced : 

ASR-9001.png


So you mean if a removable eUSB module breaks a expensive ASR-9001 router is not fixable since it is stated it is not replacable?, I have always managed to fix broken flash on what ever router and switch so long it is ofc removable....

  

 

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: