Wired Intelligent Edge

 View Only
  • 1.  Procurve 5412 Crash

    Posted Apr 01, 2015 01:27 PM

    Had one of my 5412's crash this morning & won't boot

     

    I get this message below when I hyperterm on it while it boots

     

    Can anyone tell me if this means the management module is fubared or is it something else

     

    thanks

     

     

     


    ROM information:
       Build directory: /sw/rom/build/bmrom(t2g)
       Build date:      Jan 13 2009
       Build time:      16:13:20
       Build version:   K.12.17
       Build number:    22577

    0x9eeec20 (tBoot): dosFsLib.c : Malformed boot sector. Offset 0, value 1.
    0x9eeec20 (tBoot): dosFsLib.c : Problem finding volume data, trying to use the n
    ext block as boot block.
    0x9eeec20 (tBoot): dosFsLib.c : Malformed boot sector. Offset 0, value 129.
    0x9eeec20 (tBoot): dosFsLib.c : Ensure this device is formatted and partitions a
    re properly handled.
    0x9eeec20 (tBoot): dosFsLib.c : Malformed boot sector. Offset 0, value 1.
    0x9eeec20 (tBoot): dosFsLib.c : Problem finding volume data, trying to use the n
    ext block as boot block.
    0x9eeec20 (tBoot): dosFsLib.c : Malformed boot sector. Offset 0, value 129.
    0x9eeec20 (tBoot): dosFsLib.c : Ensure this device is formatted and partitions a
    re properly handled.
    Error, unable to autogenerate boot configuration file.
    Could not open Image file


    Bad code in FLASH

     


    Flash memory needs reprogramming or chassis could be faulty.
    Use a PC as the console and perform the update procedure
     by serial Xmodem download of the current Switch Image.
    If unsuccessful w/ downloading, then try replacing chassis.

    HP ProCurve Switch 5412zl (J8698A)
    ROM Build Directory: /sw/rom/build/bmrom(t2g)
            ROM Version: K.12.17
         ROM Build Date: 16:13:20 Jan 13 2009
       ROM Build Number: 22577
            SSC Version: SSC 82 231120050317
            MSI Version: 4
            CSI Version: 5

    Copyright (c) 1995-2005 Hewlett-Packard Company. All rights reserved.

                             RESTRICTED RIGHTS LEGEND

    Use, duplication, or disclosure by the Government is subject to restrictions
    as set forth in subdivision (b) (3) (ii) of the Rights in Technical Data and
    Computer Software clause at 52.227-7013.

        Hewlett-Packard Company, 3000 Hanover Street, Palo Alto, CA 94303

    Enter h or ? for help.

    =>



  • 2.  RE: Procurve 5412 Crash

    Posted Apr 01, 2015 02:12 PM

    It looks like the switch software got corrupted somehow. Maybe a failed update.

     

    The "=>" prompt indicates that you are at the boot loader menu, which is a good sign and likely indicates that the switch is fine.

     

    The first thing to try is to boot to an alternative software version. Use the "jp 1" and "jp 2" commands to boot to primary and secondary. I am hopeful that one of these will work and the switch will fully boot. If that does work, I highly recommend upgrading to newer software.  You are running really old software.

     

    If neither image will boot, you can download new software to the switch using Xmodem. You will need a terminal program capable of Xmodem, like Tera Term. Xmodem isn't fast but it will work. Use the "do" command and then initiate the Xmodem transfer of the software (a .swi file) and then click "Y" on the switch. When it completes, use the "boot" command to boot the switch. 

     

    Your bootrom, K.12.17, will work with the latest software. Go here to download new software: https://h10145.www1.hp.com/Downloads/SoftwareReleases.aspx?ProductNumber=J8697A&lang=en,en&cc=us,us&prodSeriesId=1827663

     

    The manuals can help with this process too.

     

    Please let me know how it goes,

    Eric



  • 3.  RE: Procurve 5412 Crash

    Posted Apr 01, 2015 02:39 PM

    Neither jp 1 or jp 2 will boot the device

     

    Will try a reload & will post the result

     

     

    The s/w is 5yrs old from when we installed Cisco VOIP back when the Vancouver Olympics were happening. It's hard to upgrade the switch s/w when you are a 24/7 operation



  • 4.  RE: Procurve 5412 Crash

    Posted Apr 08, 2015 07:34 AM

    No luck

     

    6+ hrs to try & load the latest s/w & it still won't boot

     


    =>do

    You have invoked the console download utility.
    Do you wish to continue? (Y/N)>Download was successful.

     -- Download for this Product, proceeding --
    pass CRC check (len=16740105)
    0x9eeec20 (tBoot): dosFsLib.c : Malformed boot sector. Offset 0, value 1.
    0x9eeec20 (tBoot): dosFsLib.c : Problem finding volume data, trying to use the n
    ext block as boot block.
    0x9eeec20 (tBoot): dosFsLib.c : Malformed boot sector. Offset 0, value 129.
    0x9eeec20 (tBoot): dosFsLib.c : Ensure this device is formatted and partitions a
    re properly handled.

    ERROR; unable to open image '/cfa0/boot.ini'
    Ready for code execution.
    ERROR: Download was unsuccessful.
    =>

     

     

    Tried a power down

     

     

     

    ROM information:
       Build directory: /sw/rom/build/bmrom(t2g)
       Build date:      Jan 13 2009
       Build time:      16:13:20
       Build version:   K.12.17
       Build number:    22577

    0x9eeec20 (tBoot): dosFsLib.c : Malformed boot sector. Offset 0, value 1.
    0x9eeec20 (tBoot): dosFsLib.c : Problem finding volume data, trying to use the n
    ext block as boot block.
    0x9eeec20 (tBoot): dosFsLib.c : Malformed boot sector. Offset 0, value 129.
    0x9eeec20 (tBoot): dosFsLib.c : Ensure this device is formatted and partitions a
    re properly handled.
    0x9eeec20 (tBoot): dosFsLib.c : Malformed boot sector. Offset 0, value 1.
    0x9eeec20 (tBoot): dosFsLib.c : Problem finding volume data, trying to use the n
    ext block as boot block.
    0x9eeec20 (tBoot): dosFsLib.c : Malformed boot sector. Offset 0, value 129.
    0x9eeec20 (tBoot): dosFsLib.c : Ensure this device is formatted and partitions a
    re properly handled.
    Error, unable to autogenerate boot configuration file.
    Could not open Image file


    Bad code in FLASH

     


    Flash memory needs reprogramming or chassis could be faulty.
    Use a PC as the console and perform the update procedure
     by serial Xmodem download of the current Switch Image.
    If unsuccessful w/ downloading, then try replacing chassis.

    HP ProCurve Switch 5412zl (J8698A)
    ROM Build Directory: /sw/rom/build/bmrom(t2g)
            ROM Version: K.12.17
         ROM Build Date: 16:13:20 Jan 13 2009
       ROM Build Number: 22577
            SSC Version: SSC 82 231120050317
            MSI Version: 4
            CSI Version: 5

    Copyright (c) 1995-2005 Hewlett-Packard Company. All rights reserved.

                             RESTRICTED RIGHTS LEGEND

    Use, duplication, or disclosure by the Government is subject to restrictions
    as set forth in subdivision (b) (3) (ii) of the Rights in Technical Data and
    Computer Software clause at 52.227-7013.

        Hewlett-Packard Company, 3000 Hanover Street, Palo Alto, CA 94303

    Enter h or ? for help.

    =>

     

     

     



  • 5.  RE: Procurve 5412 Crash

    Posted Apr 08, 2015 10:40 AM

    Bummer. I would recommend opening a case with support and getting the chassis replaced.



  • 6.  RE: Procurve 5412 Crash

    Posted Dec 17, 2017 03:38 PM

    I just wanted to say thanks. The do command and xmodem rescued the 2920 I accidentally hosed.

    4.4 hours to write the new firmware!



  • 7.  RE: Procurve 5412 Crash

    Posted Apr 08, 2015 01:26 PM
    rgrace , try this . though it may be for 2920 it should work for 5400 zl switches too.
    http://h20565.www2.hp.com/hpsc/doc/public/display?sp4ts.oid=3901671&docId=emr_na-c03394761&lang=en&cc=us

    Or just try deleting and recreating the boot.ini file

    ==>cd cfa0 ( CFA zero)
    ==> rm boot.INI
    ==> boot/reboot
    ( rebooting will remove and recreate the boot.ini file)

    And remember replacing the chassis might not help, you may need a replacement management module , should the above steps don't work.



  • 8.  RE: Procurve 5412 Crash

    Posted Apr 09, 2015 09:44 AM

    No luck

     

    I get an error code when I try the cd command

     

    cd: error 0xc0009

     

    if I try ls or ll, I get

     

    Can't open "."

     

     

     



  • 9.  RE: Procurve 5412 Crash

    Posted Apr 09, 2015 10:21 AM

    On the newest bootrom, there is an option to erase-all. I don't remember when that was introduced but it would do the same thing as erasign the boot.ini file. It will also delete the config but you may be at that point anyway.

     

    =>erase-all

     

    By the way, replacing the 5400 chassis includes the management module. On the 5400, the mangement module owns the MAC addresses and serial numbers and the sticker resides on the chassis. So while it will work to replace a management module, you end up in a mismatch state and support doesn't like that. :)



  • 10.  RE: Procurve 5412 Crash

    Posted Apr 10, 2015 04:54 PM

    Didn't see your message in time to test

     

    I called warranty service & a replacement management module was sent out

     

    Installed it into the crashed switch & it booted up fine

     

    updated to latest sw & reboot several times & everything looks fine right now

     

    looks to be a few changes in the sw from the old version. At least java is discontinued

     

    thanks for your assistance