the problem my company tell

baselzind · ‎05-18-2016

whenever i enter the command CORESW#dir on my "WS-C6509-E " with two Supervisor Engine 720 i get this message %Error opening sup-bootflash:/ (Bad device info block) , anyone have any idea what is wrong?

Mark Malone · ‎05-18-2016

Are you getting it on the slave sup aswell , sounds as if the flash is corrupted or failed

dir slave sup-bootflash:

if the slave is still working you could format the primary flash card and then copy over the image from the slave to the primary

did you make any changes to the IOS recently newer version ?

Do you have any spare flash cards that you know are good you could use

baselzind · ‎05-19-2016

i tried

CORESW#dir slave

%Error opening sup-bootflash:/slave (Bad device info block)

but when i type "#show bootflash:"

it shows content of the flash?

Mark Malone · ‎05-19-2016

can you post the dir all-filesystems

did you check any of the flash cards in a card reader to see if its corrupt or do you have any spares to put new image on and install

baselzind · ‎05-19-2016

the supervisor engine disk 0 and disk 1 are empty unfortunately on both supervisors , the dir all-filesystems is as following;

CORE#dir
%Error opening sup-bootflash:/ (Bad device info block)
CORE#dir all
CORE#dir all-filesystems
Directory of system:/

2 dr-x 0 <no date> memory
1 -rw- 42577 <no date> running-config
12 dr-x 0 <no date> vfiles

No space information available
Directory of sup-microcode:/

1 -r-- 3662666 <no date> CWPA_version_10.10
2 -r-- 4932966 <no date> CWTLC_version_10.10
3 -r-- 4140286 <no date> CWPA2_version_10.10
4 -r-- 13129202 <no date> DRACO2_MP
5 -r-- 5494530 <no date> CHEVYS-LC
6 -r-- 6237762 <no date> C2LC
7 -r-- 2344014 <no date> MACEDON
8 -r-- 382546 <no date> LCP_LX10100
9 -r-- 353418 <no date> LCP_LX1000
10 -r-- 380732 <no date> LCP_AX1000
11 -r-- 353546 <no date> LCP_AX10100
12 -r-- 343710 <no date> LCP_CPFAB
13 -r-- 663262 <no date> LCP_CPGBIT
14 -r-- 658830 <no date> LCP_CP10G
15 -r-- 729054 <no date> LCP_CPMBIT2
16 -r-- 813166 <no date> LCP_CPMBIT

44620202 bytes total (0 bytes free)
Directory of const_nvram:/

1 -rw- 4124 <no date> vlan.dat

129004 bytes total (124880 bytes free)
Directory of nvram:/

1918 -rw- 42577 <no date> startup-config
1919 ---- 5 <no date> private-config
1920 -rw- 42577 <no date> underlying-config
1 ---- 49 <no date> persistent-data
2 ---- 4 <no date> rf_cold_starts
3 -rw- 0 <no date> ifIndex-table

1964024 bytes total (1918318 bytes free)
Directory of bootflash:/

1 -rwx 45475412 Jun 15 2009 18:02:17 +03:00 s72033-psv-mz.122-18.SXD7b.bin

65536000 bytes total (20060460 bytes free)
Directory of slavenvram:/

1918 -rw- 42577 <no date> startup-config
1919 ---- 5 <no date> private-config
1920 -rw- 42577 <no date> underlying-config
1 ---- 51 <no date> persistent-data
2 ---- 4 <no date> rf_cold_starts
3 -rw- 0 <no date> ifIndex-table

1964024 bytes total (1918318 bytes free)
Directory of slaveconst_nvram:/

1 -rw- 4124 <no date> vlan.dat

129004 bytes total (124880 bytes free)
Directory of slavebootflash:/

No files in directory

65536000 bytes total (65536000 bytes free)
Directory of dfc#2-bootflash:/

No files in directory

15990784 bytes total (15990784 bytes free)
Directory of dfc#9-bootflash:/

