From owner-freebsd-current Sun Nov 21 13: 7:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id AE7DE151AD for ; Sun, 21 Nov 1999 13:07:10 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id NAA07317; Sun, 21 Nov 1999 13:33:51 -0800 (PST) Date: Sun, 21 Nov 1999 13:33:51 -0800 (PST) From: Alfred Perlstein To: Mike Smith Cc: current@freebsd.org Subject: Re: installing onto ami mega raid. In-Reply-To: <199911212052.MAA03767@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 21 Nov 1999, Mike Smith wrote: > > > > I spent about 2 to 3 hours last night futzing with sysinstall and > > getting the amr.ko file onto the 4.0 install disk (using the > > 4.0-19991114 SNAP) I tried adding the amr disks to devices.c in > > sysinstall but had no luck. > > Bah. I knew I forgot something there. That should just about have > done it. > > > After booting the install disks and loading the amr kld (the probe > > messages showed that it was detected) I escaped to the prompt > > (alt+f4). I saw that the amrd0 /dev/ entries had been created, > > but attempts to access them gave "unit 0 not available" (as far as > > i remeber) > > That's not an error message that the driver can produce. It'd be > helpful to know what it actually said, and whether you have actually > created an array yet. > > > What exactly needs to be done to get 4.0 installed with a amr disk > > as root? > > Sysinstall needs the patch you supplied; apart from that I'm not aware > of anything else. I haven't, obviously, had time to work on this yet. > A better diagnostic from you above would save me at least one release > build... Unfortunatly all the amr systems I have are now in production, I can not test a new install on them. The way I did manage to do the install was nfs mounting another machine's /, /usr, and /var then using dump/restore to init the system over a hand done disklabel on the amr (disklabel, not sysinstall). I'm sorry. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message