This message is from the T13 list server.
That is why SAS is around for a price markup on a drive that works. The idea that a PATA-SATA painless transistion was dreamed in one of the smoke filled rooms you missed. You want to have more fun ? Pump data down one channel and do a non-data command down the other. Setfeatures is enough to smash everything. Wait I am still stuck in PATA, but recall PATA-SATA was to be seamless. Cheers, Andre Hedrick LAD Storage Consulting Group On Fri, 26 Sep 2003, Hale Landis wrote: > This message is from the T13 list server. > > > Lets see, the SATA problem list goes something like this: > > * cables can be a problem. > * connectors can be a problem. > * clock signals can cause errors. > * any kind of noise causes errors. > * these problems cause the device to reset in the > middle of commands. > * there is little or no way to detect these resets. > * command parameter data appears to get corrupted > causing ABRT errors or worse data compare errors. > > This sure sounds like another famous interface that was going to > take over the world: 1394. And these problems will not get worse > at 3Ghz? > > But I have a suggestion for you SATA testers out there - put two > SATA drives on the same system and power supply and then do lots > of Read/Write commands to both drives at the *same* time. That > means one drive on the controller's primay side and one drive on > the same controller's secondary side. See if that doesn't cause > errors on both drives. > > Hale > > > > *** Hale Landis *** www.ata-atapi.com *** > > >
