Delayed Write Failed with Quick-Serv PENR-35U2

[archcommus]

I have a Maxtor 80 GB enclosed in an el cheapo USB enclosure. I have no problems transferring small files to it, but anytime I try to transfer large ones (few hundred megs or more) it will stop responding a ways into the transfer, the light will stay on orange, and a Delayed Write Failed error will pop up in my tray.

Now, of course I'm not positive, but I'm betting that if I took the Maxtor out of the enclosure and put it inside another system, it would work fine. I also know the problem is not the USB ports or controller from my computer as the motherboard is brand new, and I also had this problem with this external drive/enclosure on my old system.

So would your first guess be to think it's the controller in the cheap enclosure causing the problem?

 

[ProviaFan]

Originally posted by: archcommus
So would your first guess be to think it's the controller in the cheap enclosure causing the problem?

Yes. The certain way to tell would be to connect the drive directly to the motherboard, which is something you should probably do as a troubleshooting step. But regardless, my guess would be on the controller in the external enclosure.

 

[archcommus]

Would the controller also be the cause of the slow transfer speeds? All USB on my motherboard is USB2, and the enclosure is advertised as USB2, yet it only averages roughly 6 MB/sec or so when transferring. Isn't USB2 supposed to be capable of 480 Mbps, which is 60 MB/sec?

 

[corkyg]

There is an easy fix for this - and it should done to all external drives. What you do is disable the Disk Write Caching for that drive:

1. Right-click My Computer, and then click Properties.
2. Click the Hardware tab.
3. Click Device Manager.
4. Click the plus sign (+) next to the Disk Drives branch to expand it.
5. Right-click the drive on which you want to enable or disable disk write caching, and then click Properties.
6. Click the Disk Properties tab.
7. Click to select Policies.
8. Deselect Performance

This fix also allows you to hot plug and unplug the drive with out regard to the safe removal procedure.

 

[archcommus]

Thanks, but it's already set. I'm going to pull the drive from the enclosure, hook it up internally, and run DFT on it to make sure the drive's alright.

 

[corkyg]

OK - here's the Microsoft KB on it:

330174

I think your drive's OK - this is a very commpn problem with external drives, but it's an easy fix.

 

[Nick5324]

I had this problem once with a firewire drive. I found the firewire cable in the back was coming out, sigh. However, i think your situation is the controller.

 

[RKS]

Originally posted by: corkyg
There is an easy fix for this - and it should done to all external drives. What you do is disable the Disk Write Caching for that drive:

1. Right-click My Computer, and then click Properties.
2. Click the Hardware tab.
3. Click Device Manager.
4. Click the plus sign (+) next to the Disk Drives branch to expand it.
5. Right-click the drive on which you want to enable or disable disk write caching, and then click Properties.
6. Click the Disk Properties tab.
7. Click to select Policies.
8. Deselect Performance

This fix also allows you to hot plug and unplug the drive with out regard to the safe removal procedure.

I had the same problem a few days ago. I found this work-around through Google, tried it, didn't work

 

[Zepper]

That transfer rate is very slow.
. Actually hooking the HD internally to the OP's system proves nothing except that the HD is good. Is the drive jumpered properly for use in the external box. Some require Cable Select, others require Master (make sure it's jumpered Master-Stand Alone if it's a WD and the box requires Master).
. You may have USB 2 high speed ports, but are you sure the HS USB drivers and patches have been installed and actually took on the port(s) you are using.
. How about the cabling? Are you sure the cable on the external drive is HS rated and that the shield is connected end-to-end? And if you are using the box connected to a front port, are you sure the cable from that port to the mobo is HS rated, shielded, and the shield connected end to end? Have you connected any other high speed device to that same port and had it work at high speed? You need to be able to check all those things off before you can be sure about calling the converter in the external box bad.

.bh.

 

[archcommus]

The transfer rate is much better now. I was experiencing slow internal transfers, as well, turns out my internal drive was in PIO mode. Now I average 15-25 MB/sec when transferring to the external drive.

So now the only issue is the Delayed Write Failed errors, not so much speed. Should I try that registry hack listed in that KB article posted by corkyg?

 

[Zepper]

You for sure want to disable delayed writes to external drives.

.bh.

 

[archcommus]

And where is that done?

 

[archcommus]

Transfer rates are better now that I enabled UDMA Mode 5 on my internal drive, but the Delayed Write Failed errors are still frequent. Is that registry hack in that KB article my only option save getting a new enclosure?

 

[corkyg]

Originally posted by: archcommus
And where is that done?

That is what I gave you a few days ago - that is how to disable write caching for an external drive.

My problem is that the change of performance option is grayed out, because my "external" SATA is really an internal connection to an external case.

In the meantime, I am looking for a RegEdit fix.

 

[archcommus]

Originally posted by: corkyg

Originally posted by: archcommus
And where is that done?

That is what I gave you a few days ago - that is how to disable write caching for an external drive.

My problem is that the change of performance option is grayed out, because my "external" SATA is really an internal connection to an external case.

In the meantime, I am looking for a RegEdit fix.

Oh, right. I figured he was referring to the same thing, but I wasn't sure.

When using my sync software it happens almost immediately when it tries to start transferring a very large file. When it's doing smaller files, it almost never happens at all. For large files, when I try to copy them over myself through Explorer, it will usually have a bit more success, but will still happen eventually.

Does that registry hack apply to my situation?

 

[archcommus]

I tried the registry hack, it slowed things down a bit but it was going good for a long time so I thought it fixed it. But, alas, it did end up getting the error again, just much later than usual.

So you really think the controller is just...broken? I'm not sure what the word for it is. It WORKS but does this. Just seems odd, makes me think the issue is something else.

 

[corkyg]

If write caching is turned off, you really can't get a Delayed Write Error. Are you sure you turned it off? Check it this way:

1. Get to Device Manager (CP/HW/DM)
2. Select the external drive in question
3. Right click on it to select PROPERTIES
4. Then click on the POLICIES tab.

You have two choices. The default is the lower - Performance. To stop write caching, select the upper one - optimize for quick removal.

That turns off write caching, and you should not get a DWF after that.

 

[archcommus]

Yep. Device Manager, expand Disk drives, view properties of the drive, Policies tab, Optimize for quick removal is selected. So it must be possible to get that error even with write caching disabled.

The enclosure is a Quick-Serv PENR-35U2. Maybe if I can find out what controller it uses I can get updated firmware?

 

[archcommus]

Well, this issue is probably not due to my system, as the motherboard is new, and I'm running all the latest drivers. Plus I experienced this with my last system and this enclosure, as well.

I just tried defragging and it gave me the error only a few percent in. Remember, I have done the registry hack, and I've disabled write caching.

I will pull the drive and test it internally to be sure it's not that. If the drive's fine, go out and buy a new enclosure?

If we can find out what controller this uses, I may be able to get new firmware!