Delayed Write Failed

[Rstiltskin]

where does the raid come in, I missed that, blame it on the beer....

I knew you wouldn't like that last post of mine. I thank you for your help. You've been great. But you still haven't offered a comment on the SP2/ Firewire/ RAID/ SATA problems pre update. You're looking at it from a hardware perspective, I am looking at it from a driver/ software perspective. So, how about a comment on the above?

0123456789

 

[fraserhutch]

I knew you wouldn't like that last post of mine. I thank you for your help. You've been great. But you still haven't offered a comment on the SP2/ Firewire/ RAID/ SATA problems pre update. You're looking at it from a hardware perspective, I am looking at it from a driver/ software perspective. So, how about a comment on the above?

Alright, last comment.

The 2nd error message you received indicated a physical error writing to the drive. At this point it has nothing to do with the firewire - if it had you would have seen buffer underrun/overrun errors at the module layer.

So, what in fact appears to have happened (if you can believe WinXp error reporting) is that the physical commit to the disk failed. That's almost always a hardware failure.

Now, I don't recall ever explicitly saying that it was a disk error. I think I said it was likely a hardware error. It likely is, but it could also be a bad SATA cable. I would find it hard to believe that you would get that error from a bad driver, but it is a possibility. It smacks to me of a sector write error. However, if it were a driver error, it is possible that it will not recur. At least now you know how to hunt down the errors.

The virtual memory you were looking has nothing to do with the drive other than that is where the page file will be written. No matter what drive it is stored on, it will be used for all paging. Get rid of the second - you should only have one if you have any at all. And a performance tip - make the min = to the max.

 

[Monkey Allen]

Again mate, thanks for your help. Obviously I will monitor the way things go with this drive over time. I can always come back to this thread and let it help me trouble shoot in future.

Edit: Putting this link here for my future reference and for other people who might be investigating the same error/ problem. Was posted to me by Seagate:

http://support.microsoft.com/default.aspx?scid=kb;en-us;885464

 

[Monkey Allen]

A new link was found by a fella from this forum...similar problem is described...at least the association with problematic 1394 connections and SP2 is mentioned...could be helpful for anyone looking into these issues:


http://support.microsoft.com/kb/885222

 

[Monkey Allen]

In case anyone is reading this thread investigating this problem...none of this stuff fixed my problem. There are pretty serious issues for users of real time audio (or video) writing to a sata slave drive via firewire audio (or video) connected devices while running SP2.