VideoHelp Forum




+ Reply to Thread
Results 1 to 9 of 9
  1. Member
    Join Date
    Jan 2004
    Location
    United States
    Search Comp PM
    Hi,

    I have three internal hard drives, 2 IDE and one sata (all West dig).
    I replaced the secondary IDE (was 80, with a 250). That seemed to go OK. But computer-windows is making me run chkdsk/f on my sata (250GB), (plugged into mobo), which I don't think I originally even touched.
    So far chkdsk has been running about 20 hours, seems to me like it's hung up--but microsoft website says it could take several days for this to complete on a large HD...

    Anyone been down this road before?
    Any quicker way around this---or do I have to let it finish?
    thanks,
    bhb
    Quote Quote  
  2. Member Xylob the Destroyer's Avatar
    Join Date
    Sep 2004
    Location
    Earth, for now
    Search Comp PM
    aren't SATA's supposed to be extra zippy???
    when my cousin's 120G Maxtor got all fucked up, it took the good portion of a day, probably about 10 hours, to run chkdsk.
    the last time I ran it on my 160G though, it only took about 2 hours.
    I guess you could just turn the PC off, but then you'd always wonder about your drive
    "To steal ideas from one person is plagiarism; to steal from many is research." - Steven Wright
    "Megalomaniacal, and harder than the rest!"
    Quote Quote  
  3. Download diagnostic tools from the hard drive manufacturer's website. They are usually quite quick (an hour or two for a full scan) and provide more detailed information.
    Quote Quote  
  4. Member
    Join Date
    Jan 2004
    Location
    United States
    Search Comp PM
    Ok,

    thanks for the suggestions...
    chkdsk has now been running for 27 hours or so and is still at this screen:

    underscore in blinking after last line...
    is it hung up or should I let it go a while longer?

    thanks

    chkdsklocked.jpg
    Quote Quote  
  5. Have you tried chkdsk while in Safe mode? That might speed it up a bit.
    Believing yourself to be secure only takes one cracker to dispel your belief.
    Quote Quote  
  6. Member Krispy Kritter's Avatar
    Join Date
    Jul 2003
    Location
    St Louis, MO USA
    Search Comp PM
    Software from the manufacturer is the best bet, but a full scan will still take a bit of time.
    Google is your Friend
    Quote Quote  
  7. It will prompt to run Chkdsk when it thinks there is a problem with the drive, My experience with SATA is that the early ones are not as reliable as the IDE drives. New one are probably OK.

    I've seen Chkdsk take a long time when the drive is bad. Myself I'd reboot, copy to another drive and run the WD diags on the drive. one way in windows to copy is

    command Prompt using d: as source and E: as destination

    Xcopy D:\ E:\Old_D /e /s /c /r /h /f
    answer D for dirctory. This will copy to to E:\Old_D and continue copy if error, copy Read only and hidden and show files while copying.

    Customer used Maxtor SATA striped, one drive died in a month, lost everything.

    Western Digitals have been pretty reliable. A Samsung SATA (160Gb) died at the one week mark, RMA'd, replacement drive died during 3 year warranty, Took less than a week to get replacement, took all day saturday plus some of monday to get data back and still lost some. My Bad for overlooking making DVDs earlier, That's Life, already moved On.

    Using the Replacement drive as DVD rip to drive when backing up DVDs.
    Quote Quote  
  8. Member
    Join Date
    Dec 2005
    Location
    United States
    Search Comp PM
    Originally Posted by bhbuckeye
    Hi,

    I have three internal hard drives, 2 IDE and one sata (all West dig).
    I replaced the secondary IDE (was 80, with a 250). That seemed to go OK. But computer-windows is making me run chkdsk/f on my sata (250GB), (plugged into mobo), which I don't think I originally even touched.
    So far chkdsk has been running about 20 hours, seems to me like it's hung up--but microsoft website says it could take several days for this to complete on a large HD...

    Anyone been down this road before?
    Any quicker way around this---or do I have to let it finish?
    thanks,
    bhb
    Hi,
    the most common reason for scandisk/chkdisk/defrag to run so long is programs running in the background.. they are interferring and causing the scan to start contiously over.. hense it never finishes....

    common cures...
    a. run checkdisk or defrag in safe mode!!
    b. disable all needless programs that startup at boot..... one of them the culprit
    c. disable culprit program running in the background that interferring.. although it maybe needed to be in startup but it could be interferring, it could be your anti malware program, couldbe your firewall, etc etc......
    d. check for spyware and virus
    Quote Quote  
  9. I'm guessing it is XP and scandisk is running before windows ever loads unless he cancels with the time it allows canceling. When I've seen the pre XP chkdsk take a long time it was trying to recover bad sectors and better to try and get what you can off of the drive and run makers diags instead.
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!