Re: Promise ATA100 controller and 160G disks

2004-05-26 Thread Frank Mueller
I have FBSD -STABLE running on a Promise Fasttrak 100 TX2 (latest BIOS) with 2 160GB HDDs as RAID1 and it is running fine. Greetz, Frank Hi, does anyone know if the Promise ATA100 controller PCI card supports 160 G disks on -STABLE? Thanks, --Stijn -- Nostalgia ain't what it used to

Re: Promise ATA100 controller and 160G disks

2004-05-26 Thread Stijn Hoop
On Wed, May 26, 2004 at 11:15:02AM +0200, Frank Mueller wrote: I have FBSD -STABLE running on a Promise Fasttrak 100 TX2 (latest BIOS) with 2 160GB HDDs as RAID1 and it is running fine. OK, but I have the older non-raid just ATA100 controller version, which is why I suspect it might not work.

Re: Promise ATA100 controller and 160G disks

2004-05-26 Thread heikki soerum
It shouldn't be an problem as long as you upgrade the BIOS in the atacontroller. I'm using an Promise Fasttrak 100 (without TX2) on two 200Gb drives. With the newest bios the controller can use drives over 120GB. Heikki Soerum, Norway. On Wed, 26 May 2004 11:53:24 +0200 Stijn Hoop [EMAIL

Re: Promise ATA100 controller and 160G disks

2004-05-26 Thread Bill Moran
Stijn Hoop wrote: Hi, does anyone know if the Promise ATA100 controller PCI card supports 160 G disks on -STABLE? I'm not 100% sure that the Promise controller is the problem here: http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/046070.html Earlier this week, I thought I'd solved the

Re: Promise ATA100 controller and 160G disks

2004-05-26 Thread Stijn Hoop
On Wed, May 26, 2004 at 09:28:09AM -0400, Bill Moran wrote: Stijn Hoop wrote: does anyone know if the Promise ATA100 controller PCI card supports 160 G disks on -STABLE? I'm not 100% sure that the Promise controller is the problem here:

Re: Promise ATA100 controller and 160G disks

2004-05-26 Thread Bill Moran
Stijn Hoop wrote: On Wed, May 26, 2004 at 09:28:09AM -0400, Bill Moran wrote: Stijn Hoop wrote: does anyone know if the Promise ATA100 controller PCI card supports 160 G disks on -STABLE? I'm not 100% sure that the Promise controller is the problem here: