New
#1
Is this bad? 1464 pending sectors on my HD but 0 reallocated
Here is a screen shot, it is a western digital black 1tb drive. Should I replace it?
I have a backup of all my important stuff on an external drive.
Here is a screen shot, it is a western digital black 1tb drive. Should I replace it?
I have a backup of all my important stuff on an external drive.
SMART details are too cryptic for mortals to understand, but I'd download and run the Western Digital disk utilities and see what it says.
I'm guessing you are not under warranty?
I have, and I am. Here ya go!
It sais it is ok on there... but other tools say nay! So.. I dont know what to make of it. BTW if I run a quick test, it fails. If I try an extended test, it blue screens.
I managed to get it to chkdsk /r! I did it off a windows disk, but it did say "failed to transfer logged messages to the event log with stats 50" after it finished.
What yall think?
I'd run a "chkdsk /f /r /x /b" (on the correct drive, not C:\ for sure). and see if it goes better. then rerun all tests.
Code:C:\>chkdsk /? Checks a disk and displays a status report. CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B] volume Specifies the drive letter (followed by a colon), mount point, or volume name. filename FAT/FAT32 only: Specifies the files to check for fragmentation. /F Fixes errors on the disk. /V On FAT/FAT32: Displays the full path and name of every file on the disk. On NTFS: Displays cleanup messages if any. /R Locates bad sectors and recovers readable information (implies /F). /L:size NTFS only: Changes the log file size to the specified number of kilobytes. If size is not specified, displays current size. /X Forces the volume to dismount first if necessary. All opened handles to the volume would then be invalid (implies /F). /I NTFS only: Performs a less vigorous check of index entries. /C NTFS only: Skips checking of cycles within the folder structure. /B NTFS only: Re-evaluates bad clusters on the volume (implies /R) The /I or /C switch reduces the amount of time required to run Chkdsk by skipping certain checks of the volume.
lotsofjam,
This is WIN 7 and not XP are still older.
In that time, chkdsk has evolved.
The only meaningful format for you is:
CHKDSK X: /R
where X is one of your drive letters.
Run chkdsk x: /r
over EACH of your drives.
When finished let me know as I've a script that will let us view the results.
WIN 7 put the chkdsk results into the EventLogs and the script extracts the eventlog entries that we need.
If at anytime a chkdsk fails, then run chkdsk again. Run up to 3 times of a drive that fails.
I have ran it three times already, the only time I managed to get it to work is when I ran it off a windows disk. It threw up an error telling me that it couldnt log it that time too. I have strted a new thread in crashes and debugging to investigate the Blue screens here:- https://www.sevenforums.com/crashes-d...ml#post2104308