From owner-freebsd-current Fri Oct 16 17:23:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23638 for freebsd-current-outgoing; Fri, 16 Oct 1998 17:23:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23556 for ; Fri, 16 Oct 1998 17:22:33 -0700 (PDT) (envelope-from mike@seidata.com) From: mike@seidata.com Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id UAA01772 for ; Fri, 16 Oct 1998 20:22:05 -0400 (EDT) Date: Fri, 16 Oct 1998 20:22:05 -0400 (EDT) To: freebsd-current@FreeBSD.ORG Subject: 3.0-RELEASE 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 Hello, I'm attempting to give 3.0-RELEASE a try on my Toshiba 4015CDT. 3.0 recognizes everything (flawlessley, I might add) at bootup. Everything goes smoothly until I attempt to start the actual transfer of information from the FTP site and sysinstall starts doing a newfs to prepare my drive... Sysinstall then gets rather upset and says, "Unable to make new root filesystem on /dev/rwd0s2a!" and I have to abort. ALT-F2 yields: newfs: ioctl (WDINFO): Cross-device link newfs: /dev/rwd0s2a: can't rewrite disk label Is my partition table just fubar? 2.2.7-RELEASE chugs happily along. I got the same thing with the last 3.0-BETA release on a PPro SMP box I was playing with the other day. On the SMP box, it was calling my SCSI drives daX instead of sdX - is this the new terminology? Just curious. :) I fell back to an older SNAP (5/20 I believe) I'd been running on a similarly-configured box with no problems. Thanks in advance for any help... -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message