Can not Read Part of Hard Drive

This will allow the backup to continue in most cases, but does not guarantee that the content in the backup is not corrupted.  When you run chkdsk on C:, it is just running on that partition.  Corruption may be  in your boot or recovery partitons and will not be scanned with the C: drive dskchk.  You can, however, use your Windows recovery disk and mount those paritions with drive letters and then run chkdsk on those as well.  You don't necesarily have to do this with your Windows recoveyr media, but I'd recommend it so that the partions don't remain mounted with drive letters after that.  Using the recovery disk to do this will only temporarily mount them with drive letters during that recovery session (basically, you're just using the recovery sessioni command prompt to run these commands). 

http://superuser.com/questions/518634/running-chkdsk-on-a-disk-partitio…

What you will have to do is use DISKPART

First, open up command prompt.

1.Goto start menu.

2.Type cmd and open it

3.Once in Command Prompt type

DISKPART

4.Then you are going to type

List Disk

5.Find your disk that has the file size of 69.71 GB

6.Then you need to type

List partition

7.Once you find the partition that you are wanting to run a chkdsk on look next to the partitions and they should be labeled by numbers. so choose the number of the partition and write the following command

Select partition 1

8.But replace the 1 with whatever number your drive letter is then type

Assign

9.That will then assign the partition a drive letter then you can run a chkdsk on that drive

Type exit to leave diskpart

then type chkdsk D: /f /r

10.Replace "D:" with whatever drive letter it is for your drive.

Thank you very much for your reply and the info you included, I will give this a try shortly.

The backup has now completed successfully, I had the verify the backup checked, so does this mean the backup will be ok, not corrupted? I am imagining seeing as it ignored the errors of the bits it could not read, that there will be things missing? (forgive my lack of knowledge)

Thanks

Jeff

(I don't suppose it matters, but I had Windows 7 Pro in my sig, but it actually now Windows 10 Pro, I have updated my sig)

It's good news that not only did the backup complete after ignoring errors, but also that the verification completed  However, the verification only means the backup is good, but doesn't necessarily mean the content in it is good.  Typcially, if your machine is working fine, then the ccontent backed up in it is fine too, but if files have been corrupted on the disk, then those files will remain corrupted in your backups as well.  

Long story short, you're backup should be usable as your system is usable as it is now though, but that is a "should" and not a guarantee although I'd be more inclined to say yes it is good, than no it's not in this case.

You may want to download the free version of hard disk sentinel and see what it says about your disk.  It will tell you the remaining life and if there are still errors on it.  If it's below the 30% realibility thresh-hold, then it may be time to consider replacing it. If it shows it's good, then I wouldn't worry about things too much, but would keep on taking regular backups and test restoring them to another drive from time to time and swapping the original drive with the resotred one to make sure it does boot as intended. 

I done the stuff in your first reply(the DISKPART stuff) and it turned up no problems. All drives and partitions return no errors.

I will look into Hard Disk Sentinel. I do not really like installing stuff on that PC as it is purely for music production and I keep it as clean as possible keeping anything unrelated away. It runs fine, as fast as ever and I have no problems, except for TI2016 telling me it can't read something.

Thank you very much for your help

Jeff

Interestingly, using TI 2017 it goes through the backup process without a hitch, nothing has changed (except more software has been installed/updated) hard drives are the same, all the same hardware, no attempt to fix the supposed problem was made, as Windows said there was nothing to fix. Luckily I haven't needed to use a backup, but I do feel a little more confident now that the process goes through hitch free :)

Sorry to resurrect the dead, just thought I would add the finding to the old thread.

cya