a request to this de device has been cancelled

[amoretam]

Ok, today when I turn on my computer in the morning all of a sudden it took ages to boot, when it booted my D: drive was not showing in MY COMPUTER.

Computer wasvery unresponsive, so I checked the Administrative events and I saw like a hundred of this message:

A request to this device has been cancelled.
Device: \Device\RaidPort0
Model: WDC WD1002FAEX-007BA0
Firmware Version:05.0
Serial Number: WD-WMAUR0614125
Port: 1

I had 3 Sata drives in my system, this one (Wester Digital Caviar Black 1000gb) had my sample libraries and it had just like 19gb of free space.

When I disconnected the drive computer booted normaly.
I dismounted the drive and put it on a usb docking station and it was not recognized and computer was slow again..

I see the BIOS and the HDD shows there.. (strange)

I can't believe my HDD died on me cause I just have like 4 months with him..

What are your advices over this issue??

Thanks a lot people

 

[F5ing]

Try burning this iso to a cd/dvd: WD Support / Downloads / SATA & SAS / WD VelociRaptor

Boot from the optical drive and see what WD's diagnostics program has to say about the drive. (WD's diagnostics program is the same for most of their products, so don't worry if the product on the d/l page doesn't match yours.)

If the drive seems to be only marginally healthy you may want to make sure you backup all data from it before running the tests.

 

[TVeblen]

By any chance do those errors list NVSTOR64 in the description?

 

[amoretam]

By any chance do those errors list NVSTOR64 in the description?

yeah that;s correct

 

[amoretam]

Try burning this iso to a cd/dvd: WD Support / Downloads / SATA & SAS / WD VelociRaptor

Boot from the optical drive and see what WD's diagnostics program has to say about the drive. (WD's diagnostics program is the same for most of their products, so don't worry if the product on the d/l page doesn't match yours.)

If the drive seems to be only marginally healthy you may want to make sure you backup all data from it before running the tests.

ok thanks man i will try that

yeah but how is a test going to alter my data, isn't a test just a test?

Also, could i do the test while the hdd is in the usb docking station, or should i put it back to its sata port??

Thanks a lot man

 

[F5ing]

Modern HD's have firmware that manages the drive and monitors health and degradation. The WD software will access the info acquired by that firmware. More than likely you'll have to have it connected directly (via SATA or PATA, whichever is appropriate for the drive) rather than a USB adapter.

As far as data damage is concerned I'm really talking about drives that are somewhat close to being "on their last leg". If I'm unsure (which is always the case as it's typically someone else's HD I'm messing with) I always back up first because you never know how many more times you'll be able to reliably access the data if the HD is about to die. Stressing an HD in this condition (including just backing it up) may be one of the last times of being able to access it.

That said, running the tests or whatever checks on a healthy drive should not present a problem. I just seem to get a few laptops to repair from folks who've got kids who are kind of rough with the hardware.

I note that you've mentioned checking the drive status in the BIOS. Some BIOS's can read the HD's diagnostics data directly. Might want to try that.

Interested too in TVeblen's post mentioning NVSTOR64 in your error messages. Worth looking in to, especially if you've updated drivers recently.

 

[amoretam]

Thanks a lot man. I'll try with the WD soft tomorrow, so in order to backup my data i need. to have acces to it. I will be able to do that via the software. right? Thanks talk tomorrow

 

[F5ing]

Thanks a lot man. I'll try with the WD soft tomorrow, so in order to backup my data i need. to have acces to it. I will be able to do that via the software. right? Thanks talk tomorrow

You'll have to use something else if you can't use your boot OS to access it. You can run a version of XP to do it. You'll need to burn to another disk and boot from it: Download Hiren (scroll down towards the bottom of the page to find the link to d/l version 15.1).

 

[TVeblen]

That NVSTOR32 error means that the error originates from the nVidia chipset.

Do a google search using the term NVSTOR32 and your exact error message.
"A request to this device has been cancelled. Device: \Device\RaidPort0"

You will see that this is a common problem with some nVidia chipset drivers. Based on what you have, you can decide whether you think it would be best to reinstall or roll back the chipset driver.

Would research more, but I got to get to work!

 

[amoretam]

I have no idea what happened.

First I did this when I read what TVeblen said about nvidia chipsets:

NVSTOR; Lag spikes; Freezing; Stuttering; Sound; Glitches - Windows | Zuki.org.uk

I did the whole procedure but nothing.

Then I followed F5ing advice but the image from WD site did not work with my sata DVD rom, so I downloaded Hirens boot and booted from there, ran Life Guard Diag for an extended test, I waited 2 hours and no errors.

Ok, then I involuntary booted to windows, (I wanted to go to bios), Chkdsk ran automatically and corrected lots of orphaned files and stuff I dont remember like for 10 minutes and booted with the driver visible in My computer!!..and no more messages in event viewer.

what was that??
who ran Chkdsk?
what are orphaned files?
do you think I may have corrupted files?

Then I went to event viewer and saw a couple of messages that said: The files system structure on the disk is corrupted and unusable, please run chkdsk utility volume D:
that message seemed from like 5 minutes before booting............????

Now I remember that this is the second time my D: drive suffer from this issue. The first time I just swapped my sata driver ports and everything went good again..
.....and I remember that chkdsk ran automatically too before booting..

This is strange and I don't want it to happen again!

anyways, I am back to bussines but I would you guys to give me some ideas to prevent this in the future

Thanks a lot

 

[TVeblen]

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.

 

[amoretam]

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

 

[F5ing]

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?

 

[amoretam]

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

 

[F5ing]

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:

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.

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.

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.

 

[amoretam]

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:

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.

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.

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.

Alrite!, thanks a lot for your support.....! very generous of you
bye

 

[F5ing]

You're welcome!

 

[amoretam]

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

 

[F5ing]

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)?

 

[amoretam]

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