No files in directory

15990784 bytes total (15990784 bytes free)
Directory of dfc#3-bootflash:/

No files in directory

15990784 bytes total (15990784 bytes free)
Directory of dfc#4-bootflash:/

1 -rw- 242340 Nov 30 1999 03:00:32 +03:00 crashinfo_19991130-000032

15990784 bytes total (15748316 bytes free)

Mark Malone · ‎05-19-2016

How did this happen do you know , any software upgrades/downgrades as using the wrong ios can cause this as some versions don't support sup-bootdisks, if its not that you may have hit serious hardware issue and should probably involve TAC if you have support on it , could be bad memory as well

what you could try on the sup is tftp a new working image to it even though it says bad block if its just corrupted it should overwrite the flash

copy tftp://1.1.1.1/s72033-adventerprisek9_wan-mz.122-33.SXJ6.bin sup-bootdisk:

baselzind · ‎05-19-2016

im confused about the 6509 flash , is the sup-bootflash the active supervisor flash while the bootflash is the standby supervisor flash?

Mark Malone · ‎05-19-2016

the sup-bootdisk is the sup-bootfash

sup-bootflash: This is the flash installed on the Supervisor's switch processor and is readable at initial boot and when the IOS code is loaded.

bootflash: This is the route processor's flash and is installed on the MSFC daughter card on the supervisor 720 module. It is not readable at initial boot and is only accessible after the Supervisor has initially booted.

baselzind · ‎05-21-2016

i guess if sup-bootflash is corrupted then the core switch wont boot at the next restart? also how can i check if the second standby supervisor bootflash and sup-bootflash is intact , like how can i show it's content?

Mark Malone · ‎05-23-2016

Try change the boot statements to bootdisk if your bootdisk is large enough to store the ios put 1 in there and boot from there or try put a CF card in disk0 and boot from there avoid the corrupted bootflash(s)

for redundant checks just put slave in front of the command

dir slavesup-bootflash:

boot system flash sup-bootdisk:/s72033-adventerprisek9_wan-mz.122-33.SXI13.bin

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

    1 -rw-    33554432 Jan 27 2014 17:11:30 +00:00 sea_console.dat
    2 -rw-    33554432 Jun 27 2008 23:18:56 +00:00 sea_log.dat
    3 -rw-    78274052 Sep 21 2008 04:37:12 +00:00 s72033-advipservicesk9_wan-mz.122-33.SXH3.bin

baselzind · ‎05-23-2016

you mean that normally the core would boot from sup-bootflash and i could make it boot from the bootflash?

i was able to show files from the slavebootflash and slavesup-bootflash , cant i simply switch to the other supervisor and make it the primary? is that possible while it is operational? or it needs a restart

Mark Malone · ‎05-23-2016

when its an mfsc daughter card you can usually boot from multiple locations not just the sup-bootflash , if the standby supervisor is still working you could fail over onto that yes just check your redundancy is still working correctly between the pair

http://www.itcertnotes.com/2011/08/catalyst-6500-redundant-supervisor-720.html

baselzind · ‎05-23-2016

the secondary sup-bootflash is giving (Bad device info block) as well , does it make sense for both supervisors sup-bootflash to be corrupted?

CORE#dir slavesup-bootflash:
%Error opening slavesup-bootflash:/ (Bad device info block)

Mark Malone · ‎05-23-2016

No it doesn't make sense, that's why I was asking were there any changes done or images installed both should not be corrupted unless something is seriously gone in hardware or you have hit a major software defect

for something as serious as this you should have a case open with Cisco TAC to try and find out exactly what went wrong

baselzind · ‎06-27-2016

the problem my company tell me to leave using cisco tac to the last measure because using tac hurt the company profile , i used show logging and i got this

: %PFREDUN-SP-4-BOOTSTRING_INVALID: The bootfile slavesup-bootflash: is not present in standby

what does it mean?

cant open dir on my core switch???