From owner-freebsd-questions@FreeBSD.ORG Thu Jun 30 09:10:50 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15A5C16A41C; Thu, 30 Jun 2005 09:10:50 +0000 (GMT) (envelope-from alan@cyclopsvision.co.uk) Received: from c2bsmtp02.btconnect.com (c2bsmtp02.btconnect.com [193.113.154.38]) by mx1.FreeBSD.org (Postfix) with SMTP id 773F343D58; Thu, 30 Jun 2005 09:10:49 +0000 (GMT) (envelope-from alan@cyclopsvision.co.uk) Received: from c2bthomr04.btconnect.com (actually host 212.73.73.194.in-addr.arpa) by c2bsmtp02.btconnect.com with SMTP (XT-PP) with ESMTP; Thu, 30 Jun 2005 10:10:44 +0100 Received: from AJDELL9200 (213-78-6-149.uk.onetel.net.uk [213.78.6.149]) by c2bthomr04.btconnect.com (MOS 3.5.8-GR) with ESMTP id BVC74231; Thu, 30 Jun 2005 10:07:39 +0100 (BST) Message-Id: <200506300907.BVC74231@c2bthomr04.btconnect.com> From: "Alan Jay" To: , Date: Thu, 30 Jun 2005 10:07:54 +0100 Organization: Cyclops Vision Limited MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcVwD46mTfKjfektTUW7fcV9PFJNdAAMBlmwAB6+FNAAAERlkAAWuxZwAw8HnPA= X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Cc: Subject: RE: ATA_Identify timeout ERROR - using Tyan S5350 with FreeBSD 5.4 (problems booting - SATA hard disk not recognised) - X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: alan@cyclopsvision.co.uk List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 09:10:50 -0000 Hi, Thought I would report back what I discovered. Following some suggestions on this list I booted into safe mode and installed the operating system successfully. I still couldn't get the machine to boot except in safe mode. After updating the source to the latest stable incarnation via cvsup I did a makeworld and rebuilt the kernel to take advantage of SMP support of our twin processors. At the end of that process the server boots fine. Not sure what the error was but it is still the case if you use the basic downloaded boot CD from the archives and boot the server it complains as below. But with the recompiled kernel it is fine. Does anyone have any insigts? Regards Alan > -----Original Message----- > From: Alan Jay [mailto:alan@cyclopsvision.co.uk] > Sent: Tuesday, June 14, 2005 8:25 PM > To: 'freebsd-questions@freebsd.org'; 'freebsd-stable@freebsd.org' > Subject: ATA_Identify timeout ERROR - using Tyan S5350 with FreeBSD 5.4 > (problems booting - SATA hard disk not recognised) - > > > > Hi, > > I just got a new Tyan S5350 using twin Xeon processors I am told this is now > a > very standard motherboard. > > Unfortunately when I try to boot FreeBSD 5.4 Release I get the following > errors on the IDE/ATA/SATA connection. > > The errors I get during boot up are as follows: > > The hard disk is not recognised you get the error: > > Ata0_master: Failure ATAPI_IDENTITY timeout (x3) Then > Ata1_master: Failure ATA_Identify timeout (x3) > > This is true if I use a standard IDE drive (160Gb) or a SATA drive (250Gb). > The BIOS recognises the drives and is happy with them but the OS has this > problem. > > The board appears to use the Intel 6300SEB chip set using for the > IDE/ATA/SATA > > is it supported? Or is there a problem with my motherboard? > > The board we have is: > http://www.tyan.com/products/html/tigeri7320r_spec.html > > If anyone is using this motherboard successfully please let me know so I can > organise a replacement. > > Any other help gratefully received. > > Alan Jay > > PS The rest of the machine specs are - twin Xeon processor; 4 Gb RAM; Intel > Gigabit Network card in the PCI slot. 250Gb SATA drive. > > PPS Having looked around the lists there appear to be people who say this is > related to the issues described 5.2.1 release errata > (http://www.freebsd.org/releases/5.2.1R/errata.html) > > PPPS loading in safe mode does work but it isn't a viable way to run a > server > anyone got any ideas why this occurs and how to work around it the ideas in > the errata for 5.2.1 don't seem to work assuming that I have the syntax > correct in the /boot/loader.comf