Data Recovery Case File · Solid State & Flash · What to Ask For
The Folders Most People Forget to Ask For
His enquiry listed priorities with a precision the archive rarely sees. A 500GB Samsung SSD that "failed on cold boot up. Recognised by BIOS but not by the operating system. This is a boot drive with many applications installed and some data files." Then, numbered: his complete email client profile; his complete browser profile and bookmark file; and all his ordinary documents, spreadsheets, PDFs and images. That first pair is the interesting part. Almost every enquiry asks for documents and photographs, and almost nobody asks for the things that actually take longest to rebuild — which is exactly what he has named.
| Media | 500GB Samsung solid-state boot drive — enumerated by system firmware and not by the operating system; application profiles and data files required |
| Reported situation | Drive failing on a cold start · present in system firmware · not available to the operating system · boot drive carrying installed applications and data · specific application profiles named as recovery priorities |
| Fault class | Identification succeeding while media addressing fails — firmware or translation-layer corruption rather than absence of the device |
| Equipment used | Vendor technological and safe-mode access (PC-3000 portfolio, SSD support) · firmware area and translation-layer assessment · imaging sequenced to named application profiles first · profiles verified by loading into fresh installations |
The decode: the technical gap, then the thing worth copying
What "in the firmware, not in the operating system" means: two different handshakes. System firmware performs a shallow enumeration — it powers the drive and asks it to identify itself, and a drive appears there if its controller can answer a few questions. An operating system needs considerably more: a usable reported capacity, and the ability to service real reads through the drive's translation layer, the internal map converting logical addresses into physical flash locations. A drive that identifies itself and cannot service reads has a broken map rather than dead memory — which is the more tractable of the two and is repaired through the manufacturer's own technological modes.
Now the part worth copying. Applications do not keep their settings in the places people think of as "my files". An email client stores everything — messages, folder structure, account settings, address book, signatures, filters — inside a single profile folder. A browser does the same with bookmarks, saved passwords, extensions, history and site preferences. Recovering that folder wholesale and dropping it into a fresh installation restores the application exactly as it was, in minutes. Recovering "my documents" and reinstalling the applications restores nothing of it.
Why this is the commonest silent loss in the trade: people commission a recovery, receive their documents and photographs, declare it a success — and then discover over the following weeks that fifteen years of email is gone, that they have none of their saved logins, and that their bookmark collection has vanished. By then the drive has often been disposed of. The material was recoverable throughout; nobody asked for it, because it did not feel like a file.
The list worth naming, whatever the fault: the email client's profile folder if mail is stored locally rather than on a server; the browser profile; any accounting or design application with a local database; saved game data; and the desktop, which is where a surprising amount of unfiled work lives. Those are ordinary folders in ordinary locations — they simply are not where people look.
Why naming them changes the work: more than politeness. On a drive whose access may not be indefinite, imaging is sequenced to capture named material first, while the drive is at its most cooperative. A specific list is therefore worth considerably more than "everything important".
One note on his stated preference: he would prefer the drive repaired if possible. On a drive whose contents matter, that order is worth reversing — get the data off first, and decide about the drive afterwards.
On the bench
Access was attempted through the PC-3000 portfolio's SSD support in the drive's vendor technological modes, with the firmware area and translation layer assessed — because a drive that identifies consistently and cannot service reads is describing a broken map rather than absent memory. Imaging was then sequenced to the named application profiles first rather than run in drive order, since those were the items he could least easily rebuild. The profiles were verified by loading them into fresh installations rather than by confirming the folders existed, which is the only test that establishes they actually work.
The outcome
The controller addressed in vendor modes, the named profiles imaged first and verified by loading them into fresh installations. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode, and the thing worth copying from this enquiry: ask for your application profiles, not just your documents — an email client keeps every message, account setting, address book entry and filter inside one profile folder, and a browser keeps bookmarks, saved logins and extensions in another, and recovering those folders restores the applications exactly as they were; people who ask only for documents discover weeks later that fifteen years of mail is gone, usually after the drive has been disposed of.
Writing your list of what to recover
Don't stop at documents and photographs — name your application profiles too, because they're what takes longest to rebuild and almost nobody asks for them. Your email client keeps every message, folder, account setting, address book entry, signature and filter inside a single profile folder, and your browser keeps bookmarks, saved logins, extensions and preferences in another. Recover those folders and drop them into a fresh installation and everything comes back exactly as it was; recover "my documents" and reinstall the applications and none of it does. The same goes for accounting or design software with a local database, saved game data, and your desktop, where a surprising amount of unfiled work lives. Being specific also changes the work itself: a named list lets imaging capture those items first, while the drive is at its most cooperative.
Include your mail and browser profiles — call Newcastle Data Recovery on 0191 406 1051; controller addressed in vendor modes, imaging sequenced to your named items, profiles verified by loading them.
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.