From owner-freebsd-questions@FreeBSD.ORG Tue May 17 16:04:34 2005 Return-Path: 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 6829E16A4CE for ; Tue, 17 May 2005 16:04:34 +0000 (GMT) Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id B998F43DB4 for ; Tue, 17 May 2005 16:04:33 +0000 (GMT) (envelope-from fbsd_user@a1poweruser.com) Received: from barbish ([69.172.31.81]) by mta11.adelphia.net (InterMail vM.6.01.04.01 201-2131-118-101-20041129) with SMTP id <20050517160426.VWFL13270.mta11.adelphia.net@barbish> for ; Tue, 17 May 2005 12:04:26 -0400 From: "fbsd_user" To: "freebsd-questions@FreeBSD. ORG" Date: Tue, 17 May 2005 12:04:21 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Subject: RE: 5.4 install disc1 will not find hard drive X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: fbsd_user@a1poweruser.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2005 16:04:34 -0000 This is not an cable problem. I can use the 5.3 cdrom and the install goes with out a problem. But when I use the 5.4 cdrom on the same PC I get error message no hard drive found. Then I use the 5.3 cdrom again on the same PC and the install goes with out a problem. I have re-downloaded the 5.4 disc1.iso file, run md5 to verify it good then burned it to cdrom for the second time and still it will not work. If it was HD cable problem I would get same error on both 5.3 and 5.4. Even tried building the bootable floppies from yesterdays 20050516 snapshot for 5.4 and it also gave "no disk found" error. Is this a bug with 5.4 and should I submit a bug report. I am open to any other ideas of how to debug this or work around this.