From tomlinson_dr@mykitchentable.net  Fri Jul 15 18:59:42 2005
Return-Path: <tomlinson_dr@mykitchentable.net>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BDECD16A421
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 15 Jul 2005 18:59:42 +0000 (GMT)
	(envelope-from tomlinson_dr@mykitchentable.net)
Received: from relay02.roc.ny.frontiernet.net (relay02.roc.ny.frontiernet.net [66.133.182.165])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2EB5543D46
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 15 Jul 2005 18:59:39 +0000 (GMT)
	(envelope-from tomlinson_dr@mykitchentable.net)
Received: from filter05.roc.ny.frontiernet.net (filter05.roc.ny.frontiernet.net [66.133.183.72])
	by relay02.roc.ny.frontiernet.net (Postfix) with ESMTP id 5FEFA3711B0
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 15 Jul 2005 18:59:38 +0000 (UTC)
Received: from relay02.roc.ny.frontiernet.net ([66.133.182.165])
	by filter05.roc.ny.frontiernet.net (filter05.roc.ny.frontiernet.net [66.133.183.72]) (amavisd-new, port 10024)
	with LMTP id 26554-01-25 for <FreeBSD-gnats-submit@freebsd.org>;
	Fri, 15 Jul 2005 18:59:38 +0000 (UTC)
Received: from blacklamb.mykitchentable.net (67-137-46-191.dsl2.elk.ca.frontiernet.net [67.137.46.191])
	by relay02.roc.ny.frontiernet.net (Postfix) with ESMTP id 4D2E2370EE8
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 15 Jul 2005 18:59:35 +0000 (UTC)
Received: by blacklamb.mykitchentable.net (Postfix, from userid 1001)
	id 262611C6C33; Fri, 15 Jul 2005 11:59:35 -0700 (PDT)
