Computer Repair · October 29, 2026 · ComputerKing Team
When a Clicking Hard Drive Cannot Be Recovered Yet: Rebuilding Your Files from Other Copies — Five Secondary Sources and a Reconciliation Checklist
While a clicking drive is still being diagnosed, work need not stop completely: rebuild files from five secondary sources — cloud, email, another device, older backups, and applications themselves — in three priority tiers, store conflicting versions separately for comparison, and immediately move rebuilt files to a new location, back them up independently, and keep the list.
Key Points
- Stop using a clicking drive at once; that rule does not change. This article covers a second, parallel track: while the original drive is being diagnosed, or its result is still unknown, how to rebuild the files you need most from other copies, without letting the two tracks undermine each other.
- Before searching anywhere, write down a most-important-files list. Do not rely on memory alone: use sent-mail records, download records, and each application's recent-files list to remind yourself, and write each item down as you think of it.
- Five secondary sources: cloud sync and version history, email attachments and copies held by the other party, another device, older backups and external drives, and the cloud content held inside applications themselves.
- Rebuild in three priority tiers: deadline and work-critical files first, everyday files second, and content that can be recreated last. Where one file exists in several versions, never overwrite directly; store each version in its own folder and compare them.
- Rebuilding part of your files does not mean the original drive no longer needs follow-up. While it is still being diagnosed, do not cancel the diagnosis because a few files turned up, and do not format or dispose of the original drive before its result has been checked.
Introduction
If you have read our clicking-drive series, you have already taken the most important step: on hearing clicking, power off at once, do not run repair software, and do not open the drive yourself. Emergency handling, the decision after stopping, and what to prepare before asking for a quote have all been covered before, and this article does not repeat them:
- "Clicking Hard Drive? Power Off Now: 2026 Recovery & Myth Guide (HK)" covers sound classification and six common myths;
- "Clicking Hard Drive? DIY vs Pro Recovery: Vetting, Verifying" covers the decision after stopping, choosing a service provider, the pre-repair checklist, and acceptance;
- "After Your Hard Drive Starts Clicking: What to Do After Powering Off — Judge Urgency, Prepare a Quote, and Avoid Making It Worse" covers the seven questions to ask about a quote and the idea of diagnosis grading.
This article covers one question the three earlier articles did not treat as a dedicated topic: the original drive is already stopped and sent for diagnosis, or its result is that some files cannot be recovered, yet work cannot stop indefinitely — what happens in between? The answer is not to power the original drive up and try again. It is to change direction: rebuild from other copies. Many files do not exist only on the original drive. They were sent to someone, synced to the cloud, opened on another device, or left inside an application. Rebuilding is the systematic job of finding those scattered copies, checking them against each other, and putting them in order.
Three boundaries apply throughout. First, rebuilding is not original-drive recovery. How much you can rebuild depends entirely on whether you previously placed files anywhere else; files that exist nowhere else cannot be rebuilt this way, and still depend on the original drive's diagnosis result. Second, a rebuilt file may be an older version, not the latest version that was on the original drive, and that gap must be written down rather than treated as a full restoration. Third, rebuilding must not create new risk: do not power the original drive up again in order to rebuild, do not download so-called recovery tools from unverified sites, and do not overwrite your only older backup with rebuilt files.
Two Parallel Tracks: Original-Drive Follow-Up and Rebuilding Must Not Undermine Each Other
After a drive starts clicking, two extremes are common. The first is to do nothing and simply wait for the result, so work stops completely, and only days later do you discover that many files could have been found elsewhere. The second is impatience: powering the original drive up repeatedly, or overwriting files carelessly while rebuilding, so the original drive gets worse or an older backup gets covered over.
The correct approach is to keep the two tracks separate. The original-drive track stays stopped and follows the diagnosis and quoting process until its result arrives. The rebuilding track runs on another device, aims only at the files work needs most, and does not attempt to restore the whole drive file by file. Keep separate records for each track: the original-drive side records diagnosis progress and quotes, while the rebuilding side records where each file was found, which version it is, and when that version dates from. With two separate records, the later reconciliation does not get confused.
One more point: rebuilding should be done on another device, not on the machine that failed. If the failed drive is an internal drive, that machine is already stopped, and it must not be powered up again for rebuilding. Another computer at home, another machine at the office, or a phone plus the web version of a cloud service is enough for every step below.
Step One: Write the Most-Important-Files List First, Not from Memory Alone
The most common mistake before rebuilding is to start searching everywhere at once, grabbing whatever turns up, and ending up with a pile of files you do not urgently need, while the file due tomorrow is missed. So the first step is not searching. It is writing a list.
How do you write a complete list? Do not rely only on thinking "what was on the drive". Use four kinds of record to remind yourself:
- Files recently sent out: open your sent-mail folder and look at attachments sent in the past month or two. Each attachment is itself a copy, and the recipient may still hold one too.
- Files recently changed: think about which projects you worked on in the past week, which documents you changed or opened most recently. Each application's recent-files list can help you recall.
- Files with a deadline: quotations, reports, homework, or application forms that must be submitted by a date. These go first.
- Files that cannot be recreated: photos, recordings, scanned handwritten notes, and manuscripts. Even if they are not urgent, they rank higher, because they cannot be redone.
For each item on the list, three columns are enough: roughly what the file is called, which project it belongs to, and roughly when it was last changed (an approximate date will do). Precision is not the point; the point is having something to check against later. Writing one item as you think of it, and only starting to search once the list is written, already beats searching at random.
Five Secondary Sources: How to Search Each One, and How to Verify What You Find
The five sources below are ordered not by importance, but by a suggested order starting with the source where a version date is easiest to verify. When you find a file in one source, record it, and do not stop there, because different sources may hold different versions.
| Secondary source | How to search it | How to verify what you find |
|---|---|---|
| Cloud sync and version history | Sign in to the cloud account you normally use and check whether the file was synced; where version history exists, open the version list and look for newer or older versions | Check the file name, modification date, and the first few paragraphs of content; do not treat a matching name as the same file. A version from the history can be downloaded first for comparison, rather than restored directly over the cloud copy |
| Email attachments and copies held by the other party | Search your sent and received mail by file name or project name for attachments you sent or that others sent you; where needed, ask the other party whether the copy they hold is the version you last sent | Check the sent date and the attachment content; if the other party's copy is older than the one you hold, record that gap rather than treating it as the latest version |
| Another device | Check a phone, tablet, older computer, or another office machine for files that were synced, copied, or downloaded there; photos and documents very often exist in another form on a phone | Check whether the file date on the device is close to the original drive's last modification date; treat a device copy as a copy for use, and copy it to the rebuild folder before editing, rather than editing it in place |
| Older backups and external drives | Go through each external drive, older backup drive, and USB stick you have used, looking for the relevant folders; the date of a folder on a backup drive is itself a version clue | Copy files from the backup drive into the rebuild folder first, and do not edit directly on the backup drive; backup files may be months old, so compare them against the last modification date on your list |
| Cloud content inside applications themselves | Photo, note, chat, document, design, and music applications often sync their content to the cloud on their own, so even if the original drive file is gone, the application may still show the content | Go through each application item by item, and use the application's own export function to take the file out; do not use a screenshot as a substitute for the original file. After export, check the file name and date |
Cloud version history deserves a little more detail, because it is the source most often overlooked. Many people assume the cloud holds only one latest file, when in fact some cloud services keep older versions. For OneDrive, the official support page explains that version history lets you view and restore older versions, and notes that version history for a personal account is generally retained for 30 days, while a work or school account may be set by an administrator. Google Drive also has version management and a bulk tool for restoring older file versions, and its official help page notes that it keeps revisions from a recent period. The point is not to memorise a retention period, but to remember to open the version list during rebuilding, rather than looking only at the file in front of you. Retention periods differ by account and setting, and an older version past its retention window may already be gone, so rebuilding should not be left too long.
The email-attachment source needs one specific warning: an attachment is the version as it was when sent. Anything changed on the original drive afterwards is not in the attachment. Finding an attachment does not mean finding the latest version, and that gap must be written down so the later reconciliation is not misled.
Rebuilding Order: Three Priority Tiers, Easiest-to-Verify Files First
Once the list is written and the sources are searched, do not rebuild everything at once. Work in three tiers:
Tier one: files with a deadline or files critical to work. For example, a report due tomorrow, a quotation awaiting a client's reply, or a contract draft being followed up. Rebuilt files in this tier must be checked against their content at once, to confirm whether the version is submittable, and not left unchecked.
Tier two: everyday work files. For example, project folders, commonly used forms, and reference documents. These can be rebuilt gradually, placed in a new folder, and checked later when needed.
Tier three: content that can be recreated, or entertainment content. For example, installer files that can be downloaded again, media that can be re-downloaded, and drafts you can write again. There is no rush here, and failing to rebuild them does not affect work.
Why split into tiers? Because rebuilding easily grows out of control, until you no longer remember which files were rebuilt and which were not. Once tier one is done, work can continue, and the other two tiers can proceed slowly, with far less pressure.
There is also a second ordering rule: do the easiest-to-verify files first. An easy-to-verify file is one with a sent record, a confirmation from the other party, or a clear cloud version date. Such files can be reconciled quickly after rebuilding. A file with only one source and no date clue takes longer to reconcile, and should come later.
Version Conflicts: Do Not Overwrite, Store Separately, Compare Three Things
One file found in different sources in different versions is the most common situation in rebuilding. The handling rule is a single sentence: never overwrite directly; store every version separately, and only then compare them.
In practice: create a new rebuild folder, with subfolders by source, for example "Cloud version", "Email attachment", "Phone copy", and "Older backup". Add the source and date to each version's file name, for example "Quotation — cloud — 20 October 2026 version" and "Quotation — email attachment — 15 October 2026 version". That way, where each version came from is visible at a glance, and nothing gets mixed up.
When comparing, three things are enough:
- Date: whichever version's modification date is closest to the original drive's last modification date is usually newer, but not certainly so, and content must still be checked afterwards.
- Key content: open the file and look at key paragraphs, figures, and the ending. For a report, look at the conclusion; for a quotation, look at the amounts and the line items; for a table, look at whether the last few rows contain newly added items.
- Sent or confirmed records: if a version was once sent to someone, the recipient's receipt of that version is external evidence that the version existed, and it deserves higher credibility.
After comparing, pick one version as the "provisional working version", and keep all other versions; do not delete them. The provisional working version's file name should say so, for example "Quotation — provisional working version", so that when the original drive's result arrives, it can be compared again. If the original drive later yields a newer version, the provisional version must give way, rather than being kept because it has become familiar.
Three Things to Do Immediately After Rebuilding
Once tier one is rebuilt, do three things at once, rather than waiting until the whole rebuilding job is finished:
First, move the rebuilt files to their new working location. That location can be a new drive, a new computer, or a new folder in the cloud — anywhere except the failed drive, and not only on the temporary device used for rebuilding. Once the working location is set, all later edits happen there, and no longer in several separate places.
Second, make an independent backup at once. Rebuilt files, assembled from several sources, exist in only one place if you stop here, and a further failure would leave nothing to rebuild from. The backup approach can follow the 3-2-1 rule described in this site's "Hong Kong User Backup Strategy Complete Guide": at least three copies of a file, on two different kinds of media, with one copy in another location. This article does not expand on backup detail; the point is that backup must happen at once after rebuilding, not later.
Third, keep the rebuild list and source record. The list should state: which files were rebuilt, which version, from which source, which files were not rebuilt, and which files exist only as older versions. The list serves two purposes: when the original drive's result arrives, each item can be reconciled one by one; and if anyone later asks why several versions of one file exist, the list is the explanation.
When to Stop and Wait for the Original Drive's Result
Rebuilding does not go on without limit. In three situations, stop and wait for the original drive's diagnosis result before deciding further:
First, the original drive is still being diagnosed, and its result may change the rebuilding choices. For example, a rebuilt file may be only a draft, while the original drive may hold a newer version. In that case, rebuilding tier one enough for work is sufficient; rebuilding a whole folder only makes the later reconciliation messier.
Second, a rebuilt file involves other people's data or needs the other party's confirmation. For example, a contract, client data, or a company shared document, where the rebuilt version differs from the version the other party holds. Confirm with the other party first, rather than choosing a version yourself and treating it as final.
Third, rebuilding starts to involve the original drive itself. For example, a suggestion to "power the original drive up once more, to see whether a few more files can be copied". That suggestion should be refused. The original drive is already stopped, and rebuilding is not a reason to power it up again. Rebuilding uses secondary sources only, and does not touch the original drive.
Common Mistakes
| Common assumption | Where the problem lies | What to do instead |
|---|---|---|
| A file found is the latest version | Cloud copies, email attachments, and older backups are very often older versions; a matching name does not mean matching content | Compare the date and key content, record the version source, and compare before choosing a provisional working version |
| Rebuilt files can overwrite an older backup directly | The older backup is the only older but complete copy; once overwritten, there is no way back | Put rebuilt files in a new folder, and leave the older backup untouched, with the two stored separately |
| Rebuilding justifies powering the original drive up again | Powering up itself may worsen the original drive, and the rebuilding benefit is not worth trading the original drive for | Rebuild from secondary sources only, keep the original drive stopped, and follow the diagnosis process |
| Stopping halfway through rebuilding without leaving a list | Days later, you no longer remember which files were rebuilt and which were not, and reconciliation cannot be done | As soon as each file is rebuilt, record its source and version date on the list at once |
| Using a screenshot instead of the original file | A screenshot shows the content, but it is not the original file, and cannot later be edited or checked for formatting | Use the application's own export function to take the original file out; a screenshot can only be a temporary reference |
| Treating rebuilding as the end of the matter | The original drive's result is still outstanding, and a rebuilt version may be only an older version, so reconciliation is still needed | Keep the rebuild list, and when the original drive's result arrives, go through it item by item before treating the matter as closed |
Summary
After a clicking hard drive, work does not have to stop completely, but it must not be rushed into carelessness either. Remember this article's order: write the most-important-files list first, search each secondary source in turn, rebuild in three tiers, store conflicting versions separately and compare their dates and content, then move rebuilt files to a new working location at once, make an independent backup, and keep the list. How much can be rebuilt depends on whether files were previously placed anywhere else; parts that cannot be rebuilt still depend on the original drive's diagnosis result, and must not be abandoned just because a few files turned up.
One safety line, once more: throughout rebuilding, do not touch the original drive — do not power it up again, do not run repair software on it, and do not open its cover yourself. The original-drive track and the rebuilding track run separately, with separate records, so that the later reconciliation can be done clearly. On charges, diagnosis and recovery are always quoted individually; do not trust a fixed price offered before the drive has been seen.
Frequently Asked Questions
Q: The original drive is still being diagnosed. Will rebuilding files now affect the diagnosis result?
A: No, as long as rebuilding never touches the original drive. Rebuilding uses cloud copies, email, another device, older backups, and content inside applications — all on another device — while the original drive stays stopped, so the diagnosis side does not change because you rebuilt. The key rule is never to power the original drive up again in order to rebuild.
Q: Is the file on the cloud necessarily the latest version that was on the original drive?
A: No. Cloud sync has a time lag, and changes made after the last sync may not be in the cloud copy. So after finding a cloud file, open its version history as well, and compare its modification date and key content. Do not treat a matching file name as the latest version.
Q: One file turns up in three sources in three different versions. How do I choose?
A: Keep all three versions, stored separately, with file names stating the source and date. Compare the date, key content, and sent records, choose one as the provisional working version, and keep the other versions without deleting them. When the original drive's result arrives, compare again; the provisional version is not the final version.
Q: How does an email attachment differ from the file that was on the original drive?
A: An email attachment is the version as it was when sent. Anything changed on the original drive afterwards is not in the attachment. So finding an attachment only proves that version once existed; it does not mean it is the latest version. Record that gap during reconciliation, and do not mistake it for the latest version.
Q: Files on an older backup drive are very old. Are they still useful?
A: Yes. Even a version from months ago is a version clue. It can confirm the file's structure, project names, and approximate content, and a newer source can then fill in the changes made in between. Never overwrite an older backup directly; copy its files into the rebuild folder first, and leave the backup itself untouched.
Q: How should rebuilt files be backed up to stay safe?
A: As soon as rebuilding is done, move the files to their new working location, and make an independent backup at once. The approach can follow the 3-2-1 rule described in this site's "Hong Kong User Backup Strategy Complete Guide": at least three copies of a file, on two different kinds of media, with one copy in another location. While rebuilt files exist in only one place, the risk is as high as before.
Q: Halfway through rebuilding, some files cannot be found anywhere. What should I do?
A: First, record those files in the "not yet rebuilt" column of the list, and do not abandon the original-drive follow-up at once. Files not yet rebuilt may depend on the original drive's diagnosis result, or may turn up later from another source, such as a copy held by the other party, a company shared folder, or an application export. Keep the list, so the later reconciliation shows what is still outstanding.
Q: How does this article differ from the three earlier clicking-drive articles?
A: The three earlier articles cover emergency handling, the decision after stopping and asking for a quote, and judging urgency after powering off — all centred on the original drive itself. This article covers only the other track: while the original drive's result is still unknown, or some files cannot be recovered, how to rebuild data from other copies, compare versions, and keep a list. Original-drive handling is only cross-referenced here, not repeated.
Sources
- Microsoft Support: Restore a previous version of a file stored in OneDrive — https://support.microsoft.com/en-us/office/restore-a-previous-version-of-a-file-stored-in-onedrive-159cad6d-d76e-4981-88ef-de6e96c93893?WT.mc_id=M365-MVP-5003350
- Google Drive Help: Restore files in bulk with Google Drive — http://support.google.com/drive?p=drive_rewind_rollback
- This site: "Clicking Hard Drive? Power Off Now: 2026 Recovery & Myth Guide (HK)" — hdd-clicking-sounds
- This site: "Clicking Hard Drive? DIY vs Pro Recovery: Vetting, Verifying" — hdd-clicking-recovery-decision-guide
- This site: "After Your Hard Drive Starts Clicking: What to Do After Powering Off — Judge Urgency, Prepare a Quote, and Avoid Making It Worse" — hdd-clicking-sounds-next-steps
- This site: "Hong Kong User Backup Strategy Complete Guide" — backup-strategy-hk
Related Articles
- hdd-clicking-sounds
- hdd-clicking-recovery-decision-guide
- hdd-clicking-sounds-next-steps
- backup-strategy-hk
Frequently Asked Questions
The original drive is still being diagnosed. Will rebuilding files now affect the diagnosis result?
No, as long as rebuilding never touches the original drive. Rebuilding uses cloud copies, email, another device, older backups, and content inside applications — all on another device — while the original drive stays stopped, so the diagnosis side does not change because you rebuilt. The key rule is never to power the original drive up again in order to rebuild.
Is the file on the cloud necessarily the latest version that was on the original drive?
No. Cloud sync has a time lag, and changes made after the last sync may not be in the cloud copy. So after finding a cloud file, open its version history as well, and compare its modification date and key content. Do not treat a matching file name as the latest version.
One file turns up in three sources in three different versions. How do I choose?
Keep all three versions, stored separately, with file names stating the source and date. Compare the date, key content, and sent records, choose one as the provisional working version, and keep the other versions without deleting them. When the original drive's result arrives, compare again; the provisional version is not the final version.
How does an email attachment differ from the file that was on the original drive?
An email attachment is the version as it was when sent. Anything changed on the original drive afterwards is not in the attachment. So finding an attachment only proves that version once existed; it does not mean it is the latest version. Record that gap during reconciliation, and do not mistake it for the latest version.
Files on an older backup drive are very old. Are they still useful?
Yes. Even a version from months ago is a version clue. It can confirm the file's structure, project names, and approximate content, and a newer source can then fill in the changes made in between. Never overwrite an older backup directly; copy its files into the rebuild folder first, and leave the backup itself untouched.
How should rebuilt files be backed up to stay safe?
As soon as rebuilding is done, move the files to their new working location, and make an independent backup at once. The approach can follow the 3-2-1 rule described in this site's "Hong Kong User Backup Strategy Complete Guide": at least three copies of a file, on two different kinds of media, with one copy in another location. While rebuilt files exist in only one place, the risk is as high as before.
Halfway through rebuilding, some files cannot be found anywhere. What should I do?
First, record those files in the "not yet rebuilt" column of the list, and do not abandon the original-drive follow-up at once. Files not yet rebuilt may depend on the original drive's diagnosis result, or may turn up later from another source, such as a copy held by the other party, a company shared folder, or an application export. Keep the list, so the later reconciliation shows what is still outstanding.
How does this article differ from the three earlier clicking-drive articles?
The three earlier articles cover emergency handling, the decision after stopping and asking for a quote, and judging urgency after powering off — all centred on the original drive itself. This article covers only the other track: while the original drive's result is still unknown, or some files cannot be recovered, how to rebuild data from other copies, compare versions, and keep a list. Original-drive handling is only cross-referenced here, not repeated.