Re: Problems with PIO, Maxtor 160Gb and A7A266 with Ali chipset

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



UDMA mode 5 for HD's is pretty common as is UDMA mode 2 for optical devices..
In the bios the drives should be set to auto configure and should have worked
on the same IDE channel showing UDMA mode 5 for both drives. If you manually
set them to UDMA mode 6, there en lies the problem..
j;-j

"DougCuk" wrote:

>
> I have also been battling a problem with XP SP2 showing sporadic IDE
> Hardisk errors in the system log and also falling back from UDMA to PIO
> mode. The System Event Log shows the following error:
>
> The driver detected a controller error on \Device\Harddisk0\DR0
>
> Also occasionally the following errors:
> An error was detected on device \Device\Harddisk0\DR0 during a paging
> operation
> \Device\Ide\IdePort0, did not respond within the timeout period
> Various "Delayed Write Failed" errors
>
> After a long process of testing I think I have found the root of the
> problem.
>
> I was attempting to run two ATA UDMA6 drives on the same IDE cable -
> Master drive: Samsung 40Gb SP04011N
> Slave drive: Maxtor 80Gb Diamond Max 9 (also tested a new Maxtor
> 250Gb)
>
> With both drives set to UDMA6 the Samsung reports sporadic UDMA CRC
> errors recorded by the drives SMART system and XP records sporadic
> bursts of Disk conroller errors in the System Event Log. The HD's SMART
> data can be viewed in Windows using various utilities - I used SpeedFan.
> After a while XP implements a protective UDMA fallback for the affected
> drive and ends up at PIO mode.
>
> To eliminate possible driver problems I tested the drive and cable
> setup using using the SpinRite HD testing program from Gibson Research
> (www.grc.com) - this runs from pure DOS but can test NTFS formatted
> disks - so if the problem still appears its not caused by Windows
> drivers or registry settings. SpinRite reported sporadic UDMA CRC
> errors (cabling errors) from the Samsung HD with the BIOS set to UDMA6.
>
>
> I tested an identical Samsung HD, and tried many different IDE cables
> without success. Finally I tested the Samsung HD on its own without the
> Maxtor on the cable - the fault vanished. I then restricted the Samsung
> to UDMA5 in the BIOS and retested the dual drive configuration - the
> fault had vanished. The Samsung runs fault free at UDMA6 as long as it
> is alone on the cable - but tests with two different UDMA6 Maxtor
> drives as Slave devices always caused the Samsung to become unstable at
> UDMA6 - reducing the BIOS setting for the Samsung to UDMA5 restores
> stability.
>
> It appears the two drives have some kind of conflict that causes a
> corruption of the UDMA data when attempting to run at the full UDMA6
> speeds. The errors are at a very low density and do not generally cause
> any data corruption - they just cause the drives and Windows to
> sporadically record controller errors. Unfortunately the standard
> registry settings in XP SP2 trigger a UDMA speed fallback after 6
> cumulative errors - often resulting in a rapid drop back to PIO mode
> from a single burst of controller errors.
>
> Having eliminated all other causes and being able to switch the fault
> on and off at will - I am forced to accept that the Samsung will not
> run at UDMA6 when paired with a Maxtor UDMA6 drive. The final test
> would be to try testing it paired with another Samsung drive and see if
> it works in that configuration.
>
> Note: As a safety measure XP blocks all attempts to reset UDMA for the
> affected drive to protect data integrity. And until you have eliminated
> the cause of the errors it will after a short period just revert back to
> PIO mode each time you reset the required registry settings.
>
> Once the controller errors have been eliminated you have to deleted the
> affected IDE controller in Device Manager and reboot to reinstall a
> clean copy of the registry settings. Or you can hack the registry as
> stated in the previous forum post to reset back to UDMA mode but its
> more hassle.
>
> Hope this lengthy report is of some assistance to others with a similar
> type of problem.
>
>
> --
> DougCuk
> ------------------------------------------------------------------------
> DougCuk's Profile: http://forums.techarena.in/member.php?userid=9829
> View this thread: http://forums.techarena.in/showthread.php?t=188426
> Visit - http://www.techarena.in | http://forums.techarena.in | http://forums.techarena.in/archive/index.php
>
>
.



Relevant Pages

  • Re: Problems with PIO, Maxtor 160Gb and A7A266 with Ali chipset
    ... Hardisk errors in the system log and also falling back from UDMA to PIO ... With both drives set to UDMA6 the Samsung reports sporadic UDMA CRC ...
    (microsoft.public.windowsxp.hardware)
  • Re: New Hd Install - No Udma Support, Dma 2 Only
    ... as a second HD as a master on the secondary ide channel using the cable ... My boot drive, a 20 gb maxtor fireball, functions fine in UDMA 5. ... I don't want to do a clean install of XP because of the time involved ... Does your motherboard really support large hard drives? ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: New Hd Install - No Udma Support, Dma 2 Only
    ... mobo only supports up to 137 GB, but windows recognises more - Possibly ... mode, only said udma). ... I don't want to do a clean install of XP because of the time involved ... Does your motherboard really support large hard drives? ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: UDMA goofed up (I think)
    ... At the get-go, if implementing UDMA, 3 things must be in place for max I/O ... cable of proper length must be in place, next, the bios must be UDMA capable ... restricts usage to four of six possible drives, ... For repeated DMA errors. ...
    (microsoft.public.windowsxp.hardware)
  • Re: New Hd Install - No Udma Support, Dma 2 Only
    ... I've reset the config data in BIOS several times, ... UDMA numbers when attached to the same channel. ... The hard drives are the only device on the channel? ... with updates and making configuration changes. ...
    (alt.comp.hardware.pc-homebuilt)