Date: Thu, 20 Jun 2002 13:14:10 -0600 From: Orrie <Orrie.Gartner@Colorado.EDU> To: "Jud" <jud@myrealbox.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: ATA RAID question Message-ID: <200206201914.g5KJED702765@refuge.Colorado.EDU>
next in thread | raw e-mail | index | archive | help
Jud, Thanks for your help. The problem turns out to be an interaction between the Promise Fasttrack 100 IDE-RAID and our Maxtor 160GB drives and not a problem with support of this controller. Any other size drive that is smaller than the Maxtor 160GB seems to work fine (we tried drives from 10 Gig to 80 Gig). The odd thing is, the 160GB drives work fine on the regular IDE controller, it just blows up when they are attached to the Promise Fasttrack 100 IDE-RAID. Here are the drives: ad0: 156334MB <Maxtor 4G160J8> [317632/16/63] at ata0-master BIOSDMA ad1: 156334MB <Maxtor 4G160J8> [317632/16/63] at ata0-slave BIOSDMA ad2: 156334MB <Maxtor 4G160J8> [317632/16/63] at ata1-master BIOSDMA ad3: 156334MB <Maxtor 4G160J8> [317632/16/63] at ata1-slave BIOSDMA ad6: 156334MB <Maxtor 4G160J8> [317632/16/63] at ata3-master UDMA100 Too bad we got these cheap and can't send them back. Anyone else out there attaching 160GB drives to a Promise Fasttrack RAID? Orrie -------- > > > Hi all, > > We have a Gigabyte GA-7DPXDW motherboard with the AMD 760MPX chipset > and the onboard Promise Fasttrack 100 IDE-RAID with Maxtor 160GB > drives. When booting off the 4.6 iso image, the install will panic > during the boot process if the drives are left connected to the onboard > promise ATA 100 IDE-RAID. If we disconnect all drives from the onboard > promise ATA 100 IDE RAID and only hook up a drive to the master IDE > controller on the motherboard, we can boot up and install 4.6. Then, > when we reattach the 160 GB drives to the onboard promise ATA 100 IDE > RAID controller the system will crash during bootup after displaying > several messages similar to the following (there is one for each > drive): > > ad0 maxtor 4G160J8 Read command Timeout tag=0 serv=0 - resetting trying > fallback to PIO mode > ata3: resetting devices > > then a kernel panic will occur (on 4.5-RELEASE-p6 it would boot up but > these drives would be stuck in PIO mode and therefore be terribly > slow). > > As indicated in the 4.6 release notes, we tried setting hw.ata.tags="1" > in /boot/loader.conf to no avail. > > Unfortunately this setup is working fine under Linux meaning my boss > wants me to switch. I'm desperate to try anything to get this to work > with FreeBSD since I can't stand linux. > > From some searches, it seems the onboard Promise ATA 100 IDE-RAID may > not be supported under FreeBSD? Can anyone confirm/deny this? I don't > need the RAID functionality to work but I do need all the disks to > function properly as independent disks (tried turning off the RAID in > the BIOS but it didn't help). Any thoughts? > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > Do a Google Groups search on -questions for PDC20265 (the Promise ATA > 100 IDE-RAID onboard chip) and PDC20276 (the ATA 133 equivalent), > and/or A7V266-E and A7V333, the ASUS mobos with these onboard controllers. > > 4.6-RELEASE supports both controllers (-STABLE has supported them for > a while). > > I don't think tagged queueing has anything to do with this - that's a > feature of IBM HDs, so you may as well leave it out of boot/loader.conf. > > Sorry I can't give you a complete solution. I can just tell you it's > not lack of support for your controller. > > Jud > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206201914.g5KJED702765>