From owner-freebsd-current Thu Oct 15 23:36:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19740 for freebsd-current-outgoing; Thu, 15 Oct 1998 23:36:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles312.castles.com [208.214.167.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19734 for ; Thu, 15 Oct 1998 23:36:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA01139; Thu, 15 Oct 1998 23:40:44 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810160640.XAA01139@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Mike Grommet" cc: freebsd-current@FreeBSD.ORG Subject: Re: Installation bugs 3.0BETA 10-09??? We need a can of RAID :) In-reply-to: Your message of "Tue, 13 Oct 1998 17:15:51 CDT." <00ca01bdf6f7$0a09a080$0cf896d0@work2.insolwwb.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Oct 1998 23:40:43 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please note that at the moment FTL doesn't have a DPT card of any description, so we can't do any inhouse debugging of release problems with them. We haven't seen any of the problems you're seeing on any other disk controller, which makes me suspect that it's related to something unique that the DPT is doing. > Hi. running into some interesting problems trying to install > 3.0 Beta, 10-09 release. > > A bit about the hardware in this machine... > Pent II 350, Intel BX Chipset > DPT Raid Controller (DPT PM3334UW) > 128 Megs of ram, etc etc. > > I go in and dedicate a partition to freebsd... > I then break the partition up into these chunks: > > 256 Megs / > 512 Megs SWAP > 1000 Megs /var > 3200 Megs /usr/local > 2400 Megs /usr > > basically all goes as normal until it tries to newfs the partitions... > > when it tries to newfs the first slice ( / filesystem) > > Debug reports "DEBUG: unknown major/minor for devtype -" The message is actually "MakeDev: Unknown major/minor for devtype ..." and comes from libdisk. It's surprising that it's being called, but it *shouldn't* actually be fatal. Do all the filesystems get created correctly at this stage? > it dies with a message on the debug console where it gives "Cross device > link" error in newfs and then a rewrite label error. This sounds a little odd. It would help to know what the actual text from newfs was. > I just wanted to make sure you guys knew of this situation before the > release date. Thanks for the notice; unfortunately it's difficult to know where to point the finger. A similar partitioning scheme on a single IDE disk seems to work just fine, so the suspicion about it maybe being DPT-related has to take some weight. I can't see how, though. -- \\ 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-current" in the body of the message