From owner-freebsd-stable Thu Dec 20 2:53:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from relay3-gui.server.ntli.net (relay3-gui.server.ntli.net [194.168.4.200]) by hub.freebsd.org (Postfix) with ESMTP id A103A37B405 for ; Thu, 20 Dec 2001 02:53:14 -0800 (PST) Received: from pc3-card4-0-cust122.cdf.cable.ntl.com ([62.254.251.122] helo=rhadamanth.private.submonkey.net ident=exim) by relay3-gui.server.ntli.net with esmtp (Exim 3.03 #2) id 16H0ox-0007DB-00; Thu, 20 Dec 2001 10:53:03 +0000 Received: from setantae by rhadamanth.private.submonkey.net with local (Exim 3.33 #1) id 16H0ld-0000MQ-00; Thu, 20 Dec 2001 10:49:37 +0000 Date: Thu, 20 Dec 2001 10:49:37 +0000 From: Ceri To: Kaming Cc: stable@freebsd.org Subject: Re: Promise ultra100 Message-ID: <20011220104937.GA1007@rhadamanth> Mail-Followup-To: Ceri , Kaming , stable@freebsd.org References: <1008828582.4164.13.camel@kaming.portal2.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1008828582.4164.13.camel@kaming.portal2.com> User-Agent: Mutt/1.3.24i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Dec 20, 2001 at 02:09:42PM +0800, Kaming wrote: > Hi all, > > I am a newbie of freebsd and hope someone can help... I have installed > the 4.4 freebsd on a PC with promise ultra100 PCI card. During the > installation. FreeBSD default kernel can find out the the harddisk > connected to the promise ultra100 PCI card. But... after the > installation and reboot it. it show the following message in the screen: > > Invalid partition > >> FreeBSD/i386 BOOT > Default: 0:ad(0,a)/kernel > boot: Oh dear, you're in for some fun. What's probably happened here is that the disk that used to be on ad0 is now ad4 (I imagine this is why disabling your onboard controller worked, Scott). This is going to let you in for a whole world of pain, including not being to remount partitions because the devices don't exist, and not being able to create the devices because you can't remount the partitions read-write. See http://marc.theaimsgroup.com/?t=100708823700004&r=1&w=2 for more details. It's certainly fixable, but you have mentioned that you are a newbie, so I think you're just about to start heading up a rather learning curve. To make life easier all round, I'd suggest making a backup of all of your important data, then try putting the drives back as they were, booting into FreeBSD and running this command as root : cd /dev && sh MAKEDEV ad4* ad4s1* ad4s2* ad4s3* ad4s4* Don't worry too much if you get some errors, as you may not have all of the relevant slices and partitions. Then edit /etc/fstab and change all occurences of /dev/ad0 to /dev/ad4. Then put the drive back onto the promise controller and you should be ok. If you're making backups, it might just be easier to reinstall FreeBSD. As for your Linux question, I don't have a clue. Ceri -- keep a mild groove on To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message