Options

am i screwed?

Darthn3ssDarthn3ss Member Posts: 1,096
So i bought a 2650 from ebay, came with 96/16. it powers up but i get this error:
boot: cannot open "flash:"
boot: cannot determine first file name on device "flash:"


it went straight into rom mon with the 96/16. When my new memory arrived (128/32), it still gives the same error, so now i'm guessing that something with the flash may be toast. am i right, or is there something i can do to fix this? i've tried reseating it, switching back to the old memory, etc etc etc.
Fantastic. The project manager is inspired.

In Progress: 70-640, 70-685

Comments

  • Options
    hypnotoadhypnotoad Banned Posts: 915
    not sure -- but from RomMon you can TFTP an image on to flash. Appears to be just a flash problem.
  • Options
    dtlokeedtlokee Member Posts: 2,378 ■■■■□□□□□□
    You need to load an image using the tftpdnld command.
    The only easy day was yesterday!
  • Options
    chrisknightchrisknight Member Posts: 7 ■□□□□□□□□□
    Does the flash have an IOS on it?
  • Options
    Darthn3ssDarthn3ss Member Posts: 1,096
    no. the flash memory is brand new.
    Fantastic. The project manager is inspired.

    In Progress: 70-640, 70-685
  • Options
    mikej412mikej412 Member Posts: 10,086 ■■■■■■■■■■
    Darthn3ss wrote:
    So i bought a 2650 from ebay, came with 96/16. it powers up but i get this error:
    boot: cannot open "flash:"
    boot: cannot determine first file name on device "flash:"
    You're only screwed if we decide to put this post on a TechExams.Net Cisco Forum specific tee-shirt. icon_lol.gif

    But this is one of those things you learn by working with real hardware (or hanging around forums with people using real hardware). icon_lol.gif

    Like the others have said -- load an IOS image onto the flash.
    :mike: Cisco Certifications -- Collect the Entire Set!
  • Options
    Darthn3ssDarthn3ss Member Posts: 1,096
    mikej412 wrote:
    Darthn3ss wrote:
    So i bought a 2650 from ebay, came with 96/16. it powers up but i get this error:
    boot: cannot open "flash:"
    boot: cannot determine first file name on device "flash:"
    You're only screwed if we decide to put this post on a TechExams.Net Cisco Forum specific tee-shirt. icon_lol.gif

    But this is one of those things you learn by working with real hardware (or hanging around forums with people using real hardware). icon_lol.gif

    Like the others have said -- load an IOS image onto the flash.
    well i'v eloaded IOS's before and don't remeber that happening ;D

    yeah its been a while...
    Fantastic. The project manager is inspired.

    In Progress: 70-640, 70-685
  • Options
    Darthn3ssDarthn3ss Member Posts: 1,096
    ios downloaded, tried to boot:
    Unexpected exception to CPUvector 100, PC = 80424E20
    -Traceback= 80424E20 80432E0C 804325AC 80034AB4 80034BAC 80030D14 804307EC 804308E4 803E7978 80320E3C 80321044 803F281C
    
    Writing crashinfo to flash:crashinfo_19930301-000006
    Queued messages:
    *** System received a SegV exception ***
    signal= 0xb, code= 0x100, context= 0x81a6f79c
    PC = 0x80424e20, Vector = 0x100, SP = 0x81c54f50
    
    Fantastic. The project manager is inspired.

    In Progress: 70-640, 70-685
  • Options
    dtlokeedtlokee Member Posts: 2,378 ■■■■□□□□□□
    Might be bad ram, bad flash memory, the IOS image is not for that model or is too large for the amount of memory. Try putting the old ram in and see what happens. Then try changing the flash... see if you can isolate the bad part.
    The only easy day was yesterday!
  • Options
    Darthn3ssDarthn3ss Member Posts: 1,096
    switched flash, used same IOS. didn't work. goign to try another ios now (probably should of done that from the start

    edit: tried a different image on old flash. fail.
    Fantastic. The project manager is inspired.

    In Progress: 70-640, 70-685
  • Options
    Darthn3ssDarthn3ss Member Posts: 1,096
    looks like the flash wasn't seated right. appears to be working now.

    although i do get this:
    00:01:12: %IP_SNMP-3-SOCKET: can't open UDP socket
    00:01:12: Unable to open socket on port 161
    
    Fantastic. The project manager is inspired.

    In Progress: 70-640, 70-685
  • Options
    dtlokeedtlokee Member Posts: 2,378 ■■■■□□□□□□
    Most likely due to no IP address on any of your interfaces.
    The only easy day was yesterday!
  • Options
    Darthn3ssDarthn3ss Member Posts: 1,096
    dtlokee wrote:
    Most likely due to no IP address on any of your interfaces.
    yeah, i took care of that by erasing the config.

    thanks for the help.
    Fantastic. The project manager is inspired.

    In Progress: 70-640, 70-685
Sign In or Register to comment.