From owner-freebsd-stable Sat Nov 11 8:40:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-206-90-77.dsl.snfc21.pacbell.net [63.206.90.77]) by hub.freebsd.org (Postfix) with ESMTP id E73A937B479 for ; Sat, 11 Nov 2000 08:40:51 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eABGkL914085; Sat, 11 Nov 2000 08:46:21 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011111646.eABGkL914085@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Hanspeter Roth Bsag Cc: freebsd-stable@FreeBSD.ORG Subject: Re: setrootbyname failed in 4.2-Beta In-reply-to: Your message of "Sat, 11 Nov 2000 14:58:34 +0100." <20001111145834.A2025@bs11.bsag.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Nov 2000 08:46:21 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > > I have upgraded from 4.1-Release to 4.2-Beta. > I've built a GENERIC kernel and run MAKEDEV all. > But MAKEDEV didn't recreate the devices which are listed in fstab > such as da0s1a. This is irrelevant to your problem. > The new kernel failes to mount the root filesystem. > The messages are: > > Mounting root from ufs:/dev/da0s1a > no such device "da" > setrootbyname failed > > Then I get to mountroot>. The ?-command lists several devices but no 'da'. > > How can I make the new kernel run? > Is there some documentation about new devices in 4.2-Beta? When you built your new kernel, you left out something. Your SCSI disks are probably not being probed (check the probe messages). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message