Capture problem with new hard disk

[eJim]

I’ve been capturing from both external A/V sources and from an internal TV tuner for a couple of months with no real problems. So, I purchased an installed a second HD and now I’m having a problem.

Here’s what been working fine so far:

Sony VAIO PCV-RX380DS
256MB RDRAM
Maxtor 80MB ATA-100 5400 RPM (partitioned C:20MB & D:60MB)
Hauppauge WinTV PVR

I’ve been capturing with:

VirtualDub 1.4.5
AVI_IO D 03.21
Using various CODECs including DivX

The new disk drive is a Maxtor 60MB ATA-100 7200 RPM and it’s a slave on the same controller as the 80MB (which is the master).

Both VirtualDub and AVI_IO have a problem with the new drive. When capturing to it, AVI_IO captures a little over 2 minutes and video and says:

“Sorry, no more I/O buffers available, reduce datarate!” and then “A fatal error occurred – press ESC to stop”.

While it is capturing, its using 0-2 buffers then around the 2:20 mark (size 1,419,848 KB), the buffer count goes up to 50 and the above error is displayed. It has nothing to do with reducing the datarate since that same parameter configuration works fine on the other disk.

Now it gets weird…if I delete the capture file(s) that failed and try it again, it fails again. If I rename the capture file and start AVI_IO, it runs OK. Sounds like a bad spot on the hard disk but I’ve done a low-level format with POWERMAX plus FDISK/FORMAT/SCANDISK “Thorough” and it still happens.

Things I’ve already tried and checked:

Both drives set for DMA (System --> Properties)
Changed System Performance from Network to Desktop and back again
Changed System Performance from 64MB Read Ahead to none and back again
Swapped the IDE cable positions and back again
Swapped the drives between Primary and Slave and back again
Used the Maxtor UDMAUPDT program and forced both drives DMA 5
Used the Maxtor WVSET and disabled Write Verify
Used the Maxtor AMSET and disabled acoustic management
The new disk is empty, defragged and scandisk-ed
Putting the drives on separate IDE controllers (both as masters)

The system still captures fine to the original 80MB drive.

What else should I try?

I’m about ready to say it’s a sick disk drive and exchange it but proving that will be a PITA.

[bachelor]

To see if your Maxtor is a dud (which I don't think is the case), go here:

http://www.maxtor.com/products/DiamondMax/techsupport/TechnicalProcedures/20014.htm

[eJim]

I think I got this figured out...

All the PowerMax diagnostics work fine include four passes at the burn-in test.

But there is something there wrong with the disk between 1.32GB and 1.35GB. Whenever the drives writes in that area, the system pauses for several seconds and then continues.

Sounds like a sick disk so I'm going to see if I can get it replaced.

[eJim]

And for those of you that use Maxtor drives, I've learned a few new things:

1) Some Maxtor drives (i.e. DiamondMax 60) come from the factory with write verification turned on for the first ten power-cycles (real power off/on -- not just a reboot). So, watch out for some performance hits during this time.

2) Some Maxtor drives (i.e. DiamondMax 60) come from the factory with an setting that makes the drive quieter but slows seek times down a little.

Both of the above can view and change the drive parameters using diagnotic program from Maxtor at:

http://www.maxtor.com/Maxtorhome.htm

Look for:

Procedure for adjusting write verify modes via the WVSET Program.

Procedure for adjusting operating sound levels via the AMSET Program.

[eJim]

Problem solved: Defective Hard Disk

Exchanged it at BestBuy and they even gave me a $40 credit since the price had dropped.