From owner-freebsd-questions@FreeBSD.ORG Wed Jun 2 06:54:22 2004 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 5A80D16A4CE for ; Wed, 2 Jun 2004 06:54:22 -0700 (PDT) Received: from destiny.chrononomicon.com (mail.chrononomicon.com [65.193.73.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5A3343D41 for ; Wed, 2 Jun 2004 06:54:21 -0700 (PDT) (envelope-from bsilver@chrononomicon.com) Received: from [IPv6:::1] (destiny.chrononomicon.com [192.168.1.42]) by destiny.chrononomicon.com (Postfix) with ESMTP id D0FBD1FDFF for ; Wed, 2 Jun 2004 09:53:54 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v618) In-Reply-To: <54C692FE-B48F-11D8-818D-000A956D2452@chrononomicon.com> References: <54C692FE-B48F-11D8-818D-000A956D2452@chrononomicon.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4A30B4AE-B49C-11D8-818D-000A956D2452@chrononomicon.com> Content-Transfer-Encoding: 7bit From: Bart Silverstrim Date: Wed, 2 Jun 2004 09:53:56 -0400 To: freebsd-questions Questions X-Mailer: Apple Mail (2.618) Subject: Re: 5.2.1 boot-install X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 13:54:22 -0000 On Jun 2, 2004, at 8:21 AM, Bart Silverstrim wrote: > I have used this technique with 4.9, and it worked. On a machine i > wanted to install 5.2.1 on, it won't (this is a machine the 4.9 > install worked on fine). The boot process starts, and it locks up > ending with this in the bootup sequence: > GEOM: create disk ad0 dp=0xc2006560 > ad0: 19092MB [38792/16/63] at ata0-masster UDMA100 > ata1-master: FAILURE - ATA_IDENTIFY status=7f DRQ, CORRECTABLE, INDEX_ERROR> error=7f NID_NOT_FOUND, MEDIA_CHANGE_REQUEST, ABORTED,NO_MEDIA,ILLEGAL_LENGTH> > LBA=0 > Answering myself for the archives.. This *should* have worked and would have worked if not for a bug I had to workaround in 4.9 on that CDROM. The CDROM is the only device on the bus, and if it were set to master, I kept getting ata1-master resetting ad infinitum; the jumper, once removed from the back of the CDROM drive, allowed 4.9 to work like a charm. I remembered this after downloading and burning the bootonly ISO and having that fail with the same error... Once I put the jumper back in to set the device to "master", the 5.2.1 CD booted straight to sysinstall. Something for people to keep in mind... :-) -Bart