Retrodata RAID Recovery
- Home
- About
- Data Recovery Services
- Apple Server Recovery
- Apple Xsan Recovery
- Compaq Server Recovery
- Database and Server recovery
- Dell Server Recovery
- Emergency RAID Recovery
- HP Server Recovery
- IBM Server Recovery
- Intel Matrix RAID recovery
- IRIS and SGI Server recovery
- Linux RAID Recovery
- NAS Data Recovery
- Buffalo LinkStation Recovery
- Buffalo TeraStation Recovery
- Cisco Data Recovery
- D-link Data Recovery
- Data Robotics Drobo Recovery
- Dell NAS data recovery
- Iomega Recovery
- LaCie Data Recovery
- NetApp Data Recovery
- Netgear ReadyNAS Recovery
- QNAP Data Recovery
- Seagate BlackArmor Recovery
- Snap Server recovery
- Synology CubeStation Recovery
- Synology DiskStation Recovery
- Synology RackStation Recovery
- Thecus NAS Recovery
- ZyXel NAS Recovery
- Novell Server recovery
- RAID Data Recovery
- SAN Data Recovery
- UNIX RAID recovery
- Windows Server recovery
- XFS RAID recovery
- FAQs
- Media
- Contact
RAID Controller failure
![]()
Raid controllers come in two basic forms; as a discrete RAID card which can be purchased as a single component, or built into a storage device such as a NAS device, or a storage server such as Infortrend.
In the early 1990s it was common to use more than one RAID controller in a server, such was the high failure rate of these cards. One of the commonest RAID configurations was Disk Duplexing; RAID 1, but with each hard drive running off its own controller.
More currently, RAID controllers do not often suffer from outright hardware failure: but they are known to cause problems following a firmware update.
Additionally, they are prone to firmware corruption, which can damage the file system or the RAID parameters – or both.
We see more RAID controller failures in external network attached storage (NAS) devices such as LaCie than we do in servers.