It seems James Satterfield wrote: Hmm there is a workaround in -current for using 48bit access to the old promises, however it should only engage when you access areas beyond 137G on the drives. However using 48bit modes on older controllers are not really a good idea as they tend to do wierd things...
> Okay... Perhaps I'm just a dumbass with a failing drive? For the longest time, I've > thought the hardware needed to support the large drives. From the reading I've just > done, that doesn't seem to be the case. I certainly hope this brand new drive isn't > failing tho. I really hate doing hardware warranty returns. > > James. > > On Fri, 7 Mar 2003 14:20:24 -0800 > James Satterfield <[EMAIL PROTECTED]> wrote: > > > I've got a 160GB ide drive in my FBSD box. It's got an old ide controller that > > doesn't support big ide drives. Yet freebsd recognizes the drives full capacity, > > allows me to partition it, and newfs it. After writing about 47GB of data to the > > drive, I start getting these. > > ad5: WRITE command timeout tag=0 serv=0 - resetting > > ata2: resetting devices .. > > > > > > atapci1: <Promise UDMA66 controller> port > > 0xef00-0xef3f,0xefe0-0xefe3,0xefa8-0xefaf,0xefe4-0xefe7,0xeff0-0xeff7 mem > > 0xffae0000-0xffafffff irq 10 at device 20.0 on pci0 > > ad5: 156334MB <Maxtor 4G160J8> [317632/16/63] at ata2-slave UDMA66 > > > > > > James. > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
