• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

"Delayed write failed" error?

Maximilian

Maximilian

Lifer
I got this error yesterday while i was just surfing the web, The hard drive made a funny noise like a click and then i kept getting delayed write failed errors. So i hit the reset button and the entire contents of drive D: which is all the programs i have was corrupted, chkdisk seemed to fix this later though.

Again today i was playing half life killing gonarch and since he was probably going to waste me i saved the game and half life closed, wayhey i had another delayed write failed error. I didnt hear a noise this time but the hdd did go a bit crazy requiring a reset. No clunking noises or anything that would definately indicate a disk failure, so why am i getting this??

Drive D: is a Samsung 160GB SP1604N (no bad sectors according to chkdisk)
 
The psu? Its a brand new 480 W antec truepower. It shows as 12.10 on the +12V rail according to speedfan. Btw how could the psu be causing this?
 
To answer your question, a delayed write failure is caused when Windows uses write-behind caching. That is, it queues up a disk write to occur, but it doesn't happen.

Check to make sure that your IDE cable is seated correctly. If you have one, be sure to use an 80-pin IDE cable, and connect the HDD to the end of the cable if it's the only drive attached. Go to the HDD manufacturer's website and download their diagnostic utilities and check to see if the drive has any errors. Additionally, try updating your motherboard chipset drivers.

The error could be caused by a damaged/misconfigured motherboard, physically damaged hard drive unit, or damaged HDD controller card.
 
first thing to do is turn off the delayed write (or "write caching", IIRC). The probaility of corrupting the filesystem due to an unplanned shutdown will be reduced immensely.
 
Ok all the porn has been moved to drive C: j/k 😛 and ive d/led samsung HUTIL and it tells me that drive D: is perfect (did surface scan too), it also says on their website that if HUTIL dosent find a problem then it isnt a hardware problem. I dont really buy that 100% but ill go with it for now. Ive turned off "write caching" for drive D: so ill see how it goes. Any more errors and ill get an rma (if i can).

So lets just say it isnt hardware for now, why has this problem surfaced now? why not a few months back?
 
Get Everest.
In its Storage section, click on SMART. You can right-click on any value, and then select copy. Paste that back here. If anything is failing, that's definitely cause for RMA.
 
ID Attribute Description Threshold Value Worst Data Status
01 Raw Read Error Rate 51 100 100 0 OK: Value is normal
03 Spin Up Time 0 253 253 0 OK: Always passing
04 Start/Stop Count 0 253 253 0 OK: Always passing
05 Reallocated Sector Count 10 253 253 0 OK: Value is normal
07 Seek Error Rate 51 253 253 0 OK: Value is normal
08 Seek Time Performance 0 253 253 0 OK: Always passing
09 Power-On Time Count 0 100 100 594 OK: Always passing
0A Spin Retry Count 49 253 253 0 OK: Value is normal
0C Power Cycle Count 0 253 253 0 OK: Always passing
C2 Temperature 0 127 94 37 OK: Always passing
C3 Hardware ECC Recovered 0 100 100 744142 OK: Always passing
C4 Reallocation Event Count 0 253 253 0 OK: Always passing
C5 Current Pending Sector Count 10 253 253 0 OK: Value is normal
C6 Off-Line Uncorrectable Sector Count 10 253 253 0 OK: Value is normal
C7 Ultra ATA CRC Error Rate 0 253 253 0 OK: Always passing
C8 Write Error Rate 51 100 100 0 OK: Value is normal
C9 <vendor-specific> 51 253 253 0 OK: Value is normal
 
Hardware ECC Recovered looks high - 744142. Unfortunately, I'm not entirely sure what this one means - I never see it on my WD drives, my IBM drive doesn't even have that function listed, but the Maxtor drives I use always show a value in the thousands for ECC Recovered.
I've not seen a comprehensive guide to what all those things mean. Read/write errors though aren't a good thingl you're not showing any of those though, nor any reallocated sectors.

I'd think that a 480W Antec PSU should be more than adequate for most systems.

Check the cabling; maybe something did wiggle loose recently. Or maybe the cable is going bad, which could explain that high ECC Recovered figure.
 
Well a while back i had an attempt at rounding the cable, but it was a mess and i cut it open a bit so i can now see copper. Cable still worked fine but this could be causing the probem now.
 
Originally posted by: Soviet
Well a while back i had an attempt at rounding the cable, but it was a mess and i cut it open a bit so i can now see copper. Cable still worked fine but this could be causing the probem now.
Click to expand...

Ah, yes quite possible, especially if you actually broke the wire. Definitely try another cable.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top