I would definitely check to see if your motherboard manufacturer has an updated chipset driver.
Even if they don't it might be a good idea to uninstall and reinstall the driver.
I would also still run the drive diagnostic as soon as you can. See if you can burn the ISO on another PC.
Glad to hear you are up and running.
Last edited by TVeblen; 28 Jun 2012 at 06:05. Reason: Spelling
that s what I did following the link I posted!
downloaded and installed latest chip-set driver but not the Storage drivers (inside the drivers package) because they cause problems as he said..
thanks
So you ran WD diagnostics via Hiren's and found no problems, right? SMART revealed a healthy disk?
Those orphan files found by chkdsk are recovered files that the file system does not know where to place in the folder structure, or something along those lines (as far as I recall). I've found that most of the time they are remnants of temporary working files that can be deleted anyway.
And you've got it all up and running great?
No loss of data?
I don,t know for sure, That disc is a huge sample library for my Virtual Instruments. I cannot know for sure until I play all of those instruments to find out, and that is going to take forever....isn't there any other way to find out?
Also I still don,t know what happened...
would you please be so kind to help me understand what happened answering my questions in my last post? That is to prevent this from happening again, because if it happens in the middle of a session I am screwed.
Thanks man
It's really hard to say what happened. I would keep an eye out for those error messages in event viewer. If you removed and did not reinstall the storage driver I would guess you wouldn't get those warnings/errors any longer.
As far as chkdsk automatically running during your accidental reboot, it sounds like Windows may have set the dirty bit for that volume. The quote below is from MS command line reference for the FSUtil command and describes a little about why a chkdsk might be triggered on reboot:
Browse around the drive's folder structure to see if you notice anything unusual, anything that jumps out at you. Hopefully you were already somewhat familiar with it's folder structure. I don't think you have to "play all of those instruments to find out" but if you successfully "play" a certain percentage of them, without ever running into a problem, you can certainly feel more confident about it. The higher percentage the better.If a volume's dirty bit is set, this indicates that the file system may be in an inconsistent state. The dirty bit can be set because the volume is online and has outstanding changes, because changes were made to the volume and the computer shutdown before the changes were committed to disk, or because corruption was detected on the volume. If the dirty bit is set when the computer restarts, chkdsk runs to verify the consistency of the volume.
Every time Windows starts, Autochk.exe is called by the Kernel to scan all volumes to check if the volume dirty bit is set. If the dirty bit is set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f verifies file system integrity and attempts to fix any problems with the volume.
In addition to keeping an eye on event viewer I would do two more things:
- Find a way to back up all that data if it is important to you in any way.
- Download the Window's version of WD Diagnostics from that same page I posted a link to. Just to keep an eye on that disk from time to time.
hey how you doing F5ing..
Here I come again with the same problem and same disk but this time Event Viewer says: the file system structure on the disk is corrupt and unusable please run the chkdsk utility.
When I run chkdsk it gets stuck at 73% and says: an unknown error occurred and something could not be corrected (something like that).
I ran WD diag utility quick test and results were PASS.
It is the second time it happens when I try to connected with this external power supply: Amazon.com: USB 2.0 to SATA/IDE Cable Adapter For 2.5 3.5 HDD: Computers & Accessories
Maybe that Psu don't have enough power for a tb hdd??
I don't know but the most important now is that I don't loose all my data, remember that drive only has 20gb free.
Please let me know what can i do
Thanks a lot
Sorry to see that problems with that drive have surfaced again.
When you do gain access again, you really ought to consider backing up all its data somewhere.
I've got a couple of those PATA/SATA to USB adapters. Both power supplies state they supply 1.5 amps for both 12v and 5v. I looked up specs for a couple of WD's 1TB drives and they state they consume 1.65 amps peak (I imagine that implies at power up). But I've used those same power supplies with many drives and never had an issue, even with 2TB drives requiring 1.75 amps peak.
Look in event viewer and search for wininit and/or chkdsk entries to find the results of the chkdsk that ran and could not repair whatever it was. When you find it you can post it here and we can take a look at it.
Did you run the WD diagnostics/test while connected to the adapter or straight to the motherboard? What did it say about SMART (ok/warning/fail)?
when the hdd did not wanted to boot I inmediately disconnected it from that adapter.
I ran WD diag/test while connected to the mobo..
right now i am running a chkdsk /r D: from the dvd installation (been reading around). It is stuck at 28% but it's been just 20 minutes, let see.
i will check for wininit when it's done and post results..
Than ks
Quote