Cat 6500 - Error opening bootdisk

[graham-lewis]

Hi,

I'm trying to upgrade our production 6509 supervisor 2T 10GE switches from version 15.1(1)SY4 to 15.2(1)SY5. I can copy the image to the slave supervisor with no problem but when I try to copy to the active supervisor I get the following error message:

"%Error opening bootdisk:/s2t54-ipservicesk9-mz.SPA.152-1.SY5.bin (Directory entries are corrupted, please format the disk)"

I'm having the problem with all our production switches and can't copy using TFTP, FTP or from the slavebootdisk: I'm guessing forcing a redundancy switch-over will fix the issue (haven't tried yet) but I'd rather avoid doing this. Has anyone else had this issue and know of a fix or workaround?

Thanks,

Graham

[Reza Sharifi]

Hi,

You may need to do a forced failover to the standby Sup and format the flash.

Have a look at this link:

https://supportforums.cisco.com/t5/lan-switching-and-routing/cat6500-w-sup-720-sup-bootdisk-error/td-p/1734860

HTH

[Leo Laohoo]

---

@graham-lewis wrote:

I'm having the problem with all our production switches and can't copy using TFTP, FTP or from the slavebootdisk:

---

Please clarify what this means.  I am reading this as:  Issue when copying from the slavebootdisk to the sup-bootdisk.  Is this correct?

Another option is to use an SD card or USB since the supervisor card has these options enabled.

[graham-lewis]

Thanks for the replies.

I'm trying to copy the image onto the active bootdisk: and it doesn't matter what method I try, from a TFTP server, an FTP server or from the slavebootdisk: I always get the same error message on the active supervisor, e.g.

router#dir
Directory of bootdisk:/

    1  -rw-    33554432   Aug 5 2013 09:40:40 +01:00  sea_console.dat
    2  -rw-    90845056   Aug 5 2013 09:44:42 +01:00  s2t54-ipbasek9-mz.SPA.151-1.SY1.bin
    3  -rw-    33554432   Aug 5 2013 09:47:38 +01:00  sea_log.dat
    4  drw-           0   Aug 5 2013 09:46:42 +01:00  call-home
    5  -rw-    93666744  Jul 14 2016 14:13:20 +01:00  s2t54-ipservicesk9-mz.SPA.151-1.SY4.bin

1024557056 bytes total (772833280 bytes free)
router#dir slavebootdisk:
Directory of slavebootdisk:/

    1  -rw-    33554432   Aug 5 2013 10:57:28 +01:00  sea_console.dat
    2  -rw-    90845056   Aug 5 2013 11:01:32 +01:00  s2t54-ipbasek9-mz.SPA.151-1.SY1.bin
    3  -rw-    33554432   Aug 5 2013 11:04:28 +01:00  sea_log.dat
    4  drw-           0   Aug 5 2013 11:03:34 +01:00  call-home
    6  -rw-    93666744  Jul 14 2016 14:15:28 +01:00  s2t54-ipservicesk9-mz.SPA.151-1.SY4.bin
    7  -rw-   153512056  May 15 2018 12:00:22 +01:00  s2t54-ipservicesk9-mz.SPA.152-1.SY5.bin

1024557056 bytes total (619347968 bytes free)

router#copy slavebootdisk:s2t54-ipservicesk9-mz.SPA.152-1.SY5.bin bootdisk:
Destination filename [s2t54-ipservicesk9-mz.SPA.152-1.SY5.bin]?
%Error opening bootdisk:/s2t54-ipservicesk9-mz.SPA.152-1.SY5.bin (Directory entries are corrupted, please format the disk)

router#copy tftp: bootdisk:
Address or name of remote host []? 10.10.10.10
Source filename []? s2t54-ipservicesk9-mz.SPA.152-1.SY5.bin
Destination filename [s2t54-ipservicesk9-mz.SPA.152-1.SY5.bin]?
Accessing tftp://10.10.10.10/s2t54-ipservicesk9-mz.SPA.152-1.SY5.bin...
Loading s2t54-ipservicesk9-mz.SPA.152-1.SY5.bin from 10.10.10.10 (via GigabitEthernet7/46): !
%Error opening bootdisk:/s2t54-ipservicesk9-mz.SPA.152-1.SY5.bin (Directory entries are corrupted, please format the disk)

I can copy to the standby supervisor without an issue.

I could accept that the bootdisk: was indeed corrupt if it was a one off but this is affecting all my enterprise production switches (16) which is why I suspect it's something else. The switches are geographically dispersed so the SD or USB option would be very time consuming. 

[Leo Laohoo]

I think this is a bug.

[graham-lewis]

Thanks Leo - I'll raise a TAC case.

[graham-lewis · Accepted solution]

Hi All, FYI I raised a TAC case and a very helpful engineer asked me to run "fsck bootdisk:" which fixed the issue immediately - I don't think I've used that command for 15 or 20 years on a Cisco switch or router! Anyway, thanks for your replies, all sorted now.