Seagate Hard Drive Firmware Failure:

Seagate Barracuda 7200.11 Firmware Failures:

Seagate Firmware.

You may note problems with your Seagate Barracuda  7200.11 hard drive  family model hard drive. The reported problem has shown specific Seagate hard drive  failures reporting a  0 GB size or not show up in BIOS during a post. This means your data stored on your failed Seagate hard drive will not be accessible until the Seagate hard drive failure is “repaired”.

The Seagate Barracuda 7200.11 firmware failure is typically a result of critical firmware modules that have become damaged. The table below shows the affected Seagate Barracuda 7200.11 model that may be affected.

Family + Hard Drive Model Affected Firmware Version Seagate Suggested Firmware Update
Seagate Barracuda 7200.11   ST3500320AS AD14, SD15, SD16, SD17, SD18, SD19, SD81 SD1A
Seagate Barracuda 7200.11   ST3500620AS AD14, SD15, SD16, SD17, SD18, SD19, SD81 SD1A
Seagate Barracuda 7200.11   ST3500820AS AD14, SD15, SD16, SD17, SD18, SD19, SD81 SD1A
Seagate Barracuda 7200.11   ST3640330AS AD14, SD15, SD16, SD17, SD18, SD19, SD81 SD1A
Seagate Barracuda 7200.11   ST3640530AS AD14, SD15, SD16, SD17, SD18, SD19, SD81 SD1A
Seagate Barracuda 7200.11   ST3750330AS AD14, SD15, SD16, SD17, SD18, SD19, SD81 SD1A
Seagate Barracuda 7200.11   ST3750630AS AD14, SD15, SD16, SD17, SD18, SD19, SD81 SD1A
Seagate Barracuda 7200.11   ST31000340AS AD14, SD15, SD16, SD17, SD18, SD19, SD81 SD1A

Table: Seagate Barracuda 7200.11 Firmware Failures.

If your Seagate Barracuda 7200.11 hard drive is physically failing, then the critical firmware region of the hard drive may not be accessible because the sectors where the firmware is stored has developed damaged sectors. When this happens, the hard drive may not be accessed since the firmware zones are corrupted or damaged.

The end result, the Seagate hard drive will not be recognized in BIOS and your computer will not recognize your failed Seagate hard drive in any type of Device Manager or  utility.

There are several references describing how to access a failed Seagate 7200.11 hard drive. One method suggests updating the corrupted Seagate firmware.  Another method suggests manually repairing the corrupted Seagate hard drives via HyperTerminal.

Attempting to repair the corrupted Seagate firmware modules via HyperTerminal when the Seagate hard drives have significant damaged sectors in the firmware zone will NOT work.

The scope of this type of repair is well beyond the ability of most individuals attempting to do their own Seagate data recovery: This is because the complexity of this type of  Seagate Barracuda 7200.11 failure involves a special technique whereby the corrupted firmware must be bypassed.

If your data is critical, then writing to your failed hard drive can be risky and can result in corrupted data and or permanent data loss. So take all necessary precautions before you experiment with your failed Seagate Hard Drive.

In several cases, some suggested repairs do work, and your data is recoverable, but there are always risks to consider before you attempt your own Seagate data recovery.

Before you attempt your own Seagate data recovery:

1 – Find out if your hard drive model and firmware are affected.

2 – Determine if your hard drive has physical damage to the sectors where the firmware is being stored.

3- Determine if your hard drive is clicking.

4- Establish if your hard drive motor is spinning.

5- Determine the value of your data and ascertain if you are willing to Risk your  data by attempting solutions that you are not familiar with if you are not a data recovery expert.

If your hard drive is clicking, or your hard drive motor does not spin up, or you have bad sectors in critical hard drive areas, then you need to consider using a data recovery professional. If you data is critical and you need help, you can always contact us via email or phone.

We welcome your feedback and posts. If you have other interesting topics to discuss, please let us know.

Buffalo NAS Data Recovery.

Buffalo Terastation – NAS & RAID Recovery

Buffalo Technology, a manufacturer of RAID, NAS, and other storage devices, are now available at affordable prices. As a result, you may find a Buffalo RAID or NAS devices in your office or attached to your home computer.

Using a Buffalo Technology RAID or NAS device is putting your data one step closer to having your critical business and or personal information protected.

Don’t get too comfortable just yet, as a hard drive failure, power surge, or a user error can result in you needing to contact a data recovery company and request information on a Buffalo NAS or Buffalo RAID data recovery service.

Depending on the Buffalo RAID or NAS failure, your files and data stored on your NAS or RAID storage device, may become inaccessible. These type of RAID or NAS data recovery’s tend to be quite time intensive, complicated and expensive.

The RAID 0, RAID JBOD or RAID 5 failure is challenging because your failed RAID data is scattered over 2 or more hard drives that were configured with RAID using your Buffalo RAID or Buffalo NAS device. In these cases, your data is stored as 0’s and 1’s on your hard drive, not as files and folders as you may expect. Therefore, for the RAID recovery or NAS recovery to be successful, you must be able to recombine almost all the 0’s and 1’s (bytes) just as they were before your Buffalo RAID or Buffalo NAS device failed.

