From owner-freebsd-stable@FreeBSD.ORG Tue Mar 1 17:00:50 2005 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 67E7816A4CE for ; Tue, 1 Mar 2005 17:00:50 +0000 (GMT) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0919A43D2F for ; Tue, 1 Mar 2005 17:00:50 +0000 (GMT) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id j21H0nCB008879 for ; Tue, 1 Mar 2005 09:00:49 -0800 (PST) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id j21H0nq3008878 for stable@freebsd.org; Tue, 1 Mar 2005 09:00:49 -0800 (PST) (envelope-from david) Date: Tue, 1 Mar 2005 09:00:49 -0800 From: David Wolfskill To: stable@freebsd.org Message-ID: <20050301170049.GB5862@bunrab.catwhisker.org> Mail-Followup-To: David Wolfskill , stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: "ioctl DIOCSMBR: Operation not permitted" from "boot0cfg -s 1" 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, 01 Mar 2005 17:00:50 -0000 On a couple of machines here (my laptop and an SMP "build machine"), I track each of RELENG_4 and RELENG_5 on a daily basis. I do this by using separate bootable slices. As a consequence of doing things this way, I have become accustomed to using boot0cfg to switch the default boot slice when I need to do this (which is usually twice daily per machine). I know of no problems doing this with RELENG_4 in the past, nor with RELENG_5 (since that tag was laid down, of course -- there had been an issue with 5.x when it was -CURRENT back in the earlier days of GEOM, but that was un-broken withiin a few days -- up through Sunday (27 Feb). This morning, I got through building & booting 5.4-PRERELEASE OK, so I tried switching back to slice 1 (where I have RELENG_4 living). This is what I saw: freebeast(5.4-P)[1] sudo boot0cfg -s 1 -v ad0 Password: boot0cfg: /dev/ad0: ioctl DIOCSMBR: Operation not permitted freebeast(5.4-P)[2] I also tried in single-user mode (after "fsck -p" and mounting the usual file systems, since boot0cfg is in /usr/sbin); same result. I can't help but think that this is a symptom of a mistake -- especially for -STABLE. (-CURRENT/HEAD, I could believe, though a "heads up" would be welcome if such a change were contemplated.) Now, on my laptop, it's easy enough to just press the appropriate Fx key at boot; for that build machine -- which runs headless, keyboardless, but with a serial console -- I found that I needed to interrupt the boot sequence early -- just after the boot blocks have been loaded; I was prompted: >> FreeBSD/i386 BOOT Default: 0:ad(0,a)/boot/loader boot: and responded "0:ad(0,1,a)/boot/loader", which booted from slice 1 (which was running 4.11-STABLE); I then used "boot0cfg" to switch the default boot slice to "1". I should be in a position to be able to test potential fixes. Thanks, david -- David H. Wolfskill david@catwhisker.org There is a place in software engineering for an appreciation of history. See http://www.catwhisker.org/~david/publickey.gpg for public key.