On Mon, 2004-09-20 at 17:47 +0200, Pawel Jakub Dawidek wrote: > On Mon, Sep 20, 2004 at 11:10:22AM -0400, Sven Willenberger wrote: > +> FreeBSD-5.3-Beta4 > +> I created a striped volume, newfs and mounted it fine and added the > +> entry in /etc/fstab. (created using the label so as to write the > +> metadata to disk and with a name of "thevolume") > +> > +> I added geom_stripe_load="YES" in /boot/loader.conf > +> > +> On bootup at the fsck stage, I get the message "could not stat /dev/ > +> stripe/thevolume. From single user, geom stripe load will load the > +> device and start the stripe at which point all is fine again. My > +> question is, is there another flag I need to set to have this startup at > +> boot time? > > I've some suspicion. Could you try this patch: > > http://people.freebsd.org/~pjd/patches/g_stripe.c.patch > > (so you have to: > > # cd /sys/geom/stripe > # patch < /path/to/g_stripe.c.patch > # cd /sys/modules/geom/geom_stripe > # make && make install > # reboot > ) > > And give me output of: > > # dmesg | grep skipping > Interestingly, once I applied the patch, and followed the make instructions you supplied above, the thing actually works (even though the patch looks like it was designed merely to trap a suspected error). I am not sure if the physical act of remaking the module from the modules directory solved the problem or what happened exactly. I will try a few more reboots and see what happens. "skipping" does not appear in the dmesg; the last few lines of my dmesg are: Waiting 10 seconds for SCSI devices to settle (probe6:ahd0:0:6:0): No or incomplete CDB sent to device. ahd0: Issued Channel A Bus Reset. 12 SCBs aborted ses0 at ahd0 bus 0 target 6 lun 0 ses0: <SUPER GEM318 0> Fixed Processor SCSI-2 device ses0: 3.300MB/s transfers ses0: SAF-TE Compliant Device da0 at ahd0 bus 0 target 0 lun 0 da0: <SEAGATE ST336607LC 0007> Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) da1 at ahd0 bus 0 target 1 lun 0 da1: <SEAGATE ST336607LC 0007> Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) da2 at ahd0 bus 0 target 2 lun 0 da2: <SEAGATE ST336607LC 0007> Fixed Direct Access SCSI-3 device da2: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! GEOM_STRIPE[1]: Creating device mysql (id=2294958973). GEOM_STRIPE[0]: Device mysql created (id=2294958973). GEOM_STRIPE[1]: Adding disk da1 to mysql. GEOM_STRIPE[0]: Disk da1 attached to mysql. GEOM_STRIPE[1]: Adding disk da2 to mysql. GEOM_STRIPE[0]: Disk da2 attached to mysql. GEOM_STRIPE[0]: Device mysql activated. Mounting root from ufs:/dev/da0s1a Sven P.S. that probe error in dmesg seems to happen when a Supermicro mobo is teamed up with a Seagate SCSI drive -- another issue for another day.Received on Mon Sep 20 2004 - 14:38:20 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:12 UTC