Drive clicks or repeatedly recalibrates
Continued power may worsen head or media damage. Record the sound and stop testing the device as soon as physical failure is suspected.
Selective in-lab recovery
Send only the member that cannot be protected safely onsite.
Most RAID recovery work should begin with the array in the client’s hands. When one member cannot be imaged safely because of firmware, electronics, media, or mechanical failure, ADR isolates that device for controlled lab work instead of shipping the complete array.
Keep every bay and member identified. Record the affected drive’s model, serial number, slot, symptoms, power history, and every test or repair already attempted.
Array remains onsiteShip only when a member requires it
Member-specific diagnosisFirmware through mechanical failure
Protected image returnedRejoin recovery without the source drive
Controlled escalationQualified specialists when appropriate
Recognize the failure
One unstable member should not force the entire array into shipment.
ADR separates connection, electronics, firmware, media-read, and internal mechanical symptoms. Stable members remain with the client while only the device requiring physical intervention is escalated.
Drive does not spin or identify
Power, connection, electronics, firmware, motor, or internal mechanical conditions can present the same outward symptom.
Drive identifies but reads slowly
A device may be developing unreadable regions or becoming unstable under sustained access even though it still reports a model and capacity.
Member drops during RAID imaging
The array problem becomes a source-media problem when one member cannot support the reads required for reconstruction.
Multiple-member RAID guidance →Impact, liquid, fire, or contamination
Environmental damage requires case-specific handling before ordinary power, cleaning, or imaging is attempted.
Prior opening or component swap
Record every part, donor, board, ROM, head, platter, and alignment change so the present state can be evaluated honestly.
A controlled recovery path
Repair or stabilize one member, then return its image to the array recovery.
- 1
Identify the affected member
Document its original slot, serial number, symptoms, failure history, and relationship to the array before shipment.
- 2
Choose the least invasive path
Determine whether the member needs firmware, electronics, controlled imaging, cleanroom work, or specialist escalation.
- 3
Create a protected member image
Read the stabilized source strategically to separate media with errors, unread regions, and progress documented.
- 4
Continue reconstruction onsite
Return or transfer the protected image so RAID reconstruction and data verification can proceed while the remaining members stay with the client.
Choose the recovery location and scope
Shipping is an exception for the affected member—not the default recovery environment.
The remaining array stays onsite, labeled, and unchanged. ADR coordinates the affected member’s evaluation and imaging, then uses its protected image with the other members in the controlled recovery process. For unusually difficult physical work, ADR may use a qualified specialist partner while retaining responsibility for the overall recovery path.
Follow the failure to the right service
Choose the path that matches the failed layer.
Storage failures often cross controller, RAID, filesystem, virtualization, and application boundaries. These services connect the next layer without asking the failed system to make another decision.
Primary operating modelRAID recovery without bringing the array onlineBegin with independently connected members while the failed server and controller remain outside the recovery path.Review this recovery path →Customer-retained custodyRemote RAID recoveryKeep stable members onsite while ADR directs protection, reconstruction, and verification.Review this recovery path →Member-set failureMultiple-member RAID recoveryPreserve every original and replacement member when the array has exceeded normal fault tolerance.Review this recovery path →
Before another repair attempt
Describe the array, affected member, physical symptoms, and what happened before it failed.
ADR will determine whether the member can be protected onsite or should be selectively escalated for firmware, electronics, imaging, cleanroom, or specialist work.