ATI 2012 Failed to Read Error On Win 7 64 bit 128 Gb Crucial SSD
My setup: AMD X2 5200, Crucial 128Gb SSD hard drive, Windows 7 Professional 64bit
My problem: I'm unable to create a backup image of my new Crucial SSD hard drive with out getting the below error.
"Failed to read from sector '1,953,525,167' of hard disk '3'. Try to repeat the operation. If the error persists, check the disk using the Check Disk Utility and create a back up disk. Failed to read the snapshot manager drive. (0x1000D7) Unknown status. (0x9) The drive cannot find the sector requested."
I have run chkdsk /r on the drive to no effect multiple times after its dismounted from a restart. chkdsk reports no errors on the drive each time in the logs.
This is a fresh install on a brand new hard drive. I initially ran Acronis Report, saw errors and RMA'd the drive to get this new one. When I run acronis report even after multiple chkdsk passes, it reports that there are errors on the drive. I've attached the report below. As an aside, when I run Acronis Report on my laptop at work it returns that the drive has errors as well, though chkdsk reports no errors. The drive on that laptop is a crucial SSD as well. That laptop is running windows 7 home 32bit.
I am able to use my machine without issues. I have sucsessfully created an image using Windows 7 Backup and restored it sucsessfully.
Thanks so much for your help!
Thanks GroverH! I ran chkdsk a second and third time using your suggestions. Here's the log for the third trial:
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 3)... 225024 file records processed. File verification completed. 268 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 279096 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)... 225024 file SDs/SIDs processed. Cleaning up 8 unused index entries from index $SII of file 0x9. Cleaning up 8 unused index entries from index $SDH of file 0x9. Cleaning up 8 unused security descriptors. Security descriptor verification completed. 27037 data files processed. CHKDSK is verifying Usn Journal... 36598712 USN bytes processed. Usn Journal verification completed. Write failure with status 0xc0000015 at offset 0x1dc8f4de00 for 0x200 bytes. The second NTFS boot sector is unwriteable. Internal Info: 00 6f 03 00 dc 4b 02 00 ba 6f 04 00 00 00 00 00 .o...K...o...... d7 00 00 00 2c 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.
This third trial CHKDSK finds the same error. What's up with that "write failure" message. Does this SSD have bad sectors? The SSD is brand new, as was the previous one I RMA'd. What are my next steps here?
THanks again for your help and time,
Jesse
Using Windows Disk Management, shrink the last volume on the drive a little (a few MB's) and rerun chkdsk to see if the error clears up.
If not, you can use the Windows command line utility "diskpart" to clean the partition information off of the drive while booted to the Windows 7 installation media, and re-install Windows.
Thanks James,
My understanding of SSDs was that they wrote evenly across all cells in the drive. A few clarifying questions:
1. By shrinking the drive am I assuming that a sector is physicallyl bad?
2. This is a brand new drive on a fresh install. Should I just RMA the drive a second time?
3. With three drives posting similar errors on acronis report is this indicitave of a separate hardware issue?
Thanks James H. Your fix got rid of the second sector unwritable error message. CHKDSK /F is still finding but not fixing errors on the drive in the same location. I've attached the log.
So some of my questions remain:
1. By having to shrink the volume and with persistent error reports, is this drive bad?
2. Why have multiple installations on three separate drives all reported similar errors? All installations were created using the same pc hardware.
Thanks again for everyone's help!
You may want to check to see if there is a BIOS update for the system you are using to create the installations.
It appears as though the BIOS is seeing the drive with different characteristics than the actual drive possesses.
When installing any new drive, it is a good idea to use the Windows command line tool "diskpart" to clean the drive of any structure (MBR/GPT/partition) information before the install. This normally will "match" the drive to the system controller using the correct geometry.
Without further analysis of your PC, I can not offer any other explanation to you.
The persistent errors you are seeing in chkdsk about security descriptors can be caused by a variety of issues.
Do a search on your favorite search engine for "Windows 7 Cleaning up unused index entries from index $SDH of file 0x9" and you will find many others with the same issues. This can be caused by incorrect shutdown, security software, poorly written applications, etc.
An update:
Acronis seems to be working now without posting an error. After your suggestion James I went to my bios settings to check what was going on. RAID was enabled and my drives were plugged in to the wrong channels on the motherboard to be RAID compliant (they needed to be on channel 1 and 2; I had them on 0 and 1). I didn't realize RAID was enabled by default in the BIOS so I disabled it.
I imagine that this caused reference issues between files on the two disks.... Weirdly though Acronis Report still reports errors on the SSD drive even though CHKDSK now reports none. Is Report seeing an error that isn't there (possibly having to do with the different way SSD's are organized from standard hard drives)?
Now that I've disabled RAID, will I encounter future problems on a drive that was initially set up for RAID?
Thanks so much everyone!
Moving the drives to new controller positions after installing Windows could be very problematic. In addition, disabling the RAID setting could cause problems as well. This is similar to taking the drive and placing it in a new system with different hardware.
After installing Windows, the installation disk drive should not be moved from one controller position to another, and the operating mode the controller is in should not be changed. Enabling RAID does not create a RAID automatically, but usually puts the controller in AHCI mode vs native IDE.
Normally you would want to leave the controller in RAID mode even for non-RAID setups, as it usually enables AHCI, which is desirable.
Your first hard disk (primary drive) should normally be connected to the "0" connector on your controller. Any additional drives would need to be connected according to the use planed for the drive.