Data Recovery Case File · Mac & Apple Systems · The Reader, Not the Drive
Third-Party Filesystem Support Is Where Cross-Platform Reading Usually Fails
Her enquiry describes a difficulty created by a change of computer rather than by a fault. A drive formatted for a platform she no longer owns, which she is trying to copy to cloud storage from a machine of the other kind, where "the drive kept disconnecting and I was getting a message saying it malfunctioned, which made me nervous." The nervousness is understandable and the cause may not be the drive at all.
| Media | External hard drive in a platform-specific filesystem format — read from a machine of a different platform through added filesystem support; connection dropping repeatedly during transfer |
| Reported situation | External drive formatted for a platform the owner no longer uses · owner attempting to copy content to cloud storage from a machine of a different platform · connection dropping repeatedly during the attempt · malfunction message reported by the host · owner concerned about the drive's condition |
| Fault class | Cross-platform filesystem handling under sustained transfer — driver instability distinguishable from device failure by independent assessment; drive condition unestablished |
| Equipment used | Filesystem support layer separated from device condition before conclusions were drawn · current draw measured across sustained operation on a controlled bench supply · imaged write-blocked at the block level irrespective of host filesystem support · native filesystem interpreted from the image · content delivered in a form readable on the owner's current platform |
The decode: which layer is dropping out, and how to tell
Why the drive is unreadable natively: each platform uses its own filesystem, and support for another's is partial or added on. A drive formatted for one is read on the other through additional software — either a driver installed for the purpose or limited built-in support.
Why that layer is the likely culprit: added filesystem support varies considerably in quality and stability. Under a sustained transfer of many gigabytes it is being worked far harder than during casual browsing, and instability there presents as the device dropping out.
Why the message she saw does not distinguish them: a malfunction notice is issued when the system loses a device unexpectedly. It reports the disappearance and not its cause — a driver crashing and a drive failing look identical from that message.
Why the distinction matters so much here: one situation is a software inconvenience and the other is a failing drive. Treating a driver problem as a hardware failure wastes money; treating a hardware failure as a driver problem spends the drive.
How it is settled: by assessing the drive independently of any filesystem support. Current draw across sustained operation and the drive's own reporting establish whether it is healthy, and neither depends on any machine being able to interpret its format.
Why imaging bypasses the question entirely: a block-level copy does not interpret the filesystem at all. It reads sectors, so it proceeds regardless of which platform formatted the drive — and the native filesystem is then interpreted from the image with the right tools.
Why that is the right approach even if the drive is healthy: it removes the unstable layer from the transfer. The drive is read once, cleanly, and everything afterwards happens against a copy that no driver can drop out on.
Why her instinct to stop was sound: repeated disconnections under load are not harmless if the drive is the cause. An abrupt disconnection during writing can leave structures inconsistent, and she was not writing — but the repetition was worth stopping.
What she should not do next: accept any offer to repair or check the volume from the machine of the other platform. A system offering to fix a filesystem it only partially understands is the worst combination available.
What is worth planning for afterwards: content delivered in a form her current machine reads natively. The drive's original format is no longer useful to her, and a recovery is the natural moment to leave it behind.
On the bench
The filesystem support layer was separated from device condition before conclusions were drawn — platform-specific formats being read on another platform through added software that varies in stability and is worked far harder by a sustained transfer than by browsing, with instability presenting as the device dropping out, while a malfunction notice reports an unexpected disappearance without indicating its cause. Imaging ran write-blocked at the block level irrespective of host filesystem support, reading sectors without interpreting the format.
The outcome
The support layer separated from device condition, draw measured across sustained operation, and the drive imaged irrespective of host filesystem support. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: the disconnections may not be the drive. Added filesystem support is worked hardest during a large transfer, and a malfunction message reports the disappearance rather than what caused it.
Reading a drive formatted for a platform you no longer have
Refuse any offer to repair or check the volume from the other platform — a system proposing to fix a filesystem it only partially understands is the worst combination available. Before assuming the drive is failing, consider the layer in between: added filesystem support varies in stability and is worked far harder by a sustained transfer than by browsing, and a malfunction message only reports that a device disappeared, not why. Imaging sidesteps the question entirely, since a block-level copy reads sectors without interpreting the format at all.
Don't let it be repaired — call Manchester Data Recovery on 0161 871 0788; support layer separated from device condition, draw measured across sustained operation, imaged irrespective of host filesystem support.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.