Table of Contents
Advertisement
Corrupted Bootflash Recovery
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m .
Specify the IP address of the default gateway.
Step 3
loader> ip default-gateway 172.16.1.1
Address: 172.16.1.2
Netmask: 255.255.255.0
Server: 0.0.0.0
Gateway: 172.16.1.1
Boot the kickstart image file from the required server.
Step 4
loader> boot tftp://172.16.10.100/kickstart-latest
Address: 172.16.1.2
Netmask: 255.255.255.0
Server: 172.16.10.100
Gateway: 172.16.1.1
Booting: /kick-282 console=ttyS0,9600n8nn quiet loader_ver= "2.1(2)"....
............................................Image verification OK
Starting kernel...
INIT: version 2.78 booting
Checking all filesystems..... done.
Loading system software
INIT: Sending processes the TERM signal
Sending all processes the TERM signal... done.
Sending all processes the KILL signal... done.
Entering single-user mode...
INIT: Going single user
INIT: Sending processes the TERM signal
switch(boot)#
The
Issue the init-system command to repartition and format the bootflash.
Step 5
Perform the procedure specified in the
Step 6
Perform the procedure specified in the
Step 7
section on page 6-37
Note
If you do not issue the reload module command when a boot failure has occurred, the active supervisor
module automatically reloads the standby supervisor module within 3 to 6 minutes after the failure (see
the
"Standby Supervisor Boot Alert" section on page
Cisco MDS 9000 Family Configuration Guide
6-38
prompt indicates that you have a usable Kickstart image.
switch(boot)#
to recover the other supervisor module.
"Recovery from the switch(boot)# Prompt" section on page
"Recovering One Supervisor Module With Corrupted Bootflash"
6-27).
Chapter 6
Software Images
OL-6973-03, Cisco MDS SAN-OS Release 2.x
6-35.
Advertisement
Table of Contents
