Windows Backup Error: System could not find the path specified

Aethiel

Reputable
Aug 25, 2015
3
0
4,510
Hey guys,
I've been having troubles trying to back up/create a system image of my laptop's hard drive. Every time I try it gives me the following error

30ur31y.jpg


I've run a chkdsk on C: and it came back with 4kb in bad sectors. Here's the log for it

Code:
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  756736 file records processed.                                          File verification completed.
  3669 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              60 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  1042226 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  756736 file SDs/SIDs processed.                                         Cleaning up 53 unused index entries from index $SII of file 0x9.
Cleaning up 53 unused index entries from index $SDH of file 0x9.
Cleaning up 53 unused security descriptors.
Security descriptor verification completed.
  142746 data files processed.                                            CHKDSK is verifying Usn Journal...
  36890456 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  756720 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  6893563 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 442304511 KB total disk space.
 413511032 KB in 569480 files.
    343076 KB in 142747 indexes.
         4 KB in bad sectors.
    876147 KB in use by the system.
     65536 KB occupied by the log file.
  27574252 KB available on disk.

      4096 bytes in each allocation unit.
 110576127 total allocation units on disk.
   6893563 allocation units available on disk.

Internal Info:
00 8c 0b 00 26 de 0a 00 c0 fa 12 00 00 00 00 00  ....&...........
d9 1a 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  ....<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

I've also run the WD Data Lifeguard Diagnostics quick test and extended test: Both returned errors: the Quick saying it didn't complete and the Extended saying that it could not repair bad sectors

Code:
------------------------------
Test Option: QUICK TEST 
Model Number: WDC WD5000BEVT-24A0RT0 
Unit Serial Number: WD-WX81AA0D6829 
Firmware Number: 01.01A02 
Capacity: 500.11 GB 
SMART Status: PASS 
Test Result: FAIL 
Test Error Code: 06-Quick Test on drive 1 did not complete! Status code = 07 (Failed read test element), Failure Checkpoint = 97 (Unknown Test) SMART self-test did not complete on drive 1! 
Test Time: 13:05:11, August 24, 2015 
------------------------------
Test Option: EXTENDED TEST 
Model Number: WDC WD5000BEVT-24A0RT0 
Unit Serial Number: WD-WX81AA0D6829 
Firmware Number: 01.01A02 
Capacity: 500.11 GB 
SMART Status: PASS 
Test Result: FAIL 
Test Error Code: 08-Unable to repair bad sectors. 
Test Time: 15:42:46, August 24, 2015 
------------------------------

I'm kind of at a loss as where to go from here. Any help you guys could provide would be greatly appreciated.
 
Solution
First on the list would be to image the drive, skipping read errors. This will at least grab all the files that are still valid but anything that had data in the bad sectors is already lost. I use linux ddrescue but I'm sure there are other windows tools that can do this skipping errors.

If you dont have a backup of your important files then thats your next priority even though we have made kind of a backup in step1. Make at least 1 copy of those files you cant replace if this drive completely dies.

Next up would be to create your factory restore disk set if you can. Hopefully the bad sectors are not in that partition. This will save you from buying the diskset from the laptop manufacturer.

popatim

Titan
Moderator
First on the list would be to image the drive, skipping read errors. This will at least grab all the files that are still valid but anything that had data in the bad sectors is already lost. I use linux ddrescue but I'm sure there are other windows tools that can do this skipping errors.

If you dont have a backup of your important files then thats your next priority even though we have made kind of a backup in step1. Make at least 1 copy of those files you cant replace if this drive completely dies.

Next up would be to create your factory restore disk set if you can. Hopefully the bad sectors are not in that partition. This will save you from buying the diskset from the laptop manufacturer.
 
Solution

Aethiel

Reputable
Aug 25, 2015
3
0
4,510
Ok so I've finally managed to make a backup. I initially tried Acronis True Image but that failed to make an image (twice, about 16 hours each time -_-). I finally settled on booting from a LiveUSB of Mepis and running ddrescue on the drive. I've now got a 460 odd gigabyte .IMG file on my external now so I'm assuming that it got the whole drive. It did find something like 12 errors totalling about a megabyte on the drive too. I also saved the log of the ddrescue in case that's any help.

Problem is now I have no idea how to get access to the contents of the .IMG file. I've tried mounting it on OSFMount and MagicDisc but it can't access it. How do I get access to the backup files? And do you have any idea on whether I'm better off replacing the HD before it completely fails? Or is it a minor problem and not worth worrying too much about?

ddrescue log
------------------------------
# Rescue Logfile. Created by GNU ddrescue version 1.11
# current_pos current_status
0x72FD5A6C00 +
# pos size status
0x00000000 0xC7304000 +
0xC7304000 0x00001000 -
0xC7305000 0x71364F3000 +
0x71FD7F8000 0x00001000 -
0x71FD7F9000 0x00072000 +
0x71FD86B000 0x00001000 -
0x71FD86C000 0x00071000 +
0x71FD8DD000 0x00001000 -
0x71FD8DE000 0x00072000 +
0x71FD950000 0x00001000 -
0x71FD951000 0x000F4000 +
0x71FDA45000 0x00001000 -
0x71FDA46000 0x00072000 +
0x71FDAB8000 0x00001000 -
0x71FDAB9000 0x7A34B000 +
0x7277E04000 0x00001000 -
0x7277E05000 0x00072000 +
0x7277E77000 0x00001000 -
0x7277E78000 0x85308000 +
0x72FD180000 0x00000800 -
0x72FD180800 0x00000600 +
0x72FD180E00 0x00000200 -
0x72FD181000 0x00073000 +
0x72FD1F4000 0x00000800 -
0x72FD1F4800 0x00000600 +
0x72FD1F4E00 0x00000200 -
0x72FD1F5000 0x003B1000 +
0x72FD5A6000 0x00001000 -
0x72FD5A7000 0x17365F000 +
------------------------------

 

Aethiel

Reputable
Aug 25, 2015
3
0
4,510
Update: So I ran ddrescue again last night and this time the backup seems to be working; I can mount it using OSFMount and read through the contents. Turns out the first backup I did was missing a header table or something. I'm in the process of making a restore disk set now.

I'd still like to know if you have any idea on how long the hard drive's got left in its useful life span. Also probably worth mentioning that it's about 5 years old too
 

popatim

Titan
Moderator
no one can say for sure, even on a brand new drive, which is why backing up important data is so crucial. Even this drive that appears to be failing can last several more years before it fails completely.
I typical stop using a drive for critical data as soon as it comes up with 1 bad sector. if its in warrant I send it back, if its out of warranty I'll use if for something I dont care if i loose like a grandkids gaming pc.