If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Chkdsk.exe
I have a friend who is too lazy to post his own problems. He bought a
high capacity drive. The drive started running chkdsk at reboot. He got a replacement from Seagate. The second drive is also running chkdsk at startup. Since this happened on two brand new drives, I told him that getting a new controller card may help. He has been still writing to the drives while waiting on the controller card. Does chkdsk fix errors, or just mark sectors as bad? Anyone else think a controller will fix his problem? |
#2
|
|||
|
|||
Chkdsk.exe
"Metspitzer" wrote in message
... I have a friend who is too lazy to post his own problems. He bought a high capacity drive. The drive started running chkdsk at reboot. He got a replacement from Seagate. The second drive is also running chkdsk at startup. Since this happened on two brand new drives, I told him that getting a new controller card may help. He has been still writing to the drives while waiting on the controller card. Does chkdsk fix errors, or just mark sectors as bad? Anyone else think a controller will fix his problem? If this is a Windows PC tell your friend about the MS "Knowledge Base" where utilities like CHKDSK are fully documented or teach him how to search via Google. The point is that this is usually much faster than waiting for a reply in a NG. -- Don Phillipson Carlsbad Springs (Ottawa, Canada) |
#3
|
|||
|
|||
Chkdsk.exe
Metspitzer wrote:
I have a friend who is too lazy to post his own problems. Ha! -- Mike Easter |
#4
|
|||
|
|||
Chkdsk.exe
Metspitzer wrote:
I have a friend who is too lazy to post his own problems. He bought a high capacity drive. The drive started running chkdsk at reboot. He got a replacement from Seagate. The second drive is also running chkdsk at startup. Since this happened on two brand new drives, I told him that getting a new controller card may help. He has been still writing to the drives while waiting on the controller card. Does chkdsk fix errors, or just mark sectors as bad? Anyone else think a controller will fix his problem? CHKDSK can stay in a loop, running at each startup of the system. There is a "dirty" flag, which can be set, to indicate the file system needs to be checked. And sometimes, the flag doesn't get cleared after CHKDSK runs. Maybe your problem is something like that. fsutil dirty query C: http://technet.microsoft.com/en-us/l.../bb490641.aspx The flag can be queried or it can be set (to request a CHKDSK), but it cannot be cleared with that command. And the location of the flag is not documented on purpose, so people cannot bypass it. It is only supposed to be cleared, when CHKDSK is happy. You can try booting the Recovery Console using the WinXP disc, and do a chkdsk from there. Perhaps that might clear the flag. The options available in chkdsk, vary depending on where you run it from. The options in Recovery Console are different than the ones elsewhere. These are a couple links from my bookmarks. The second one is pretty easy to read. http://support.microsoft.com/kb/314835/EN-US/#/ http://www.answers.com/topic/chkdsk-1 Paul |
#5
|
|||
|
|||
Chkdsk.exe
On Fri, 15 Jan 2010 19:35:51 -0500, Paul wrote:
Metspitzer wrote: I have a friend who is too lazy to post his own problems. He bought a high capacity drive. The drive started running chkdsk at reboot. He got a replacement from Seagate. The second drive is also running chkdsk at startup. Since this happened on two brand new drives, I told him that getting a new controller card may help. He has been still writing to the drives while waiting on the controller card. Does chkdsk fix errors, or just mark sectors as bad? Anyone else think a controller will fix his problem? CHKDSK can stay in a loop, running at each startup of the system. There is a "dirty" flag, which can be set, to indicate the file system needs to be checked. And sometimes, the flag doesn't get cleared after CHKDSK runs. Maybe your problem is something like that. fsutil dirty query C: http://technet.microsoft.com/en-us/l.../bb490641.aspx The flag can be queried or it can be set (to request a CHKDSK), but it cannot be cleared with that command. And the location of the flag is not documented on purpose, so people cannot bypass it. It is only supposed to be cleared, when CHKDSK is happy. You can try booting the Recovery Console using the WinXP disc, and do a chkdsk from there. Perhaps that might clear the flag. The options available in chkdsk, vary depending on where you run it from. The options in Recovery Console are different than the ones elsewhere. These are a couple links from my bookmarks. The second one is pretty easy to read. http://support.microsoft.com/kb/314835/EN-US/#/ http://www.answers.com/topic/chkdsk-1 Paul Thanks Do you know how this could happen on two new drives? The first drive he bought was new when it started the errors, but the replacement drive is doing the same thing. He has other drives that are not doing this. The drives are at least 1TB The may even be 1.5TB. |
#6
|
|||
|
|||
Chkdsk.exe
Metspitzer wrote:
On Fri, 15 Jan 2010 19:35:51 -0500, Paul wrote: Metspitzer wrote: I have a friend who is too lazy to post his own problems. He bought a high capacity drive. The drive started running chkdsk at reboot. He got a replacement from Seagate. The second drive is also running chkdsk at startup. Since this happened on two brand new drives, I told him that getting a new controller card may help. He has been still writing to the drives while waiting on the controller card. Does chkdsk fix errors, or just mark sectors as bad? Anyone else think a controller will fix his problem? CHKDSK can stay in a loop, running at each startup of the system. There is a "dirty" flag, which can be set, to indicate the file system needs to be checked. And sometimes, the flag doesn't get cleared after CHKDSK runs. Maybe your problem is something like that. fsutil dirty query C: http://technet.microsoft.com/en-us/l.../bb490641.aspx The flag can be queried or it can be set (to request a CHKDSK), but it cannot be cleared with that command. And the location of the flag is not documented on purpose, so people cannot bypass it. It is only supposed to be cleared, when CHKDSK is happy. You can try booting the Recovery Console using the WinXP disc, and do a chkdsk from there. Perhaps that might clear the flag. The options available in chkdsk, vary depending on where you run it from. The options in Recovery Console are different than the ones elsewhere. These are a couple links from my bookmarks. The second one is pretty easy to read. http://support.microsoft.com/kb/314835/EN-US/#/ http://www.answers.com/topic/chkdsk-1 Paul Thanks Do you know how this could happen on two new drives? The first drive he bought was new when it started the errors, but the replacement drive is doing the same thing. He has other drives that are not doing this. The drives are at least 1TB The may even be 1.5TB. If I have computer crashes here, not all the partitions are checked, so I don't know what would kick off the whole process. I've had my C: checked a few times, but never got stuck in a loop. Paul |
#7
|
|||
|
|||
Chkdsk.exe
Metspitzer wrote:
high capacity drive. The drive started running chkdsk at reboot. He got a replacement from Seagate. Normally a drive mfr 'requires'/wants the user to run their diagnostics such as SeaTools in this case, in order to issue an RMA to initiate the standard warranty replacement process. What happened when he ran the diagnostics on the first drive? http://snipr.com/u3qtd How to use SeaTools for Windows The second drive is also running chkdsk at startup. .... or the second? http://snipr.com/u3qtq My desktop or laptop hard drive may be defective, how can I test it? ... Over 30% of all drives returned under warranty to Seagate are in good working order, with no problems found. To save time and the hassle of shipping a drive that may not be defective at all, please test your drive to see if it really is defective. -- Mike Easter |
#9
|
|||
|
|||
Chkdsk.exe
On Fri, 15 Jan 2010 13:58:57 -0500, Metspitzer wrote:
I have a friend who is too lazy to post his own problems. He bought a high capacity drive. The drive started running chkdsk at reboot. He got a replacement from Seagate. The second drive is also running chkdsk at startup. Since this happened on two brand new drives, I told him that getting a new controller card may help. He has been still writing to the drives while waiting on the controller card. Does chkdsk fix errors, or just mark sectors as bad? Anyone else think a controller will fix his problem? Once upon a time, many years ago, I purchased a Seagate IDE drive for a computer (this was before GB drives). I had nothing but problems with the drive, lots of read/write errors, etc. Seagate had me low level format the drive (so you know how long ago this was) with no joy, still problems with the drive. They sent me a replacement. Still problems. Turned out there was a firmware problem with that particular model of drive that they hadn't discovered yet. After speaking with numerous technicians over the phone, one finally sent me a copy of the new firmware. When that was installed, all problems disappeared. My point is, even with new drives there can be problems that aren't even realized by the manufacturer at first. Patty |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
CHKDSK error | alfo | Storage (alternative) | 0 | October 12th 09 09:21 AM |
CHKDSK | Keith Wilby | Storage (alternative) | 5 | December 15th 06 10:54 PM |
CHKDSK always checking | Angelfood MacSpade | Storage (alternative) | 0 | January 17th 04 07:44 PM |
Any use for "chkdsk /R" ? | David Arnstein | Storage (alternative) | 4 | January 9th 04 09:45 PM |
CHKDSK /F won't run | JD | General Hardware | 1 | October 28th 03 10:26 PM |