Message-Id: <20050715185935.262611C6C33@blacklamb.mykitchentable.net>
Date: Fri, 15 Jul 2005 11:59:35 -0700 (PDT)
From: Drew Tomlinson <drew@mykitchentable.net>
Reply-To: Drew Tomlinson <drew@mykitchentable.net>
To: FreeBSD-gnats-submit@freebsd.org
Cc: Drew Tomlinson <drew@mykitchentable.net>
Subject: GEOM_STRIPE Error On Boot
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         83521
>Category:       kern
>Synopsis:       GEOM_STRIPE Error On Boot
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pjd
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jul 15 19:00:36 GMT 2005
>Closed-Date:    Sat Sep 16 10:57:03 GMT 2006
>Last-Modified:  Sat Sep 16 10:57:03 GMT 2006
>Originator:     Drew Tomlinson <drew@mykitchentable.net>
>Release:        FreeBSD 5.4-RELEASE-p4 i386
>Organization:
>Environment:
blacklamb> dmesg
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD 5.4-RELEASE-p4 #1: Sun Jul 10 23:14:18 PDT 2005
    tomlinson_dr@blacklamb.mykitchentable.net:/usr/obj/usr/src/sys/BLACKLAMB
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Pentium III/Pentium III Xeon/Celeron (601.37-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x673  Stepping = 3
  Features=0x387fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,PN,MMX,FXSR,SSE>
real memory  = 805240832 (767 MB)
avail memory = 778248192 (742 MB)
ACPI APIC Table: <PTLTD    APIC  >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  1
 cpu1 (AP): APIC ID:  0
ioapic0 <Version 1.1> irqs 0-23 on motherboard
npx0: <math processor> on motherboard
npx0: INT 16 interface
acpi0: <PTLTD   RSDT> on motherboard
acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 4.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 UDMA33 controller> port 0x1c90-0x1c9f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0x1ca0-0x1cbf irq 19 at device 4.2 on pci0
usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
pci0: <bridge> at device 4.3 (no driver attached)
ahc0: <Adaptec aic7895 Ultra SCSI adapter> port 0x1000-0x10ff mem 0xfc100000-0xfc100fff irq 18 at device 5.0 on pci0
ahc0: Using left over BIOS settings
aic7895C: Ultra Wide Channel A, SCSI Id=7, 32/253 SCBs
ahc1: <Adaptec aic7895 Ultra SCSI adapter> port 0x1400-0x14ff mem 0xfc101000-0xfc101fff irq 18 at device 5.1 on pci0
ahc1: Host Adapter Bios disabled.  Using default SCSI device parameters
aic7895C: Ultra Wide Channel B, SCSI Id=7, 32/253 SCBs
fxp0: <Intel 82559 Pro/100 Ethernet> port 0x1cc0-0x1cff mem 0xfc000000-0xfc0fffff,0xfc102000-0xfc102fff irq 19 at device 6.0 on pci0
miibus0: <MII bus> on fxp0
inphy0: <i82555 10/100 media interface> on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:e0:18:c4:f4:5e
isp0: <Qlogic ISP 1020/1040 PCI SCSI Adapter> port 0x1800-0x18ff mem 0xfc103000-0xfc103fff irq 17 at device 9.0 on pci0
fwohci0: <VIA Fire II (VT6306)> port 0x1c00-0x1c7f mem 0xfc104000-0xfc1047ff irq 16 at device 10.0 on pci0
fwohci0: OHCI version 1.0 (ROM=1)
fwohci0: No. of Isochronous channels is 8.
fwohci0: EUI64 00:40:63:00:00:00:07:ff
fwohci0: Phy 1394a available S400, 3 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0
sbp0: <SBP-2/SCSI over FireWire> on firewire0
fwe0: <Ethernet over FireWire> on firewire0
if_fwe0: Fake Ethernet address: 02:40:63:00:07:ff
fwe0: Ethernet address: 02:40:63:00:07:ff
fwe0: if_start running deferred for Giant
fwohci0: Initiate bus reset
fwohci0: node_id=0xc800ffc1, gen=1, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
firewire0: bus manager 1 (me)
pcib2: <ACPI PCI-PCI bridge> at device 12.0 on pci0
pci2: <ACPI PCI bus> on pcib2
atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
fdc0: <floppy drive controller> port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x30 on acpi0
sio0: type 16550A, console
ppc0: <Standard parallel printer port> port 0x378-0x37b irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
orm0: <ISA Option ROMs> at iomem 0xc8000-0xcd7ff,0xc0000-0xc7fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounters tick every 10.000 msec
ad0: 76319MB <GENERIC GENERIC/A08.1500> [155061/16/63] at ata0-master UDMA33
ad1: 76319MB <WDC WD800AB-22CBA0/03.06A03> [155061/16/63] at ata0-slave UDMA33
firewire0: New S400 device ID:00d04b0cee100707
acd0: CDROM <HITACHI CDR-8435/0010> at ata1-master PIO4
Waiting 15 seconds for SCSI devices to settle
da0 at ahc0 bus 0 target 0 lun 0
da0: <SEAGATE SX19171W 9D32> 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: <SEAGATE SX19171W 9D32> 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: <Oxford 911G 0135> 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: <Oxford 911G 0135> 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!
Mounting root from ufs:/dev/da0s1a
System: FreeBSD blacklamb.mykitchentable.net 5.4-RELEASE-p4 FreeBSD 5.4-RELEASE-p4 #1: Sun Jul 10 23:14:18 PDT 2005 tomlinson_dr@blacklamb.mykitchentable.net:/usr/obj/usr/src/sys/BLACKLAMB i386


	
>Description:
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: <SEAGATE SX19171W 9D32> 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: <SEAGATE SX19171W 9D32> 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: <Oxford 911G 0135> 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: <Oxford 911G 0135> 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.  I also have tried compiling GEOM_STRIPE support in the kernel but get the same behavior (except that I can't perform the kldunload/load workaround).

	
>How-To-Repeat:
Happens upon every boot sequence.
>Fix:
Workaround:

At the single user prompt, use 'kldunload geom_stripe' to unload the module.  Then use 'kldload geom_stripe' to load.  The stripe is created without error.  Type 'exit' to continue full boot sequence.

	


>Release-Note:
>Audit-Trail:

From: Drew Tomlinson <drew@mykitchentable.net>
To: bug-followup@FreeBSD.org, drew@mykitchentable.net
Cc:  
Subject: Re: kern/83521: GEOM_STRIPE Error On Boot
Date: Fri, 15 Jul 2005 13:18:21 -0700

 Wanted to add that when I did compile a kernel with GEOM_STRIPE support, 
 I **DID** remove the load line from /boot/loader.
 
Responsible-Changed-From-To: freebsd-bugs->pjd 
Responsible-Changed-By: pjd 
Responsible-Changed-When: Sun Jul 17 13:02:15 GMT 2005 
Responsible-Changed-Why:  
I'll take this one. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=83521 
State-Changed-From-To: open->feedback 
State-Changed-By: pjd 
State-Changed-When: Sun Jul 17 13:02:55 GMT 2005 
State-Changed-Why:  
Your configuration seems to be a bit odd. 
How do you have providers da0d and da0s1d? 
It looks that you used bsdlabel(8) and fdisk(8) on plain da0. 

I wonder how such errors stops your boot process - gstripe only 
tells you that some provider is visible under two names (error 
17 is EEXIST). 

Do you see any error why single-user mode is started? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=83521 

From: Drew Tomlinson <drew@mykitchentable.net>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>, bug-followup@FreeBSD.org
Cc:  
Subject: Re: kern/83521: GEOM_STRIPE Error On Boot
Date: Sun, 17 Jul 2005 16:37:42 -0700

 On 7/17/2005 6:07 AM Pawel Jakub Dawidek wrote:
 
 >Synopsis: GEOM_STRIPE Error On Boot
 >
 >State-Changed-From-To: open->feedback
 >State-Changed-By: pjd
 >State-Changed-When: Sun Jul 17 13:02:55 GMT 2005
 >State-Changed-Why: 
 >  
 >
 Thank you very much for taking time to review this problem.
 
 Please tell me if I am not replying the right way as this is the first 
 PR I have ever filed.  I am not sure if I am doing this correctly.
 
 >Your configuration seems to be a bit odd.
 >How do you have providers da0d and da0s1d?
 >  
 >
 I'm not sure what a "provider" is.  da0s1a is my / .  I made the rest of 
 the space on the drive on da0s1d.
 
 >It looks that you used bsdlabel(8) and fdisk(8) on plain da0.
 >  
 >
 I installed using /usr/sbin/sysinstall. Thus fdisk and bsdlabel were 
 used however sysinstall does it.  Maybe this output will help?
 
 blacklamb# fdisk -s da0
 /dev/da0: 8683 cyl 64 hd 32 sec
 Part        Start        Size Type Flags
    1:           0    17783112 0xa5 0x80
 
 blacklamb# fdisk -s da1
 /dev/da1: 8683 cyl 64 hd 32 sec
 Part        Start        Size Type Flags
    1:           0    17783112 0xa5 0x80
 
 blacklamb# bsdlabel da0
 # /dev/da0:
 8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   a:  1024000        0    4.2BSD     2048 16384 64008
   c: 17783112        0    unused        0     0         # "raw" part, 
 don't edit
   d: 16759112  1024000    4.2BSD     2048 16384 28552
 
 blacklamb# bsdlabel da1
 # /dev/da1:
 8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   b:  1024000        0      swap                   
   c: 17783112        0    unused        0     0         # "raw" part, 
 don't edit
   d: 16759112  1024000    4.2BSD     2048 16384 28552
 
 >I wonder how such errors stops your boot process - gstripe only
 >tells you that some provider is visible under two names (error
 >17 is EEXIST).
 >
 >Do you see any error why single-user mode is started?
 >  
 >
 I'm using this stripe as my /usr.  Since there's no /usr, the boot 
 process stops.
 
 Please let me know if I can provide any additional information.  Thank 
 you again for looking at this.
 
 Drew

From: Pawel Jakub Dawidek <pjd@FreeBSD.org>
To: Drew Tomlinson <drew@mykitchentable.net>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/83521: GEOM_STRIPE Error On Boot
Date: Mon, 18 Jul 2005 10:28:16 +0200

 --H23uHpCUqgUcHMpK
 Content-Type: text/plain; charset=iso-8859-2
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Sun, Jul 17, 2005 at 04:37:42PM -0700, Drew Tomlinson wrote:
 +> >It looks that you used bsdlabel(8) and fdisk(8) on plain da0.
 +> >=20
 +> >
 +> I installed using /usr/sbin/sysinstall. Thus fdisk and bsdlabel were=20
 +> used however sysinstall does it.  Maybe this output will help?
 +>=20
 +> blacklamb# fdisk -s da0
 +> /dev/da0: 8683 cyl 64 hd 32 sec
 +> Part        Start        Size Type Flags
 +>   1:           0    17783112 0xa5 0x80
 +>=20
 +> blacklamb# fdisk -s da1
 +> /dev/da1: 8683 cyl 64 hd 32 sec
 +> Part        Start        Size Type Flags
 +>   1:           0    17783112 0xa5 0x80
 +>=20
 +> blacklamb# bsdlabel da0
 +> # /dev/da0:
 +> 8 partitions:
 +> #        size   offset    fstype   [fsize bsize bps/cpg]
 +>  a:  1024000        0    4.2BSD     2048 16384 64008
 +>  c: 17783112        0    unused        0     0         # "raw" part,=20
 +> don't edit
 +>  d: 16759112  1024000    4.2BSD     2048 16384 28552
 +>=20
 +> blacklamb# bsdlabel da1
 +> # /dev/da1:
 +> 8 partitions:
 +> #        size   offset    fstype   [fsize bsize bps/cpg]
 +>  b:  1024000        0      swap                  =20
 +>  c: 17783112        0    unused        0     0         # "raw" part,=20
 +> don't edit
 +>  d: 16759112  1024000    4.2BSD     2048 16384 28552
 
 Why did you configure bsdlabel partitions on da0 and da1? You should do
 this on da0s1 and da1s1 only.
 
 Are you sure you have used da0s1d and da1s1d providers when you were
 configuring your stripe device? Or maybe you have used da0d and da1d?
 
 --=20
 Pawel Jakub Dawidek                       http://www.wheel.pl
 pjd@FreeBSD.org                           http://www.FreeBSD.org
 FreeBSD committer                         Am I Evil? Yes, I Am!
 
 --H23uHpCUqgUcHMpK
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.4 (FreeBSD)
 
 iD8DBQFC22ggForvXbEpPzQRAsixAJ0ZEGU7/tSWhAbJKCcfqZw2+vJcaACg335U
 O4X59Cyff5QTigEhnXmkA4M=
 =aczU
 -----END PGP SIGNATURE-----
 
 --H23uHpCUqgUcHMpK--

From: Drew Tomlinson <drew@mykitchentable.net>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/83521: GEOM_STRIPE Error On Boot
Date: Mon, 18 Jul 2005 10:32:27 -0700

 On 7/18/2005 1:28 AM Pawel Jakub Dawidek wrote:
 
 >On Sun, Jul 17, 2005 at 04:37:42PM -0700, Drew Tomlinson wrote:
 >+> >It looks that you used bsdlabel(8) and fdisk(8) on plain da0.
 >+> > 
 >+> >
 >+> I installed using /usr/sbin/sysinstall. Thus fdisk and bsdlabel were 
 >+> used however sysinstall does it.  Maybe this output will help?
 >+> 
 >+> blacklamb# fdisk -s da0
 >+> /dev/da0: 8683 cyl 64 hd 32 sec
 >+> Part        Start        Size Type Flags
 >+>   1:           0    17783112 0xa5 0x80
 >+> 
 >+> blacklamb# fdisk -s da1
 >+> /dev/da1: 8683 cyl 64 hd 32 sec
 >+> Part        Start        Size Type Flags
 >+>   1:           0    17783112 0xa5 0x80
 >+> 
 >+> blacklamb# bsdlabel da0
 >+> # /dev/da0:
 >+> 8 partitions:
 >+> #        size   offset    fstype   [fsize bsize bps/cpg]
 >+>  a:  1024000        0    4.2BSD     2048 16384 64008
 >+>  c: 17783112        0    unused        0     0         # "raw" part, 
 >+> don't edit
 >+>  d: 16759112  1024000    4.2BSD     2048 16384 28552
 >+> 
 >+> blacklamb# bsdlabel da1
 >+> # /dev/da1:
 >+> 8 partitions:
 >+> #        size   offset    fstype   [fsize bsize bps/cpg]
 >+>  b:  1024000        0      swap                   
 >+>  c: 17783112        0    unused        0     0         # "raw" part, 
 >+> don't edit
 >+>  d: 16759112  1024000    4.2BSD     2048 16384 28552
 >
 >Why did you configure bsdlabel partitions on da0 and da1? You should do
 >this on da0s1 and da1s1 only.
 >  
 >
 I don't know.  I used sysinstall like I have always done in the 4x 
 version.  I guess I did something wrong?  How should I fix it?  Is there 
 any way to fix it without wiping all the data from the disk?
 
 >Are you sure you have used da0s1d and da1s1d providers when you were
 >configuring your stripe device? Or maybe you have used da0d and da1d?
 >  
 >
 
 I am 99.9% sure I used da0s1d and da1s1d.  I used the example in the man 
 page and changed it for my system.  This is the command I used:
 
 gstripe label -v -s 131072 data /dev/da0s1d /dev/da1s1d
 
 Is there some way to verify that I used this command?
 
 Thank you again,
 
 Drew

From: Pawel Jakub Dawidek <pjd@FreeBSD.org>
To: Drew Tomlinson <drew@mykitchentable.net>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/83521: GEOM_STRIPE Error On Boot
Date: Mon, 18 Jul 2005 23:19:11 +0200

 --KO6AnYnUdC9Z3rW+
 Content-Type: text/plain; charset=iso-8859-2
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Mon, Jul 18, 2005 at 10:32:27AM -0700, Drew Tomlinson wrote:
 +> >Why did you configure bsdlabel partitions on da0 and da1? You should do
 +> >this on da0s1 and da1s1 only.
 +> >=20
 +> >
 +> I don't know.  I used sysinstall like I have always done in the 4x=20
 +> version.  I guess I did something wrong?  How should I fix it?  Is there=
 =20
 +> any way to fix it without wiping all the data from the disk?
 +>=20
 +> >Are you sure you have used da0s1d and da1s1d providers when you were
 +> >configuring your stripe device? Or maybe you have used da0d and da1d?
 +> >=20
 +> >
 +>=20
 +> I am 99.9% sure I used da0s1d and da1s1d.  I used the example in the man=
 =20
 +> page and changed it for my system.  This is the command I used:
 +>=20
 +> gstripe label -v -s 131072 data /dev/da0s1d /dev/da1s1d
 +>=20
 +> Is there some way to verify that I used this command?
 
 You can try:
 
 	# gstripe dump /dev/da[01]d /dev/da[01]s1d
 
 --=20
 Pawel Jakub Dawidek                       http://www.wheel.pl
 pjd@FreeBSD.org                           http://www.FreeBSD.org
 FreeBSD committer                         Am I Evil? Yes, I Am!
 
 --KO6AnYnUdC9Z3rW+
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.4 (FreeBSD)
 
 iD8DBQFC3BzPForvXbEpPzQRAob2AJkBFsWivEkxhkeipOpEGdigY+vycACeK5f7
 LofXsJ6WP9L1R23cXXjhHFQ=
 =oQl/
 -----END PGP SIGNATURE-----
 
 --KO6AnYnUdC9Z3rW+--

From: Drew Tomlinson <drew@mykitchentable.net>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/83521: GEOM_STRIPE Error On Boot
Date: Mon, 18 Jul 2005 16:57:49 -0700

 On 7/18/2005 2:19 PM Pawel Jakub Dawidek wrote:
 
 >On Mon, Jul 18, 2005 at 10:32:27AM -0700, Drew Tomlinson wrote:
 >+> >Why did you configure bsdlabel partitions on da0 and da1? You should do
 >+> >this on da0s1 and da1s1 only.
 >+> > 
 >+> >
 >+> I don't know.  I used sysinstall like I have always done in the 4x 
 >+> version.  I guess I did something wrong?  How should I fix it?  Is there 
 >+> any way to fix it without wiping all the data from the disk?
 >+> 
 >+> >Are you sure you have used da0s1d and da1s1d providers when you were
 >+> >configuring your stripe device? Or maybe you have used da0d and da1d?
 >+> > 
 >+> >
 >+> 
 >+> I am 99.9% sure I used da0s1d and da1s1d.  I used the example in the man 
 >+> page and changed it for my system.  This is the command I used:
 >+> 
 >+> gstripe label -v -s 131072 data /dev/da0s1d /dev/da1s1d
 >+> 
 >+> Is there some way to verify that I used this command?
 >
 >You can try:
 >
 >	# gstripe dump /dev/da[01]d /dev/da[01]s1d
 >  
 >
 
 Thank you.  I tried it and this is what I got:
 
 blacklamb# gstripe dump /dev/da[01]d /dev/da[01]s1d
 Metadata on /dev/da0s1d:
          Magic string: GEOM::STRIPE
      Metadata version: 3
           Device name: data
             Device ID: 896603271
           Disk number: 0
 Total number of disks: 2
           Stripe size: 131072
    Hardcoded provider:
 
 Metadata on /dev/da1s1d:
          Magic string: GEOM::STRIPE
      Metadata version: 3
           Device name: data
             Device ID: 896603271
           Disk number: 1
 Total number of disks: 2
           Stripe size: 131072
    Hardcoded provider:
 
 But maybe you meant 'gstripe dump /dev/da[01] /dev/da[01]s1d'?  That 
 gives this:
 
 blacklamb# gstripe dump /dev/da[01] /dev/da[01]s1d
 Metadata on /dev/da0:
          Magic string: GEOM::STRIPE
      Metadata version: 3
           Device name: data
             Device ID: 896603271
           Disk number: 0
 Total number of disks: 2
           Stripe size: 131072
    Hardcoded provider:
 
 Metadata on /dev/da1:
          Magic string: GEOM::STRIPE
      Metadata version: 3
           Device name: data
             Device ID: 896603271
           Disk number: 1
 Total number of disks: 2
           Stripe size: 131072
    Hardcoded provider:
 
 Metadata on /dev/da0s1d:
          Magic string: GEOM::STRIPE
      Metadata version: 3
           Device name: data
             Device ID: 896603271
           Disk number: 0
 Total number of disks: 2
           Stripe size: 131072
    Hardcoded provider:
 
 Metadata on /dev/da1s1d:
          Magic string: GEOM::STRIPE
      Metadata version: 3
           Device name: data
             Device ID: 896603271
           Disk number: 1
 Total number of disks: 2
           Stripe size: 131072
    Hardcoded provider:
 
 Does this mean I have metadata on both /dev/da0 and /dev/da0s1d?  And 
 again on both /dev/da1 and /dev/da1s1d?  Is that why it tries to load 
 twice and makes ERROR=17?  If so, how can I fix it?
 
 Thank you again!
 
 Drew

From: Drew Tomlinson <drew@mykitchentable.net>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/83521: GEOM_STRIPE Error On Boot
Date: Thu, 21 Jul 2005 11:46:54 -0700

 On 7/18/2005 4:57 PM Drew Tomlinson wrote:
 
 > On 7/18/2005 2:19 PM Pawel Jakub Dawidek wrote:
 >
 >> On Mon, Jul 18, 2005 at 10:32:27AM -0700, Drew Tomlinson wrote:
 >> +> >Why did you configure bsdlabel partitions on da0 and da1? You 
 >> should do
 >> +> >this on da0s1 and da1s1 only.
 >> +> > +> >
 >> +> I don't know.  I used sysinstall like I have always done in the 4x 
 >> +> version.  I guess I did something wrong?  How should I fix it?  Is 
 >> there +> any way to fix it without wiping all the data from the disk?
 >> +> +> >Are you sure you have used da0s1d and da1s1d providers when 
 >> you were
 >> +> >configuring your stripe device? Or maybe you have used da0d and 
 >> da1d?
 >> +> > +> >
 >> +> +> I am 99.9% sure I used da0s1d and da1s1d.  I used the example 
 >> in the man +> page and changed it for my system.  This is the command 
 >> I used:
 >> +> +> gstripe label -v -s 131072 data /dev/da0s1d /dev/da1s1d
 >> +> +> Is there some way to verify that I used this command?
 >>
 >> You can try:
 >>
 >>     # gstripe dump /dev/da[01]d /dev/da[01]s1d
 >>  
 >>
 >
 > Thank you.  I tried it and this is what I got:
 >
 > blacklamb# gstripe dump /dev/da[01]d /dev/da[01]s1d
 > Metadata on /dev/da0s1d:
 >         Magic string: GEOM::STRIPE
 >     Metadata version: 3
 >          Device name: data
 >            Device ID: 896603271
 >          Disk number: 0
 > Total number of disks: 2
 >          Stripe size: 131072
 >   Hardcoded provider:
 >
 > Metadata on /dev/da1s1d:
 >         Magic string: GEOM::STRIPE
 >     Metadata version: 3
 >          Device name: data
 >            Device ID: 896603271
 >          Disk number: 1
 > Total number of disks: 2
 >          Stripe size: 131072
 >   Hardcoded provider:
 >
 > But maybe you meant 'gstripe dump /dev/da[01] /dev/da[01]s1d'?  That 
 > gives this:
 >
 > blacklamb# gstripe dump /dev/da[01] /dev/da[01]s1d
 > Metadata on /dev/da0:
 >         Magic string: GEOM::STRIPE
 >     Metadata version: 3
 >          Device name: data
 >            Device ID: 896603271
 >          Disk number: 0
 > Total number of disks: 2
 >          Stripe size: 131072
 >   Hardcoded provider:
 >
 > Metadata on /dev/da1:
 >         Magic string: GEOM::STRIPE
 >     Metadata version: 3
 >          Device name: data
 >            Device ID: 896603271
 >          Disk number: 1
 > Total number of disks: 2
 >          Stripe size: 131072
 >   Hardcoded provider:
 >
 > Metadata on /dev/da0s1d:
 >         Magic string: GEOM::STRIPE
 >     Metadata version: 3
 >          Device name: data
 >            Device ID: 896603271
 >          Disk number: 0
 > Total number of disks: 2
 >          Stripe size: 131072
 >   Hardcoded provider:
 >
 > Metadata on /dev/da1s1d:
 >         Magic string: GEOM::STRIPE
 >     Metadata version: 3
 >          Device name: data
 >            Device ID: 896603271
 >          Disk number: 1
 > Total number of disks: 2
 >          Stripe size: 131072
 >   Hardcoded provider:
 >
 > Does this mean I have metadata on both /dev/da0 and /dev/da0s1d?  And 
 > again on both /dev/da1 and /dev/da1s1d?  Is that why it tries to load 
 > twice and makes ERROR=17?  If so, how can I fix it?
 >
 > Thank you again!
 >
 > Drew
 >
 
 I just had a thought.  When I used sysinstall to create da0 and da1, I 
 used "Dangerously Dedicated" because I use this system for FBSD only.  I 
 made all my disks "Dangerously Dedicated" since the beginning of version 
 4 and just continued.  Could this have something to do with the problem 
 I'm having?
 
 Thanks,
 
 Drew
 
 -- 
 Visit The Alchemist's Warehouse
 Magic Tricks, DVDs, Videos, Books, & More!
 
 http://www.alchemistswarehouse.com
 

From: Drew Tomlinson <drew@mykitchentable.net>
To: bug-followup@FreeBSD.org, pjd@FreeBSD.org
Cc:  
Subject: Re: kern/83521: GEOM_STRIPE Error On Boot
Date: Sat, 10 Sep 2005 10:12:05 -0700

 Just wondering if you had any more suggestions on how I might resolve 
 this problem?  I don't mean to be a pest so if you tell me to go away, I 
 will.
 
 Thanks for your help!
 
 Drew

From: Drew Tomlinson <drew@mykitchentable.net>
To: bug-followup@FreeBSD.org, drew@mykitchentable.net
Cc:  
Subject: Re: kern/83521: GEOM_STRIPE Error On Boot
Date: Sat, 17 Sep 2005 19:07:14 -0700

 I did some more checking and this may be of help in figuring out what's 
 going on.  I set  kern.geom.stripe.debug=3 in /boot/loader.conf and then 
 rebooted.  The following is the (what I think) relevant part of the 
 console output from the reboot:
 
 ---BEGIN---
 ad0: 76319MB <GENERIC GENERIC/A08.1500> [155061/16/63] at ata0-master UDMA33
 ad1: 76319MB <WDC WD800AB-22CBA0/03.06A03> [155061/16/63] at ata0-slave 
 UDMA33
 acd0: CDROM <HITACHI CDR-8435/0010> at ata1-master PIO4
 Waiting 10 seconds for SCSI devices to settle
 GEOM_STRIPE[3]: Tasting fd0.
 GEOM_STRIPE[3]: Tasting ad0.
 GEOM_STRIPE[3]: Tasting ad1.
 GEOM_STRIPE[3]: Tasting acd0.
 GEOM_STRIPE[3]: Tasting ad0c.
 GEOM_STRIPE[3]: Tasting ad0d.
 GEOM_STRIPE[3]: Tasting ad0s1.
 GEOM_STRIPE[3]: Tasting ad1c.
 GEOM_STRIPE[3]: Tasting ad1s1.
 GEOM_STRIPE[3]: Tasting ad0cs1.
 GEOM_STRIPE[3]: Tasting ad0ds1.
 GEOM_STRIPE[3]: Tasting ad0s1c.
 GEOM_STRIPE[3]: Tasting ad0s1d.
 GEOM_STRIPE[3]: Tasting ad1cs1.
 GEOM_STRIPE[3]: Tasting ad1s1c.
 GEOM_STRIPE[3]: Tasting ad1s1d.
 GEOM_STRIPE[3]: Tasting ad0cs1c.
 GEOM_STRIPE[3]: Tasting ad0cs1d.
 GEOM_STRIPE[3]: Tasting ad0ds1c.
 GEOM_STRIPE[3]: Tasting ad0ds1d.
 GEOM_STRIPE[3]: Tasting ad1cs1c.
 GEOM_STRIPE[3]: Tasting ad1cs1d.
 sa0 at isp0 bus 0 target 6 lun 0
 sa0: <DEC DLT2000 840F> Removable Sequential Access SCSI-2 device
 sa0: 3.300MB/s transfers
 da0 at ahc0 bus 0 target 0 lun 0
 da0: <SEAGATE SX19171W 9D32> 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: <SEAGATE SX19171W 9D32> 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)
 SMP: AP CPU #1 Launched!
 GEOM_STRIPE[3]: Tasting da0.
 GEOM_STRIPE[3]: Tasting da1.
 GEOM_STRIPE[3]: Tasting da0c.
 GEOM_STRIPE[3]: Tasting da0s1.
 GEOM_STRIPE[3]: Tasting da1b.
 GEOM_STRIPE[3]: Tasting da1c.
 GEOM_STRIPE[3]: Tasting da1d.
 GEOM_STRIPE[1]: Creating device data (id=896603271).
 GEOM_STRIPE[0]: Device data created (id=896603271).
 GEOM_STRIPE[1]: Adding disk da1d to data.
 GEOM_STRIPE[0]: Disk da1d attached to data.
 GEOM_STRIPE[3]: Tasting da1s1.
 GEOM_STRIPE[3]: Tasting da0cs1.
 GEOM_STRIPE[3]: Tasting da0s1a.
 GEOM_STRIPE[3]: Tasting da0s1c.
 GEOM_STRIPE[3]: Tasting da0s1d.
 GEOM_STRIPE[1]: Creating device data (id=4121873480).
 GEOM_STRIPE[0]: Device data already configured.
 GEOM_STRIPE[0]: Cannot create device data.
 GEOM_STRIPE[3]: Tasting da1bs1.
 GEOM_STRIPE[3]: Tasting da1cs1.
 GEOM_STRIPE[3]: Tasting da1s1b.
 GEOM_STRIPE[3]: Tasting da1s1c.
 GEOM_STRIPE[3]: Tasting da1s1d.
 GEOM_STRIPE[1]: Creating device data (id=4121873480).
 GEOM_STRIPE[0]: Device data already configured.
 GEOM_STRIPE[0]: Cannot create device data.
 GEOM_STRIPE[3]: Tasting da0cs1a.
 GEOM_STRIPE[3]: Tasting da0cs1c.
 GEOM_STRIPE[3]: Tasting da0cs1d.
 GEOM_STRIPE[1]: Creating device data (id=4121873480).
 GEOM_STRIPE[0]: Device data already configured.
 GEOM_STRIPE[0]: Cannot create device data.
 GEOM_STRIPE[3]: Tasting da1bs1b.
 GEOM_STRIPE[3]: Tasting da1bs1c.
 GEOM_STRIPE[3]: Tasting da1bs1d.
 GEOM_STRIPE[3]: Tasting da1cs1b.
 GEOM_STRIPE[3]: Tasting da1cs1c.
 GEOM_STRIPE[3]: Tasting da1cs1d.
 GEOM_STRIPE[1]: Creating device data (id=4121873480).
 GEOM_STRIPE[0]: Device data already configured.
 GEOM_STRIPE[0]: Cannot create device data.
 Mounting root from ufs:/dev/da0s1a
 Pre-seeding PRNG: kickstart.
 Loading configuration files.
 Entropy harvesting: interrupts ethernet point_to_point kickstart.
 GEOM_STRIPE[0]: Disk da1d removed from data.
 GEOM_STRIPE[0]: Device data destroyed.
 swapon: adding /dev/da1s1b as swap device
 Starting file system checks:
 /dev/da0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS
 /dev/da0s1a: clean, 219581 free (725 frags, 27357 blocks, 0.3% 
 fragmentation)
 Can't stat /dev/stripe/data: No such file or directory
 Can't stat /dev/stripe/data: No such file or directory
 Can't stat /dev/stripe/data: No such file or directory
 /dev/stripe/data: CAN'T CHECK FILE SYSTEM.
 /dev/stripe/data: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
 THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY:
         ufs: /dev/stripe/data (/usr)
 Automatic file system check failed; help!
 Enter full pathname of shell or RETURN for /bin/sh:
 ---END---
 
 So it appears to me that I do have metadata on both /dev/da[01] and 
 /dev/da[01]s1d as indicated in previous PR entries and that's why 
 geom_stripe is trying to load twice.  The question now is, how can I fix 
 this?
 
 Thanks,
 
 Drew
 
 -- 
 Visit The Alchemist's Warehouse
 Magic Tricks, DVDs, Videos, Books, & More!
 
 http://www.alchemistswarehouse.com
 

From: Jung-uk Kim <jkim@FreeBSD.org>
To: bug-followup@FreeBSD.org
Cc: drew@mykitchentable.net
Subject: Re: kern/83521: GEOM_STRIPE Error On Boot
Date: Mon, 3 Apr 2006 15:37:42 -0400

 You can hardcode providers with '-h' option.  Try
 
 gstripe label -hv -s 131072 data /dev/da0s1d /dev/da1s1d
 
 That way gstripe won't taste the label twice.
 
 Jung-uk Kim
State-Changed-From-To: feedback->closed 
State-Changed-By: pjd 
State-Changed-When: Sat Sep 16 10:53:21 UTC 2006 
State-Changed-Why:  
Work-around was given by Jung-uk Kim <jkim@FreeBSD.org> and no answer 
from the author. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=83521 
>Unformatted:
