From owner-freebsd-questions@FreeBSD.ORG Sat Nov 8 07:00:31 2003 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 61D9416A4CE for ; Sat, 8 Nov 2003 07:00:31 -0800 (PST) Received: from smtp.1-us.com (wsip-24-120-195-10.lv.lv.cox.net [24.120.195.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABA0143FCB for ; Sat, 8 Nov 2003 07:00:30 -0800 (PST) (envelope-from zeke@WW-TEL.NET) Received: from DESKOFZEKE (wsip-24-120-195-14.lv.lv.cox.net [24.120.195.14]) by smtp.1-us.com (8.12.6/8.12.6) with SMTP id hA8F6i69024982 for ; Sat, 8 Nov 2003 07:06:44 -0800 (PST) (envelope-from zeke@WW-TEL.NET) Message-ID: <000e01c3a609$0d0c9230$0ec37818@DESKOFZEKE> From: "A1-Vegas.com \"Zeke\"" To: Date: Sat, 8 Nov 2003 07:00:29 -0800 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 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: work-around for 5.2 on SOYO raid. 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: Sat, 08 Nov 2003 15:00:31 -0000 please forward to the appropriate people. problem: sysinstall in CDimage cannot write to HPT raid work around: installation procedure freeBSD 5.2 soyo P4S Dragon ultra. 1. plug one of the hard drives into IDE1 2. install freeBSD onto drive. 3. edit /etc/fstab, change drives to ar0s1a ar0s1b ...etc. 4. power down and re-plug drive into IDE3, plug empty drive into IDE4. 5. set cmos to boot on SCSI 6. run ^H setting tool, create mirror, and duplicate drive 1 to empty drive. 7. freeBSD will now boot from the array. these steps should not be necessary, but the installer was unable to write to the hpt raid, even thopugh it was successfully probed. after moving the hard drive to the raid array the boot loader would run from the hard drive, and the raid was successfully probed, but the boot loader was not able to translate the fstab entries to the new environment. may i humbly suggest adding this capability, possibly with an operator confirmation. the purpose of mirrioring is to allow fast recovery from system failures, the ability of the loader to discover it's new environment serves that end. thanks ...zeke P.S. the soyo motherboard makes a great hard drive cloner, too. ..Z