With a good maintenance and backup plan, most RAID and NAS failures typically only require you to rebuild your failed Buffalo RAID or Buffalo NAS device by installing new hard drives. This is assuming no other electrical components failed and your Buffalo Terastation has not been damaged.

Overview – How to Perform a Buffalo Data Recovery:

How to Perform a Buffalo NAS Data Recovery – Guideline.

1-  Repair any physically damaged Buffalo RAID hard drives. *

2-  Make two sets of forensic images (bit by bit) of all the Buffalo RAID drives onto low level formatted hard drives.

3-  Store one set of imaged hard drives in a secure location.

4- Using the second set of hard drive images, calculate the Strip Size and Parity of the RAID array.

5- Once the strip size is calculated,  “Destrip” the second set of forensic images onto a RAID server or a large

capacity hard drive.

Stay tuned, we will post more details on Parity and Strip size ASAP.

6-  Now you can use your data recovery utilities to recombine the 0’s and 1’s into files and save them on your server.

7- Test the files for functionality to ensure they are working. If they are not working properly, then you will need to manually edit the data files and test them again.

8- When you are done with your Buffalo NAS Recovery, backup your recovered data onto a second hard drive. This will ensure that all your hard work in preparing your own Buffalo NAS data recovery does  not “vaporize” as a result of an accident or unforeseen event.

Special Buffalo Data Recovery Precautions:

Before you start your own Buffalo NAS Data Recovery – Consider this:

Any hard drive images you prepare must use write protection on the source drives. That means if you slave your RAID hard drives to your  computer, without using any hardware write protection hardware, you are destroying your data even before you start. Also know the beginning part of the failed RAID drives has information that is needed to successfully perform your Buffalo RAID or NAS Data Recovery.

* If you are not comfortable with physically repairing failed RAID  hard drives, then you should not attempt your own Buffalo RAID data Recovery.

If you are not able to get all of your RAID hard drives imaged, then your Buffalo RAID data recovery will not be successful and your files will not work or be repairable.

 We welcome your feedback and posts. If you have any interesting data recovery topics to discuss, please let us know.

RAID Hard Drive Failure.

RAID Hard Drive Failure:
understanding hard drives

read / write heads on platter

A RAID server failure or computer failure can occur in many ways.  A server failure or computer failure could be a result of a some type of hard drive failure. The hard drive failure can either be a physical hard drive failure or a logical hard drive failure.

Since this is the most serious type of  RAID server failure or computer failure, we will discuss this first. Understanding your RAID failure or computer failure early on is important because trying to reboot your failed RAID server or failed computer will only make your situation worse. The rebooting can result in permanent data loss if the hard drives get scored or scratched by the read/write heads when you attempt to perform your RAID Server or computer reboot.

Depending on your server configuration, when this type of hard drive failure occurs, you may or may not be able to boot up your failed RAID Server. With regard to most computers, your computer will mostly likely not boot up or POST.

The most serious type of RAID server failure or Computer Failures is a “head crash”. This occurs when the "read/write  heads" inside your hard drive physically touch the hard drive platters. The platters, an internal hard drive storage surface, is where your data is being stored and read from. Depending on the severity of the hard drive failure, you may hear a clicking hard drive sound, or a grinding noise coming from your failed hard drive.

If this occurs, do not reboot your RAID server or computer, or try to access your failed hard drive/s. Doing so will reduce the possibility of recovering data and increase the chances that your data will get permanently destroyed. The following links may also help you better understand about how to handle your computer failure.

Other reasons why your RAID server or computer failed to boot:

  1. Your RAID server when offline.
  2. Your RAID server or hard drive got hit by an electrical surge or sag.
  3. Your computer’s hard drive got hit by an electrical surge or sag.
  4. A virus attacked your operating system.
  5. The power supply to your RAID server or computer is faulty.
  6. Your motherboard and or hard drive controller is malfunctioning.
  7. A critical computer hardware component has failed.
  8. Your memory (RAM) has failed and your computer or server shows a memory dump and blue screens (BSoD).
  9. The Raid server or computer’s power supply is dead or not working properly.
  10. An application loaded is not compatible with your operating system.
  11. A hard drive cable got loose so the hard drive can not being accessed.
  12. A user accidentally or intentionally damaged your operating system.
  13. You rebooted your server or computer and left a non bootable key or media device in your server or computer.
  14. Your computer or server registry has been corrupted.
  15. A buffer overflow resulted because a program bug, using badly written software, overwrote a portion of your program code.

What can you do when your RAID server fails or your computer will not boot?

When your RAID server fails or your computer will not boot, you may follow some of the steps shown below.

But FIRST: Protect your DATA & Don’t PANIC.

Please note, since each RAID server failure or computer failure is unique, your situation may require an alternative strategy.

  1. Turn your RAID server or computer off, if it is safe to do so.
  2. If you do not have a plan of attack, now is the time to make one.
  3. Take a few minutes and figure out how important is your data.
  4. If you have an IT staff or computer consultant, you may consider asking them for help.
  5. If your staff is not experienced in data recovery or hard drive failure, then contact RMD and we can offer you some viable solutions.

On a final note…

Whatever you do, please make sure you do not compromise your data or try solutions that you are not familiar with. Doing so could make the difference between a successful RAID data recovery and a successful computer data recovery.

Often, there are no do overs if things don't work out as you expected them to.

So plan your steps carefully.