From owner-freebsd-stable@FreeBSD.ORG Tue Sep 28 20:31:22 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E8F516A4CE for ; Tue, 28 Sep 2004 20:31:22 +0000 (GMT) Received: from out-mx1.crosswinds.net (out-mx1.crosswinds.net [216.18.117.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id C946743D39 for ; Tue, 28 Sep 2004 20:31:21 +0000 (GMT) (envelope-from tony@crosswinds.net) Received: from admin.crosswinds.net (out-mx1.crosswinds.net [216.18.117.38]) by out-mx1.crosswinds.net (Postfix) with ESMTP id E00482B038 for ; Tue, 28 Sep 2004 16:31:20 -0400 (EDT) Received: by admin.crosswinds.net (Postfix, from userid 1001) id B22D63F0B; Tue, 28 Sep 2004 16:31:20 -0400 (EDT) Date: Tue, 28 Sep 2004 16:31:20 -0400 From: Tony Holmes To: freebsd-stable@freebsd.org Message-ID: <20040928203120.GA42296@crosswinds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Fdisk/Disklabel ARG X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Sep 2004 20:31:22 -0000 I'm using 4.10 on various sytems, and getting the same problems on SCSI, ATA (direct and via a Promise TX2) with ufs or vinum and it's driving me nuts! After installing a base OS disk (no problems there), I add other disks and partitions. Now, to be lazy, I usually cheat by using /stand/sysinstall, first fdisk, then label, no boot manager. Usually, it works 100% and I keep my lazy factor high. As of 4.10, it started to complain about invalid argument when I would create a parition, and attempt to newfs/mount it. So, I got "un"-lazy and attempted to do it manually. I do (using ar0 as the example device): fdisk -I ar0 disklabel -r -w ar0 auto disklabel -e ar0 I muck around in disklabel and make my partitions, expending *far* too much energy as compared to /stand/sysinstall. Save and exit. Then I do the nice newfs. newfs -N -b 16384 -f 2048 -i 32768 -c 102 /dev/ar0s1e It newfs's wonderfully, showing me all the superblock locations and such as I yawn at this unnecessary work. Then I attempt to mount the partition: mount /dev/ar0s1e /mnt And I get: sh1# mount /usr/home mount: /dev/ar0s1e on /usr/home: incorrect super block /var/log/messages shows: dscheck(#ar/0x20002): fixlabel: invalid magic fixlabel: invalid magic WHAT GIVES? I have attempted obliterating the info on disk with a dd to the c partition and the raw device itself. As mentioned, I have this problem with all sorts of devices, so a number of scenarios present themselves: 1. FreeBSD 4.10 disklabel/fdisk has some form of regression 2. I am the one suffering from the regression and being too lazy for too long forget what to do As another note, I attempted the same thing under FreeBSD 4.8 and had no problem!!! Any help would be appreciated. I've tried everything except taking the disks to dinner to get them to take a fileystem! -- Tony Holmes Ph: (416) 993-1219 Founder and Senior Systems Architect Crosswinds Internet Communications Inc.