FAQ

A failed RAID controller is a hardware failure that prevents the operating system from detecting and accessing the entire RAID volume, making all data inaccessible until the failed component is replaced or bypassed by a specialist. According to Ontrack's data recovery statistics (2024), controller failures account for approximately 20% of cases of loss of access to RAID systems.

RAID degraded mode is a critical state in which a RAID controller reports that one or more disks in the group are no longer functioning correctly, reducing data redundancy without necessarily interrupting service. According to Backblaze statistics (2024), 5.1% of hard drives fail each year, making degraded mode one of the most frequent RAID alerts in a server environment.

The system generally remains operational in degraded mode, but any additional disk failure can lead to total data loss. Rapid intervention is imperative.

A RAID not detected by the computer is a critical situation that occurs when the RAID controller is defective or its configuration has been lost, making the entire RAID volume inaccessible to the operating system.

The main causes of an undetected RAID include:

• Defective RAID controller: The card or chip managing the RAID no longer responds, preventing any communication with the disks
• RAID configuration loss: The metadata describing the RAID structure (type, disk order, block size) has been erased or corrupted
• Power or connection problem: A faulty cable or unstable power supply can make the RAID invisible at startup

A solid-state drive (SSD) with a LED that is off or blinking indicates a hardware failure affecting the power supply or a critical internal component. The most frequent causes are: a power failure (defective cable, out-of-service SATA port), a damaged SSD controller, or a faulty NAND memory chip. According to industry data, approximately 60% of LED failures on SSDs are related to an internal component rather than the power supply.

An inactive LED indicates that the SSD is not receiving enough power or that its internal controller is no longer responding. Abnormal blinking may indicate firmware corruption or a defective memory chip.

An SSD not recognized by the BIOS is a hardware or software problem preventing the boot system from detecting the SSD drive, usually caused by a failure of the connectors, firmware, controller, or memory chips.

To diagnose the problem, access your computer's BIOS by pressing F2, F9, F12, or DEL at startup (the key varies depending on the manufacturer: Dell uses F2, HP uses F9, ASUS uses DEL). The BIOS will immediately indicate whether the SSD is detected or not.

Symptoms

A scratched CD/DVD is an optical disc whose reading surface is damaged by scratches, compromising the drive's ability to read the data correctly. It is essential not to cause further scratches: stop using your CD/DVD immediately and gently remove it from the drive.

A broken SATA connector on an SSD is a physical failure that prevents power and data transfer between the drive and the motherboard. Do not attempt to force the damaged connector and never open your SSD to attempt a DIY repair: the internal components of an SSD (controller, NAND chips, capacitors) are extremely sensitive to uncontrolled handling and static electricity. An unprofessional intervention can make data recovery definitively impossible.

The LED on a USB drive is a built-in indicator light that signals the activity and power of the storage device. When the LED on your USB drive no longer lights up or flashes abnormally, this indicates an internal malfunction. This problem usually stems from an internal power failure or, in most cases, a damaged internal electronic component (controller, flash memory, or circuit board).

A broken USB connector is a physical failure that prevents the USB drive from establishing a stable connection with a computer, exposing the stored data to the risk of permanent inaccessibility if inappropriate intervention damages the internal memory chips.

Do not attempt to force the damaged connector or open your USB drive to resolder the connector yourself: according to data recovery specialists, more than 60% of DIY repair attempts on USB connectors worsen the damage to internal components, making data recovery more complex and costly.

A USB drive damaged by fire or flood is a storage device that has suffered physical or electronic damage caused by heat, flames, or moisture. These disasters can cause three types of critical failures: melting of internal components (connector, circuit board), the presence of residual moisture inside the case, and failure of the control electronics, making the data inaccessible without specialized intervention.

A USB drive broken into pieces is a physically fragmented storage device whose internal components, including the NAND flash memory chip, may remain functional despite the external damage. If your USB drive is broken, handle the pieces as little as possible: any attempt to glue or solder the fragments, or to extract the internal components yourself, risks permanently damaging the memory chip and making data recovery impossible.

A USB drive not recognized by Windows or Mac OS is a hardware or software problem that prevents the operating system from detecting and mounting the storage device. According to Ontrack data recovery data (2024), approximately 35% of USB drive failures are software-related (file system corruption, partitioning error), while 65% are related to physical failure of the internal controller or NAND components.

The most frequent causes are:

1. Partitioning problem – The partition table is corrupted or missing, making the drive unreadable without damaging the data.
2. Incompatible or corrupted file system – An interrupted format or incorrect ejection can corrupt the file system (FAT32, exFAT, NTFS).
3. Internal controller failure – The USB drive's controller chip is damaged, preventing any communication with the USB port.
4. Obsolete or faulty USB driver – Under Windows, a corrupted USB driver can block device detection.

A USB drive that is recognized but inaccessible is a storage device detected by the operating system, visible in the Device Manager or File Explorer, but whose contents remain unreadable or inaccessible.

Two main causes explain this problem:

1. Software partitioning issue — The partition table or file system (FAT32, exFAT, NTFS) is corrupted, making the data unreadable without physically damaging the media.
2. Physical failure — The NAND memory chips or the USB controller are damaged, preventing any reliable communication between the drive and the operating system.

An unusual noise from a hard drive — repetitive clicking (« click-click-click »), screeching, or dull thumping — indicates an internal physical failure, most often involving the read/write heads.

Two main causes are identified:

• Defective read/write heads: they can no longer read the magnetic platters, producing a characteristic clicking sound and preventing the drive from initializing.
• Damaged platter surface: scratches or defective areas generate a screeching noise and make data reading impossible.

Key point: Any abnormal mechanical noise from a hard drive indicates a hardware emergency. Each additional startup cycle worsens the damage and reduces the chances of data recovery.

Data privacy refers to all the technical and contractual measures ensuring that the information collected is only accessible to authorized individuals and used solely for its intended purposes.

All recovered data is treated with strict confidentiality, in accordance with the requirements of the General Data Protection Regulation (GDPR), in effect since May 2018 in the European Union. Our concrete commitments include:

Key commitment: The protection of your data is not an option — it is a contractual and ethical obligation integrated into each of our interventions.

#Information