Re: GEOM_STRIPE Problems on Reboot
On 7/14/2005 7:57 AM Pertti Kosunen wrote: Drew Tomlinson wrote: So where in the boot sequence is GEOM_STRIPE loaded? I'm starting to suspect it's being loaded twice. I have it in /boot/loader.conf which is where I thought it should be. Is there anywhere else to check? If you have GEOM_STRIPE in kernel do you have to load it from loader.conf? No. I have tried it both ways. Compiled in kernel and *NOT* in loader.conf. And *NOT* in kernel and load geom_stripe.ko from loader.conf. Same error either way. The only exception is that when GEOM_STRIPE is compiled in kernel, I can't (obviously) use the kldunload/kldload workaround to make the stripe accessible.. I have also tried removing the line that loads the module from loader.conf and *NOT* having GEOM_STRIPE compiled in the kernel. I wanted to see if GEOM_STRIPE still got loaded to test Giovanni Tirloni's theory that the module was being loaded twice. GEOM_STRIPE was not loaded when removed from loader.conf (as expected). So I'm still stuck. Any other ideas? Thanks for your help. I'll try anything at this point. :) Drew -- Visit The Alchemist's Warehouse Magic Tricks, DVDs, Videos, Books, & More! http://www.alchemistswarehouse.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GEOM_STRIPE Problems on Reboot
Drew Tomlinson wrote: So where in the boot sequence is GEOM_STRIPE loaded? I'm starting to suspect it's being loaded twice. I have it in /boot/loader.conf which is where I thought it should be. Is there anywhere else to check? If you have GEOM_STRIPE in kernel do you have to load it from loader.conf? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GEOM_STRIPE Problems on Reboot
On 7/14/2005 5:30 AM Giovanni P. Tirloni wrote: Drew Tomlinson wrote: 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? It looks like it's trying to add both disks again. I'd try to clean the metadata (gstripe clear from a fixit cdrom) and recreate it but I might be wrong. Thanks for your reply. Yes, now I see that it *DOES* look like it's trying to add it twice. I haven't tried cleaning the metadata as you suggest because I don't want to lose data on the drive if I can avoid it. Would your suggestion wipe the drive? Also, I wonder if the metadata is really bad? It works just fine if I kldunload and kldload the module. I ask because I would think that if the metadata were bad, I would get this error every time I created the stripe. So where in the boot sequence is GEOM_STRIPE loaded? I'm starting to suspect it's being loaded twice. I have it in /boot/loader.conf which is where I thought it should be. Is there anywhere else to check? Thanks, Drew -- Visit The Alchemist's Warehouse Magic Tricks, DVDs, Videos, Books, & More! http://www.alchemistswarehouse.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GEOM_STRIPE Problems on Reboot
Drew Tomlinson wrote: 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? It looks like it's trying to add both disks again. I'd try to clean the metadata (gstripe clear from a fixit cdrom) and recreate it but I might be wrong. -- Giovanni P. Tirloni / [EMAIL PROTECTED] / PGP: 0xD0315C26 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
GEOM_STRIPE Problems on Reboot
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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
