E- Studio 2000AC F510 Error

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • copyguy69
    Technician

    50+ Posts
    • Feb 2016
    • 92

    #1

    E- Studio 2000AC F510 Error

    Went on site an the error F510 appears. Tried to reboot the machine and it makes it to 8/9 and reboots itself. Loaded the firmware and same issue. Formatted HDD and loaded firmware and same issue. Machine won't make it to the ready state. I am thinking of changing the HDD. Should I try a ROM recovery update? Any suggestions are welcome. Thanks in advance
    copyguy69
  • blackcat4866
    Master Of The Obvious

    Site Contributor
    10,000+ Posts
    • Jul 2007
    • 22917

    #2
    Usually a brownout, or other power disruption has damaged your HDD. I have had a couple reformat OK, but the majority will require replacing. The ROM recovery won't help.
    If you'd like a serious answer to your request:
    1) demonstrate that you've read the manual
    2) demonstrate that you made some attempt to fix it.
    3) if you're going to ask about jams include the jam code.
    4) if you're going to ask about an error code include the error code.
    5) You are the person onsite. Only you can make observations.

    blackcat: Master Of The Obvious =^..^=

    Comment

    • SalesServiceGuy
      Field Supervisor

      Site Contributor
      5,000+ Posts
      • Dec 2009
      • 8061

      #3
      Only a Toshiba original SED-HDD will work.

      Comment

      • Rusty.Harris
        Senior Tech

        Site Contributor
        500+ Posts
        • Jan 2021
        • 605

        #4
        We had 12 330/400AC's pop 510's last week AFTER being on the 21xx firmware. We downgraded them to 1904, but have since updated them to the 2102, which that issuse
        was suppose to be corrected. Never seen that on the 2000 series. As others have said, probably had a power issue. Might not hurt to put an ESP filter on the line and monitor
        it a while.

        Comment

        • copyguy69
          Technician

          50+ Posts
          • Feb 2016
          • 92

          #5
          Thanks for the replies. Thought it might be a HDD issue. Loaded the firmware for a third time and it seems ok for now.

          Comment

          • jonwill
            Junior Member
            • Jan 2017
            • 9

            #6
            Originally posted by copyguy69
            Thanks for the replies. Thought it might be a HDD issue. Loaded the firmware for a third time and it seems ok for now.
            It'll bounce on you mate if not next week soon after put a new hdd in it.

            Comment

            Working...