From owner-freebsd-stable@FreeBSD.ORG Wed Jul 13 21:52:44 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 B6B2616A41C for ; Wed, 13 Jul 2005 21:52:44 +0000 (GMT) (envelope-from drew@mykitchentable.net) Received: from relay03.roc.ny.frontiernet.net (relay03.roc.ny.frontiernet.net [66.133.182.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A23543D45 for ; Wed, 13 Jul 2005 21:52:44 +0000 (GMT) (envelope-from drew@mykitchentable.net) Received: from filter08.roc.ny.frontiernet.net (filter08.roc.ny.frontiernet.net [66.133.183.75]) by relay03.roc.ny.frontiernet.net (Postfix) with ESMTP id 810D735869C for ; Wed, 13 Jul 2005 21:52:43 +0000 (UTC) Received: from relay03.roc.ny.frontiernet.net ([66.133.182.166]) by filter08.roc.ny.frontiernet.net (filter08.roc.ny.frontiernet.net [66.133.183.75]) (amavisd-new, port 10024) with LMTP id 07115-05-15 for ; Wed, 13 Jul 2005 21:52:43 +0000 (UTC) Received: from blacklamb.mykitchentable.net (67-137-46-191.dsl2.elk.ca.frontiernet.net [67.137.46.191]) by relay03.roc.ny.frontiernet.net (Postfix) with ESMTP id 224E435873F for ; Wed, 13 Jul 2005 21:52:41 +0000 (UTC) Received: from [165.107.42.217] (unknown [165.107.42.217]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by blacklamb.mykitchentable.net (Postfix) with ESMTP id 5F6451C6B9C for ; Wed, 13 Jul 2005 14:52:40 -0700 (PDT) Message-ID: <42D58CDA.3000208@mykitchentable.net> Date: Wed, 13 Jul 2005 14:51:22 -0700 From: Drew Tomlinson User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20040701 (2.0) at filter08.roc.ny.frontiernet.net Subject: GEOM_STRIPE Problems on Reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jul 2005 21:52:44 -0000 I posted the following on -questions but have not received any assistance. I also have since tried compiling GEOM_STRIPE support in the kernel but get the same behavior (except that I can't perform the kldunload/load workaround). I'm hoping someone here may be able to point me in the right direction Thanks, Drew -------- Original Message -------- I just installed 5.4-RELEASE. I created a gstripe volume per the example in the man page. Googling revealed that I needed to load the geom_stripe module upon reboot so the volume can be created. I added the following line to /boot/loader.conf: geom_stripe_load="yes" Now upon reboot, I get this output: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8683MB (17783112 512 byte sectors: 64H 32S/T 8683C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8683MB (17783112 512 byte sectors: 64H 32S/T 8683C) da2 at sbp0 bus 0 target 0 lun 0 da2: Fixed Simplified Direct Access SCSI-4 device da2: 50.000MB/s transfers da2: 76351MB (156368016 512 byte sectors: 255H 63S/T 9733C) da3 at sbp0 bus 0 target 0 lun 1 da3: Fixed Simplified Direct Access SCSI-4 device da3: 50.000MB/s transfers da3: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) SMP: AP CPU #1 Launched! GEOM_STRIPE: Device data created (id=896603271). GEOM_STRIPE: Disk da0d attached to data. GEOM_STRIPE: Disk da1d attached to data. GEOM_STRIPE: Device data activated. GEOM_STRIPE: Cannot add disk da0s1d to data (error=17). GEOM_STRIPE: Cannot add disk da1s1d to data (error=17). Mounting root from ufs:/dev/da0s1a Then the machine comes up in single user mode. At this point if I unload and reload geom_stripe, then the volume is created just fine and I can boot the system in full production mode. Any ideas on why I'm seeing this behavior? How can I fix it so that my machine reboots without incident? Thanks, Drew