Drobo Not Mounting and Drobo Inc. Are Gone? We Still Recover Your Data.
UK Drobo data recovery specialists since 2002. Drobo 5N, 5D, 5C, B810n, B810i, Mini, FS. BeyondRAID reassembly without needing a working Drobo unit. Free collection. No-fix-no-fee.
What this means and what to do next
Drobo Inc. ceased trading in 2023, leaving thousands of Drobo NAS owners worldwide with units that have no support, no replacement parts, and no path to firmware updates. When a Drobo fails — most commonly the 5N, 5D, B810n, or Mini — the natural first step (buy a replacement Drobo, swap the disks in) is no longer viable because new Drobos cannot be bought. The only paths forward are to source a used identical unit and hope it works, or to recover the data outside the Drobo ecosystem entirely. Data Clinic does the second.
Drobo's BeyondRAID format is proprietary but well-understood. The disks store data in a striped, mirrored, or single-parity layout depending on capacity and disk count, with thin provisioning at the volume layer. Each disk carries metadata identifying its position in the array, the layout of stripes, and the version of the BeyondRAID format in use. Given the physical disks and the original bay order, the array can be reassembled on PC equipment without any Drobo hardware being present.
The most common Drobo failure scenarios we recover from are: capacitor failure on the controller board (the unit simply stops powering up), accumulated disk failures that exceed the redundancy level after a long-running unnoticed degradation, and disks ejected from the array after a power event because the BeyondRAID metadata went out of sync. All three are recoverable provided the disks themselves are not all physically failed and have not been wiped by an attempted re-initialisation.
The common Drobo failure scenarios — and what they mean for recovery
1. Drobo unit dead but disks are intact. Symptom: unit will not power on, no lights, no fan. Disks are physically fine — the failure is in the Drobo controller, typically capacitor failure on the main board. Recovery: remove the disks with bay positions documented, image each disk, reassemble the BeyondRAID array on our equipment, extract the data. This is the most common Drobo recovery and one of the most successful — provided the disks are not moved out of bay order before removal.
2. Drobo flashing amber/red after a power event. Symptom: unit powers on but indicators show one or more disks have been ejected from the array. Drobo Dashboard either won't connect or shows the array as in critical or rebuild state. Recovery: stop the unit immediately — letting it attempt a rebuild against potentially out-of-sync disks will destroy data. Image the disks externally, reassemble the array using the BeyondRAID metadata from each disk, identify which disks were the last consistent set, extract the data.
3. Disks have failed beyond the array's redundancy level. Symptom: Drobo reports the array is unrecoverable, or you have replaced one failed disk and during the long Drobo rebuild a second disk failed. The Drobo unit is correct that the array as a single-redundancy or dual-redundancy set cannot be reassembled, but partial recovery is usually still possible from the surviving disks plus images of the failed ones. Cleanroom imaging of the failed disks is often the critical step.
4. Filesystem corruption above the BeyondRAID layer. Symptom: Drobo says the array is healthy, the disk lights are green, but the volume mounts empty or with corrupt directory structures. The BeyondRAID layer is fine; the HFS+, ext3, ext4 or NTFS filesystem on top of it has corrupted. Recovery: image the array via the Drobo if it is still working, or via direct disk imaging if not, then perform standard filesystem recovery on the extracted volume image.
How Data Clinic recovers data from a failed Drobo NAS
Call before doing anything to the Drobo. Many failed Drobos arrive at our lab with their data already destroyed by attempted recovery — disks reseated in wrong bays, factory-reset attempted, disks moved into a different Drobo unit. The first job on any Drobo call is to talk you through preserving the current state so the recovery has the best possible starting point.
Disks are then collected by secure courier with bay positions documented and shipped to our Bury lab. We image each disk on PC-3000, applying cleanroom or PCB-swap techniques to any disk that is itself failing. The BeyondRAID array is reassembled on our equipment using the disk-position metadata. We mount the resulting filesystem read-only, walk the directory tree, and report the recoverable contents within 48 hours of receipt.
Recovered data is returned on a new external drive or NAS of the customer's choice. We provide a written report detailing the recovery and any limitations — useful for owners who are using the recovery as the trigger to migrate off the Drobo platform entirely (which we recommend, given Drobo's closure). More about our NAS data recovery service →.
Get a free initial diagnosis in 60 seconds
Use the diagnostic tool below to record the model (Drobo 5N, 5D, 5C, B810n, etc.), the disk count and capacities, and the lights you are seeing. BeyondRAID recovery depends on knowing the exact disk lineup, so capture this before powering the unit off.
What our customers say
"Three years of family photos on a drive that suddenly failed. Data Clinic collected next day, kept me updated through the cleanroom work, and got everything back. Worth every penny."
"Honest, fixed-price, no-fix-no-fee. Quoted by another lab at three times the price. Recovered 100% of my files."
"Reasonable cost, clear communication, and they were straight with me about what was recoverable and what wasn't. Recommended."
Frequently asked questions
Drobo is out of business — can anyone still recover my data?
Yes. Drobo recovery does not depend on Drobo the company. The BeyondRAID format is well-understood and the data lives on the disks — we image the disks and reassemble the array on PC equipment. The disappearance of Drobo means you cannot buy a replacement unit, but it does not affect data recovery.
Should I just buy a used Drobo on eBay and put my disks in it?
Strongly recommend against this until we have imaged the disks. A used Drobo with different firmware, or any tendency to re-initialise an unrecognised array, can destroy the data on disks that were otherwise fully recoverable. If you want to keep using Drobo (which we would not recommend long-term), the safe sequence is: image the disks for safety, then try the used unit. Not the other way round.
How do I know which Drobo model I have, and does it matter?
It matters because BeyondRAID has evolved across models. Drobo 5N, 5D, 5C, 5N2, B810n, B810i, Mini, FS each have slightly different layouts. The model is printed on the back of the unit. Photograph the back panel — including model number and serial — before shipping us anything.
How long does Drobo recovery take?
Typical case: 5–7 working days from receipt of the disks to delivery of recovered data. Drobo recoveries tend to be slightly longer than other NAS recoveries because BeyondRAID reassembly requires more permutation testing than standard md-RAID. Add 1–2 days per failed disk that requires cleanroom imaging.
What if some of my disks have died completely?
Provided enough disks survive to reach the array's redundancy threshold, recovery is still possible. For single-disk-redundancy arrays, we need all-but-one disk readable. For dual-disk-redundancy arrays, we need all-but-two. Failed disks can usually be imaged via cleanroom or PCB swap — we count a disk as 'lost' only if it has total platter destruction, which is rare.
After recovery, what should I migrate to instead of Drobo?
Synology and QNAP are the dominant supported NAS platforms in 2026 and both have mature data recovery pathways if they ever fail. We commonly migrate recovered Drobo data straight onto a new Synology or QNAP unit and ship it ready for the customer to plug in. We can quote that as part of the recovery if you want a single supplier for the whole transition.