Data Recovery Case File · Games & Consoles · The Storage Map
Where the progress actually lives: a PS4 external decoded for a worried household — the saves found safe, the drive recovered, and the crisis honestly downsized
The enquiry was a father doing diligence on a son's distress. The PS4 "will no longer recognise the external hard drive," and the fear had a number on it: "he is worried that he has lost ~1TB of gaming progress." Dad's own troubleshooting had hit a wall that felt like confirmation — "I can't read the drive on my laptop because I only have a Mac that will not recognise it" — and his ask was practical and generous: retrieve the data, and either reinstall it on the reformatted drive or onto a new one he'd supply. Every part of that deserved a straight answer, and the straightest one came first: the thing his son most feared losing was very probably never on that drive at all. The console storage map — which nobody hands parents — is the page; the drive's recovery is the postscript.
| Device | External hard drive in PS4 extended-storage service — ~1TB in use; no longer recognised by the console; unreadable on a Mac (by design, not damage) |
| The fear vs the map | "Gaming progress" = save data — which the PS4 keeps on its internal storage and, where subscribed, in cloud backup; the external holds installed games, which redownload |
| Fault class | Drive/enclosure fault behind the console's rejection — assessed after the stakes were honestly re-sized |
| Equipment used | Console-format-aware assessment · standard recovery of the failed drive · re-preparation for console service on supplied replacement |
The map: what a console keeps where — and why the Mac's blindness was innocent
The Mac first, acquitted in a sentence: a PS4 formats its extended storage in the console's own way, readable by PlayStations and nothing else — a computer meeting that drive sees an alien format and offers nothing, which is the system working, not the drive dying; his laptop's blindness was never evidence. Now the map, because it re-sizes the whole crisis. A console's storage splits into two very different cargoes. Installed games — the terabyte — live on whichever drive they were installed to, his son's external included; they are enormous, and they are also re-downloadable: the licences live with the account, not the drive, and every one of those games can be reinstalled from the console's library onto any storage, tonight, for the cost of bandwidth and patience. Progress — the saves, the actual irreplaceable record of hours played — lives elsewhere: on the console's internal storage, where this PS4 generation keeps save data as a rule, and, for households with the subscription, mirrored to cloud save backup besides. The honest first instruction, given before any quote: check the console's save-data management screens — and the household's check came back exactly as the map predicted: the saves were on the internal drive, intact, every hour of progress present — the terabyte of fear reduced, in one settings screen, to a redownload queue. This archive publishes that deflation proudly, because a lab that lets a family pay for recovering re-downloadable games without first pointing at the saves' real address is monetising a misunderstanding. The external's fault was still real — the console rejecting it meant the drive or its enclosure genuinely failing — but it was now the small problem, priced and decided accordingly.
The recovery — the right-sized remainder
With the stakes honestly shrunk, the drive itself was assessed and treated on its merits: the fault behind the console's rejection addressed, the drive's contents recovered where recovery beat redownloading (a judgement itemised against the family's connection and library — for some households, a recovered install library genuinely saves days of bandwidth; the choice was theirs, made informed), and the storage re-prepared for console service on the replacement drive dad had offered to supply — set up, tested against the console's requirements, and handed back ready for the reinstall session. The delivery note carried the two lines every console household should have on the fridge: saves are the treasure — turn on cloud save backup if the subscription allows, and export/copy saves to a USB stick periodically regardless (the console supports it, and it costs minutes); and externals holding installed games are convenience, not archive — their failure is an errand, never a loss, provided the saves' two homes are tended. His son's progress, it turned out, had never been in danger. The page exists so the next worried household finds that out in one paragraph instead of one bad week.
Outcome
Saves confirmed safe, drive recovered and replaced, crisis correctly sized — and the console doctrine filed for every parent fielding this exact distress. Check the map before fearing the terabyte: installed games redownload from the account's library; progress lives in save data on the console's internal storage and (with the subscription) the cloud — the settings screens answer in minutes what dread guesses at for days. Don't read a computer's blindness as damage: console-formatted drives are alien to Macs and PCs by design. And build the two save habits: cloud backup on, periodic USB export — after which no external drive failure in the household will ever again be more than a queue of downloads. The honest answer here made the recovery smaller and the trust bigger. That's the trade working as it should — and the son's hours, every one of them, were exactly where the map said they'd be.
Console can't see its external drive
Check save-data management on the console first — progress lives internally and in cloud backup, not usually on the external, and the answer takes minutes. Don't reformat the external at the console's suggestion until you've decided whether its installed library is worth recovering versus redownloading (an honest lab will price that choice, not assume it). Never judge a console drive by a computer's inability to read it. And set the two habits now: cloud saves on, periodic USB save export — they make every future drive failure boring.
Check the saves first — then call Belfast Data Recovery on 028 9002 0144; honest map, right-sized fix, progress usually safe.
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.