From owner-freebsd-stable Wed May 12 16:46:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id F241714EDD; Wed, 12 May 1999 16:46:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id QAA02146; Wed, 12 May 1999 16:44:47 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905122344.QAA02146@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" Cc: stable@FreeBSD.ORG, pkh@FreeBSD.ORG Subject: Re: Fubar w/3.2-BETA In-reply-to: Your message of "Wed, 12 May 1999 16:30:48 PDT." <66746.926551848@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 1999 16:44:47 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is really weird; I can't reproduce this! > > I wonder if it's because my test box uses SCSI. Damn, time to dust > off the IDE system I think. :) > > - Jordan > > > You're one up on me. My errors were fatal, as it wouldn't allow the creation > > of the devices in /dev, thereby not allowing newfs to run, or even to mount > > them if I didn't newfs them. The error messages here really worry me: DEBUG: MakeDev: Unknown major/minor for devtype 0s1b Something has corrrupted (or never set) the device prefix in the path entries in the disk chunk that's being fed to MakeDevDisk() here. I'm at a bit of a loss as to how this can happen though; it's meant to be maintained by libdisk... Brian, can you offer any more details on your install? Disk type? Prior disk layout, etc? I'd like to try to reproduce it if I can... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message