From owner-freebsd-questions Mon Feb 18 6: 9:38 2002 Delivered-To: freebsd-questions@freebsd.org Received: from florida-wireless.com (mailserver.florida-wireless.com [208.62.145.34]) by hub.freebsd.org (Postfix) with ESMTP id 52C0B37B404 for ; Mon, 18 Feb 2002 06:09:28 -0800 (PST) Received: from mdd [208.62.145.61] by florida-wireless.com (SMTPD32-7.05) id ABBD12DD014A; Mon, 18 Feb 2002 09:12:13 -0500 Message-ID: <008501c1b885$dca66ca0$1aa8a8c0@mdd> From: "freebsd" To: References: Subject: ata/100 controller Date: Mon, 18 Feb 2002 09:09:21 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have three hard drives in my freebsd machine. a maxtor,wd and seagate. They show as being dma 2 , ultra dma 2 and ultra dma 4. This is from when booting up ad0: 1223MB [2485/16/63] at ata0-master WDMA2 ad1: 4104MB [8896/15/63] at ata0-slave WDMA2 ata1-master: DMA limited to UDMA33, non-ATA66 compliant cable ad2: 12982MB [26377/16/63] at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a I get alot of timeout errors: ad0: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad0: READ command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done ad0: WRITE command timeout tag=0 serv=0 - resetting ata0: resetting devices .. done and the part about non ata66 complaint cable. I assumed that the timeouts were from the FreeBsd detecting these higher/faster hd and they were connected to a regular onboard hd controller. so I went a bought a maxtor utlra pci ata/100 controller. I connected all 3 drives. removed them from the bios standard setup and rebooted. All 3 drives are found. System starts to boot then I run into a problem were it ask for me to manual enter the root bootfile system. I have no clue or idea what it is asking for ? I did a while back do a tune -nfs on all the drives thinking that might remove the problem but it did nothing that I know of. I really can not afford to lose the data on the drives and I would reallly like to see if the controller will take care of these timeout problems so I am not sure what I have to do to get the system to boot with the ultra 100 controller. What would I put in the line for root filesystem ? doing a ? gives me a list of options but no idea. thanks mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message