From owner-freebsd-questions@FreeBSD.ORG Sat Aug 26 22:06:21 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB89F16A4DF for ; Sat, 26 Aug 2006 22:06:21 +0000 (UTC) (envelope-from astounding@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C8D74482B for ; Sat, 26 Aug 2006 22:06:11 +0000 (GMT) (envelope-from astounding@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so1237996wxd for ; Sat, 26 Aug 2006 15:06:11 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=L59QLRyP20x8QZ9mTZcaTIivTYqmTTbcPTuiLPJ9PlJcR3K/vvj5zny7bFCntIP17nfXg2D/tcOaT4YQPg4FtWFWxWiwiB+VP5Gm1B5HR/eoADgBnu+p/W+tYh2Ay1tD8RBsLug617xtjchOS5IJ6mcPFUE5nXH72pwwb+alrDw= Received: by 10.70.19.2 with SMTP id 2mr6782254wxs; Sat, 26 Aug 2006 15:06:11 -0700 (PDT) Received: by 10.70.21.16 with HTTP; Sat, 26 Aug 2006 15:06:11 -0700 (PDT) Message-ID: Date: Sat, 26 Aug 2006 16:06:11 -0600 From: "Aaron Gifford" To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Booting gvinum fails: missing /dev/gvinum/* device entries X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Aug 2006 22:06:21 -0000 I'm running 6.1R (amd64) on a system, and recently added more drives. I decided I would eventually migrate my root system off the existing drive (/dev/ad0a) to use a gvinum root (/dev/gvinum/root) filesystem and eventually remove the old hard drive altogether. The two added drives (ad1 and ad2) are labeled (with bsdlabel) identically like this: # size offset fstype a: 4194039 281 4.2BSD b: 4194394 4194320 vinum c: 625142448 0 unused d: 4194304 16 vinum e: 616753824 8388624 vinum The gvinum configuration looks like: # Drives for the root gvinum RAID-1 volume: drive a1 device /dev/ad1d drive a2 device /dev/ad2d # # Drives for the swap gvinum RAID-1 volume: drive b1 device /dev/ad1b drive b2 device /dev/ad2b # # Drives for the usr gvinum RAID-1 volume: drive c1 device /dev/ad1e drive c2 device /dev/ad2e # # RAID-1 volume for root: volume root plex org concat sd length 0 drive a1 plex org concat sd length 0 drive a2 # # RAID-1 volume for swap: volume swap plex org concat sd length 0 drive b1 plex org concat sd length 0 drive b2 # # RAID-1 volume for usr: volume usr plex org concat sd length 0 drive c1 sd length 0 drive c2 Once the gvinum volumes were created, new filesystems created, and mounted temporarily on /mnt and /mnt/usr, I added a line to loader.conf in the new drives' future /boot directory containing 'geom_vinum_load="YES"'. Oh, and the new drives' future /etc/fstab contains: # Device Mountpoint FStype Options Dump Pass# /dev/gvinum/swap none swap sw 0 0 /dev/gvinum/root / ufs rw 1 1 /dev/gvinum/usr /usr ufs rw 2 2 Oh, boot blocks were also written to both drives before the gvinum volumes were set up using bsdlabel -b. Now for the test. I rebooted, changing the boot order in BIOS so the first drive, ad1 (instead of ad0) was the boot source. THE PROBLEM: No matter what I tried, booting always failed at the point of mounting the root filesystem. I would be kicked to a "mountroot>" prompt. Any attempts at mounting root from ufs:/dev/gvinum/root failed. Even if I loaded geom_vinum.ko by hand during boot to be absolutely sure gvinum was loaded, this failed. At "mountroot>", the gvinum devices did not show up at all. So I fell back and mounted /dev/ad0a (my old non-gvinum drive) as root. That worked. kldstat showed that indeed geom_vinum.ko WAS successfully loaded. But when I looked in /dev nothing for gvinum showed up there. It was empty. The "gvinum list" command showed all my gvinum volumes working, but there were NO entries in /dev. No wonder I was unable to mount /dev/gvinum/root -- There was no device entry. So what's the deal? Any suggestions? Is there something I need to compile in my kernel? If I boot off my old drive and only load the geom_vinum.ko module by hand at the command-line by using the gvinum command, the entries in /dev/ DO appear normally. Puzzled, frustrated, Aaron out.