cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2830
Views
5
Helpful
5
Replies
Highlighted
Beginner

6509 BOOTSTRING_INVALID The bootfile slavedisk0:_is not present in standby

Hi All,

Can anyone explain me what is this error? The bootfile slavedisk0:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin is not present in standby.

Please see below my switch logs, is it ok that disk0: is not connected?

A# sh bootvar
BOOT variable = disk0:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin,12;sup-bootdisk:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin,1;sup-bootdisk:s3223-ipbasek9-mz.122-18.SXF8.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2102

Standby is up
Standby has 227328K/34816K bytes of memory.

Standby BOOT variable = disk0:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin,12;sup-bootdisk:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin,1;sup-bootdisk:s3223-ipbasek9-mz.122-18.SXF8.bin,1;
Standby CONFIG_FILE variable does not exist
Standby BOOTLDR variable does not exist
Standby Configuration register is 0x2102

#dir disk0:

%Error opening disk0:/ (No such device)

#dir sup-bootdisk:
Directory of sup-bootdisk:/

    1  -rw-    27267012  Jan 18 2006 09:52:14 +08:00  s3223-ipbasek9-mz.122-18.SXF.bin
    2  -rw-    28005828  Oct 23 2007 22:13:36 +08:00  s3223-ipbasek9-mz.122-18.SXF8.bin
    3  -rw-    49016324  Jul 24 2012 10:59:38 +08:00  s3223-ipservicesk9_wan-mz.122-18.SXF16.bin

255954944 bytes total (151662592 bytes free)

2 ACCEPTED SOLUTIONS

Accepted Solutions
Highlighted

Hi Denz,

Thanks for your kind response. If i undestood your question correctly., please see the below clarification.

The congfig register is set as 0x2102 any vlaue from 2102 to 210F tells the router to use the boot commands specified in NVRAM.

Your boot sequence is follows,

boot system disk0:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin

boot system flash sup-bootdisk:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin

boot system flash sup-bootdisk:s3223-ipbasek9-mz.122-18.SXF8.bin

So, the system will try to boot the image from disk0: first, in case if fails, then it will try to check next sequence, our case it is sup-bootdisk:, if it find the valid image from second statement, it will boot successfully or if it fails to find the image from all three statement, then will go to rommon mode.

If you need more clarification, could you brief me about your question again. Sorry for the inconvenience.

Regards,

Aru

*** Please rate if the post is useful ***

Regards, Aru *** Please rate if the post useful ***

View solution in original post

Highlighted

Hi Denz,

Sorry for the late response. Please see my comments below,

  • Yes, as per your boot sequence configuration, If the disk0: fails, still it will try to load image from sup-bootdisk:
  • Re-insertion of CF doesnot impact any service after switch boot up. We shouldnt remove CF only during the switch bootup time (when we set the booting sequece from disk0:)

Please see the supported compact flash for Sup32

http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/prod_bulletin0900aecd801ff3ee.html

The below commands used for erasing, deleting, and recovering files depend on the class of the filesystem.

Disk0: is a Class C file system and bootflash:, slot0:, and sup-bootflash: are Class A file systems.

  • delete - "Marks" files as deleted, but the files still occupy space in Flash memory. Use the undelete command to recover these files later.
  • squeeze - Permanently removes all of the files marked "deleted" or "error" from the specified Flash memory device. These files can no longer be recovered. The squeeze operation can take as long as several minutes if it needs to erase and rewrite most of the Flash memory space on a PCMCIA card.
  • format - Erases all of the files on a Flash device.

          Ex: Switch# format disk0:

  • mkdir - To create a new directory in a Class C Flash filesystem.
  • rmdir - To remove an existing directory in a Class C Flash filesystem.
  • rename - To rename a file in a Class C Flash filesystem.
  • fsck [/no confirm]{disk0: | disk1: | flash:} - To perform a file system check and to repair corruptions

Refer:

https://supportforums.cisco.com/docs/DOC-3654

http://www.cisco.com/en/US/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml#classc

Regards,

Aru

*** Please rate if the post is useful ****

Regards, Aru *** Please rate if the post useful ***

View solution in original post

5 REPLIES 5
Highlighted
Cisco Employee

Hi,

Error message:
The bootfile slavedisk0:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin is not present in standby.

  • This is indicates that specified image is not avilable on slavedisk0:
  • When you see the boot variable on standby supervisor, you have specified that disk0:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin, please verify #dir slavedisk0: whether do you have particular image. If not avilable, plese copy the image to slavedisk0:

    

Standby BOOT variable = disk0:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin,12;sup-bootdisk:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin,1;sup-bootdisk:s3223-ipbasek9-mz.122-18.SXF8.bin,1;

Note:

On the active SUP:
disk0:
is the CF card slot in the SUP
bootflash: is flash memory on the RP
sup-bootdisk: or sup-bootflash: (depend on the version) - flash memory on the SP

On Standby SUP:
slavedisk0:
is the CF card slot on the standby SUP.
slavebootflash: is flash memory on RP
slavesup-bootdisk or slavesup-bootflash is the flash memory on the SP

Problem 2:

#dir disk0:
%Error opening disk0:/ (No such device)

  • Try to remove and reinsert the disk0: then check the status
  • To perform a file system check and to repair corruptions, use the fsck command in privileged EXEC mode.
    fsck [/no confirm]{disk0: | disk1: | flash:}
  • Switch# format disk0:
  • Issue the format disk0: command in order to format CompactFlash on a Supervisor Engine
  • Issue squeeze disk0: command, in order to erase all deleted files from the device.

If you cant read the disk0: still, it might have gone bad, which you need replace it. Before that could you share me below detail,

  1. What type of supervisor insalled on the switch
  2. What is the supervisor redundancy you have configured on the switch.
  3. Configuration on the boot sequence

