LSilver
asked on
Firewire Drive Delayed Write Failure
I recently upgraded from Win2000 Pro to XP Pro (SP2). This problem never occured with Win2000.
I have a FireWire LaCie BigDisk (500 Gig in 2 partitions (drive letters W and Y)). The policies for the drive are "Optimize for Quick Removal" (which disables Write Caching). After the system has been running for a few hours I get the following message in the System Tray: "Windows - Delayed Write Failed : Windows was unable to save all the data for the file Y:\$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere" at which point the drive is Stopped by the OS.
Once the drive is stopped, its icon in DM is flagged with an "!"; the Properties/General window has the following Device-status: "Windows has stopped this device because it has reported problems. (Code 43)"; and clicking Troubleshoot brings up a blank Help & Support Center screen.
1) how can I eliminate this problem or 2) how can I restart the drive.
I have a FireWire LaCie BigDisk (500 Gig in 2 partitions (drive letters W and Y)). The policies for the drive are "Optimize for Quick Removal" (which disables Write Caching). After the system has been running for a few hours I get the following message in the System Tray: "Windows - Delayed Write Failed : Windows was unable to save all the data for the file Y:\$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere" at which point the drive is Stopped by the OS.
Once the drive is stopped, its icon in DM is flagged with an "!"; the Properties/General window has the following Device-status: "Windows has stopped this device because it has reported problems. (Code 43)"; and clicking Troubleshoot brings up a blank Help & Support Center screen.
1) how can I eliminate this problem or 2) how can I restart the drive.
And it can also be a bad connection of this drive; open the case and check or replace the cables and connections
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check the following http://support.microsoft.com/?kbid=330174
also http://forum.kaspersky.com/lofiversion/index.php/t1432.html
also http://forum.kaspersky.com/lofiversion/index.php/t1432.html
ASKER
nobus: I'm fairly sure the drive didn't suddenly and coincidentally go bad; and nor did its connections when I upgraded to XP :) . Also, being a FireWire drive, it has no IDE connector.
JBlond: The article you reference has to do with performance. The drive acts just fine (it's not accessed very much) until I get the "delayed write error" -- so I suspect this is not the problem.
1stITMAN: I've now modified my Cache from System to Programs and will see what affect that has (your 2nd suggestion). Your first suggestion's reference had to do with UDMA (which I don't have) and disabling the disks write caching which is already true. The article on Kaspersky has no useful info and the link therein to 'write failed' is broken
JBlond: The article you reference has to do with performance. The drive acts just fine (it's not accessed very much) until I get the "delayed write error" -- so I suspect this is not the problem.
1stITMAN: I've now modified my Cache from System to Programs and will see what affect that has (your 2nd suggestion). Your first suggestion's reference had to do with UDMA (which I don't have) and disabling the disks write caching which is already true. The article on Kaspersky has no useful info and the link therein to 'write failed' is broken
>> it has no IDE connector<< are you sure about that ? i do not know a drive with a firewire connection, they all have ide connections
Do you have updated the firmware as described here?
http://www.lacie.com/download/drivers/ReadMeFW800SP2.pdf
http://www.lacie.com/download/drivers/ReadMeFW800SP2.pdf
ASKER
nobus: I'm really sure that there's no ide connection - a Firewire cable connects the drive to the Firewire port.
JBlond: I had seen this on the LaCie site but I must have mis-read it; so I didn't think that it applied to my situation. I'll attempt to apply it and see what it does.
JBlond: I had seen this on the LaCie site but I must have mis-read it; so I didn't think that it applied to my situation. I'll attempt to apply it and see what it does.
>> I'm really sure that there's no ide connection - a Firewire cable connects the drive to the Firewire port << from the external case to the port, yes; but inside the case the drive has an ide connector...
ASKER
nobus: aah - I guess I didn't realize what you were talking about. I don't think I would know how to get into the case (I'm not very mechanically inclined :)) and, like I said in my first response to you, I really doubt the drive or its interface coincidentally went south when I upgraded the os.
>> I don't think I would know how to get into the case (I'm not very mechanically inclined << then let a techie friend have a look at it. I don't say it is bad, but ther is always a possibility, and without testing it, you cannot know.
You could test the drive on another PC, to make sure the problem is not coming from the PC
You could test the drive on another PC, to make sure the problem is not coming from the PC
With SP2 some things changed with the firewire support in XP. (new drivers...)
After releasing SP2, some bugs were detected, so I would update the firmware/drivers to the most current versions, to rule out such things.
After releasing SP2, some bugs were detected, so I would update the firmware/drivers to the most current versions, to rule out such things.
ASKER
nobus: Along with the firmware/driver download came a diagnostic program. When I ran it, it showed no errors on the drive.
JBlond: I downloaded the latest firmware from LaCie and the installer said that the drive was already up to date.
I modified the Cache settings and it took about 4 1/2 hours for the problem to recur. Disconnecting/reconnecting
JBlond: I downloaded the latest firmware from LaCie and the installer said that the drive was already up to date.
I modified the Cache settings and it took about 4 1/2 hours for the problem to recur. Disconnecting/reconnecting
ASKER
JBlond: I've also applied KB885222 as you suggested much earlier. I should find out in about 4 hours if that cures the problem -- the problem seems to occur after the system has been up for that amount of time.
>> the problem seems to occur after the system has been up for that amount of time. << then it can be a heat issue. check for drive and PC if all fans are running, clean system and drive from dust, check if the heatsink is fully seated on the cpu.
ASKER
It looks like the application of KB885222 solved the problem. I applied the fix at 9pm and at 7:30am the drive is still operating normally.
If not, the drive can be faulty; you can hook it directly to an IDE cable, and save the data.