I can see that you configured, the second boot preference on Standby supervisor as sup-bootdisk:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin, even the switch failes to find the image from disk0:, it will find the image from sup-bootdisk:

Regards,

Aru

*** Please rate if the post is useful ***

Regards, Aru *** Please rate if the post useful ***
Highlighted

Hi Aru,

Thank you for the response. Please see below switch logs that you asked. To my understanding everything will be ok incase there will be failure in active sup-engine because the standby sup-engine configured correctly even though the disk0: is not working properly?

1. sh module

  5    9  Supervisor Engine 32 8GE (Active)      WS-SUP32-GE-3B    

  6    9  Supervisor Engine 32 8GE (Hot)         WS-SUP32-GE-3B

 

2. sh run (supervisor redundancy you have configured on the switch, not sure how to check the config)

!
boot system disk0:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin
boot system flash sup-bootdisk:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin
boot system flash sup-bootdisk:s3223-ipbasek9-mz.122-18.SXF8.bin

!

3. sh red
Redundant System Information :
------------------------------
       Available system uptime = 11 weeks, 5 days, 21 hours, 36 minutes
Switchovers system experienced = 0
              Standby failures = 0
        Last switchover reason = none

                 Hardware Mode = Duplex
    Configured Redundancy Mode = sso
     Operating Redundancy Mode = sso
              Maintenance Mode = Disabled
                Communications = Up

Current Processor Information :
-------------------------------
               Active Location = slot 5
        Current Software state = ACTIVE
       Uptime in current state = 11 weeks, 5 days, 21 hours, 35 minutes
                 Image Version = Cisco Internetwork Operating System Software
IOS (tm) s3223_rp Software (s3223_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXF16, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by cisco Systems, Inc.
Compiled Tue 03-Mar-09 17:44 by kellythw
                          BOOT = disk0:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin,12;sup-bootdisk:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin,1;sup-bootdisk:s3223-ipbasek9-mz.122-18.SXF8.bin,1;
        Configuration register = 0x2102

Peer Processor Information :
----------------------------
              Standby Location = slot 6
        Current Software state = STANDBY HOT
       Uptime in current state = 11 weeks, 5 days, 21 hours, 34 minutes
                 Image Version = Cisco Internetwork Operating System Software
IOS (tm) s3223_rp Software (s3223_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXF16, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by cisco Systems, Inc.
Compiled Tue 03-Mar-09 17:44 by kellythw
                          BOOT = disk0:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin,12;sup-bootdisk:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin,1;sup-bootdisk:s3223-ipbasek9-mz.122-18.SXF8.bin,1;
        Configuration register = 0x2102

Highlighted

Hi Denz,

Thanks for your kind response. If i undestood your question correctly., please see the below clarification.

The congfig register is set as 0x2102 any vlaue from 2102 to 210F tells the router to use the boot commands specified in NVRAM.

Your boot sequence is follows,

boot system disk0:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin

boot system flash sup-bootdisk:s3223-ipservicesk9_wan-mz.122-18.SXF16.bin

boot system flash sup-bootdisk:s3223-ipbasek9-mz.122-18.SXF8.bin

So, the system will try to boot the image from disk0: first, in case if fails, then it will try to check next sequence, our case it is sup-bootdisk:, if it find the valid image from second statement, it will boot successfully or if it fails to find the image from all three statement, then will go to rommon mode.

If you need more clarification, could you brief me about your question again. Sorry for the inconvenience.

Regards,

Aru

*** Please rate if the post is useful ***

Regards, Aru *** Please rate if the post useful ***

View solution in original post

Highlighted

Hi Aru,

Just asking if it will load the image if disk0: is not working.  I check the switch and see that both CF2 is not working because of output below.

#dir disk0:

%Error opening disk0:/ (No such device)

#dir slavedisk0:

%Error opening slavedisk0:/ (No such device)

Also re-inserting the CF is not service affecting?

Any troubleshoot command I need to know because I have only remote access?

Highlighted

Hi Denz,

Sorry for the late response. Please see my comments below,

  • Yes, as per your boot sequence configuration, If the disk0: fails, still it will try to load image from sup-bootdisk:
  • Re-insertion of CF doesnot impact any service after switch boot up. We shouldnt remove CF only during the switch bootup time (when we set the booting sequece from disk0:)

Please see the supported compact flash for Sup32

http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/prod_bulletin0900aecd801ff3ee.html

The below commands used for erasing, deleting, and recovering files depend on the class of the filesystem.

Disk0: is a Class C file system and bootflash:, slot0:, and sup-bootflash: are Class A file systems.

  • delete - "Marks" files as deleted, but the files still occupy space in Flash memory. Use the undelete command to recover these files later.
  • squeeze - Permanently removes all of the files marked "deleted" or "error" from the specified Flash memory device. These files can no longer be recovered. The squeeze operation can take as long as several minutes if it needs to erase and rewrite most of the Flash memory space on a PCMCIA card.
  • format - Erases all of the files on a Flash device.

          Ex: Switch# format disk0:

  • mkdir - To create a new directory in a Class C Flash filesystem.
  • rmdir - To remove an existing directory in a Class C Flash filesystem.
  • rename - To rename a file in a Class C Flash filesystem.
  • fsck [/no confirm]{disk0: | disk1: | flash:} - To perform a file system check and to repair corruptions

Refer:

https://supportforums.cisco.com/docs/DOC-3654

http://www.cisco.com/en/US/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml#classc

Regards,

Aru

*** Please rate if the post is useful ****

Regards, Aru *** Please rate if the post useful ***

View solution in original post

Content for Community-Ad