Re: vinum concatenated raid setup problems - SOLVED
On Friday, 24 October 2003 at 12:47:52 -0400, Alvin Gunkel wrote: Mike, Thanks for the pointers on the fstab file, they solved that part of the puzzle. (and trying to help with the other issues) Greg, Thanks for pointing me to the right part of the vinum manpage...it was indeed the simple fact that I was trying to build the configuration on disk's rather than partitions that was sabotaging the mission! I see this has been solved, but i'll throw one more gotcha to watch for out there. Use of 'vinum saveconfig' is a good thing. It has no effect under these circumstances. From the vinum man page: saveconfig Save the current configuration to disk. Normally this is not necessary, Please note. since vinum automatically saves any change in configuration. If an error occurs on startup, updates will be disabled. When you reenable them with the setdaemon command, vinum does not automatically save the configuration to disk. Use this command to save the configuration. As I was learning to use vinum I made frequent mistakes, disabling updates, then built the system, rebooted, and nothing survived ;) Had to rtfm a couple of times before I caught that. Vinum now reminds you every time you enter a command if configuration updates are disabled. The trouble with recommending this sort of thing is that it has no relevance, and it'll go down in folklore as a solution to all kinds of problems, when in fact it has a very limited scope and wouldn't have helped here. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
RE: vinum concatenated raid setup problems
start_vinum=YES is already in the /etc/rc.conf...see below: --- thegibsor# cat /etc/rc.conf # -- sysinstall generated deltas -- # Sun Oct 19 20:37:29 2003 # Created: Sun Oct 19 20:37:29 2003 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=thegibsor.thebeatbox.org sshd_enable=YES usbd_enable=NO start_vinum=YES # set to YES to start vinum Doh! My faux pas. I'm reading up a bit, but this one may be best left to Greg. Have you verified that the vinum module has loaded after boot? One other thing I just noticed, you didn't use setupstate in the volume line of your config file...did you do an init on the second plex/subdisk before you newfs'd and mounted the volume? not a faux pas for me!! as i am new to this and it could be anything, I did init the second plex before newfs'ing and mounting it, but I think that the auto mounting is less of a problem than the config not being read (or vinum not starting) with the reboot. If i can get that fixed, i think i will be well on my way to getting this solved... it doesn't look like the vinum kld is being loaded, since even with the vinum config gone, it should say something like no vinum drives found, vinum not loaded in dmesg (i think, please correct me if im wrong) i will investigate this furthar and report back. thanks for the help roland ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum concatenated raid setup problems
it doesn't look like the vinum kld is being loaded, since even with the vinum config gone, it should say something like no vinum drives found, vinum not loaded in dmesg (i think, please correct me if im wrong) i will investigate this furthar and report back. So you've checked kldstat following boot? Does the vinum kld load when you manually start vinum? What about with kldload? I just loaded it and it did indeed complain of no drives being found. What do the contents of /dev/vinum look like? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum concatenated raid setup problems
On Friday, 24 October 2003 at 0:27:03 -0700, Mike Maltese wrote: it doesn't look like the vinum kld is being loaded, since even with the vinum config gone, it should say something like no vinum drives found, vinum not loaded in dmesg (i think, please correct me if im wrong) i will investigate this furthar and report back. So you've checked kldstat following boot? Does the vinum kld load when you manually start vinum? What about with kldload? I just loaded it and it did indeed complain of no drives being found. What do the contents of /dev/vinum look like? Given the output he showed at the beginning, it's clear that the kld is being loaded correctly. Watch for the next reply. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
Re: vinum concatenated raid setup problems
[Format recovered--see http://www.lemis.com/email/email-format.html] Computer output wrapped. On Thursday, 23 October 2003 at 23:10:01 -0500, [EMAIL PROTECTED] wrote: Hello all, I have been trying without success to implement a simple vinum concatenated RAID system made up of 2 IDE drives. The boot drive is located on another physical drive and is not part of the RAID. The problems: 1 - I am able to build the RAID, create a filesystem, and mount to a directory in the tree. But I am not able to figure out how to add an entry to my /etc/fstab file so that it is automatically mounted on reboot. I have looked in the handbook and all it says is to add the proper entries. I simple do not know what entry to add. Looks like this question has been answered. 2 - On reboot, the vinum config is erased. (or at least thats what it looks like...see dmesg output for info) It is my understanding that on reboot, vinum reads it's configuration from each vinum drive. Since I was able to create and mount the RAID, I assume that the configuration would still be there on reboot, even thought it is not being mounted with fstab (see problem 1). I have tried this on several systems and have yet to be successful in having a vinum config survive reboot. I have re-read and re-read the vinum section in the handbook and have looked elsewhere but have had no luck :( Relevent Info: I have not made any changes to system or vinum sources. The system is a generic 5.1 installed from FTP today. From the box: VINUM STATE BEFORE REBOOT ## vinum - l 2 drives: D a State: up /dev/ad2A: 981/28629 MB (3%) D b State: up /dev/ad3A: 981/28629 MB (3%) 1 volumes: V core State: up Plexes: 2 Size: 27 GB 2 plexes: P core.p0 C State: up Subdisks: 1 Size: 27 GB P core.p1 C State: up Subdisks: 1 Size: 27 GB 2 subdisks: S core.p0.s0State: up D: aSize: 27 GB S core.p1.s0State: up D: bSize: 27 GB #VINUM CONFIG FILE## thegibsor# cat vinum_config drive a device /dev/ad2 drive b device /dev/ad3 Vinum drives should be partitions, not disks. This is why Vinum is not finding anything after 'vinum start'. From the man page: DRIVE LAYOUT CONSIDERATIONS vinum drives are currently BSD disk partitions. They must be of type vinum in order to avoid overwriting data used for other purposes. Use disklabel -e to edit a partition type definition. The following display shows a typical partition layout as shown by disklabel(8): 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a:81920 3440644.2BSD0 0 0 # (Cyl. 240*- 297*) b: 26214481920 swap# (Cyl. 57*- 240*) c: 42267250unused0 0 # (Cyl.0 - 2955*) e:8192004.2BSD0 0 0 # (Cyl.0 - 57*) f: 190 4259844.2BSD0 0 0 # (Cyl. 297*- 1626*) g: 1900741 2325984 vinum0 0 0 # (Cyl. 1626*- 2955*) In this example, partition ``g'' may be used as a vinum partition. Par- titions ``a'', ``e'' and ``f'' may be used as UFS file systems or ccd partitions. Partition ``b'' is a swap partition, and partition ``c'' represents the whole disk and should not be used for any other purpose. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
RE: vinum concatenated raid setup problems - SOLVED
Mike, Thanks for the pointers on the fstab file, they solved that part of the puzzle. (and trying to help with the other issues) Greg, Thanks for pointing me to the right part of the vinum manpage...it was indeed the simple fact that I was trying to build the configuration on disk's rather than partitions that was sabotaging the mission! A little about me and FreeBSD, I am the (volunteer) director of a youth center, The Beatbox (http://www.thebeatbox.org), in Fairfield Iowa, USA and am new to FreeBSD, I am working to switch the network infrastructure entirely to FreeBSD over the next couple months. We currently host 50+ websites for users and have 20+ workstations as well as 6 network server for internal and external purposes. Although I hope that I don't have to bother everyone on the list too much in the coming months, it is certianly enjoyable to be part of this wonderful FreeBSD community. I will do my best to represent this great operating system and all the great people who make it happen. Thanks again for your time and help. Roland Wells Director The Beatbox http://www.thebeatbox.org FTEC http://www.fftechcenter.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: vinum concatenated raid setup problems - SOLVED
I see this has been solved, but i'll throw one more gotcha to watch for out there. Use of 'vinum saveconfig' is a good thing. From the vinum man page: saveconfig Save the current configuration to disk. Normally this is not necessary, since vinum automatically saves any change in configu- ration. If an error occurs on startup, updates will be disabled. When you reenable them with the setdaemon command, vinum does not automatically save the configuration to disk. Use this command to save the configuration. As I was learning to use vinum I made frequent mistakes, disabling updates, then built the system, rebooted, and nothing survived ;) Had to rtfm a couple of times before I caught that. Alvin Mike, Thanks for the pointers on the fstab file, they solved that part of the puzzle. (and trying to help with the other issues) Greg, Thanks for pointing me to the right part of the vinum manpage...it was indeed the simple fact that I was trying to build the configuration on disk's rather than partitions that was sabotaging the mission! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vinum concatenated raid setup problems
Hello all, I have been trying without success to implement a simple vinum concatenated RAID system made up of 2 IDE drives. The boot drive is located on another physical drive and is not part of the RAID. The problems: 1 - I am able to build the RAID, create a filesystem, and mount to a directory in the tree. But I am not able to figure out how to add an entry to my /etc/fstab file so that it is automatically mounted on reboot. I have looked in the handbook and all it says is to add the proper entries. I simple do not know what entry to add. 2 - On reboot, the vinum config is erased. (or at least thats what it looks like...see dmesg output for info) It is my understanding that on reboot, vinum reads it's configuration from each vinum drive. Since I was able to create and mount the RAID, I assume that the configuration would still be there on reboot, even thought it is not being mounted with fstab (see problem 1). I have tried this on several systems and have yet to be successful in having a vinum config survive reboot. I have re-read and re-read the vinum section in the handbook and have looked elsewhere but have had no luck :( Relevent Info: I have not made any changes to system or vinum sources. The system is a generic 5.1 installed from FTP today. From the box: VINUM STATE BEFORE REBOOT ## vinum - l 2 drives: D a State: up /dev/ad2A: 981/28629 MB (3%) D b State: up /dev/ad3A: 981/28629 MB (3%) 1 volumes: V core State: up Plexes: 2 Size: 27 GB 2 plexes: P core.p0 C State: up Subdisks: 1 Size: 27 GB P core.p1 C State: up Subdisks: 1 Size: 27 GB 2 subdisks: S core.p0.s0State: up D: aSize: 27 GB S core.p1.s0State: up D: bSize: 27 GB #VINUM STATE AFTER REBOOT ## vinum - l 0 drives: 0 volumes: 0 plexes: 0 subdisks: #VINUM CONFIG FILE## thegibsor# cat vinum_config drive a device /dev/ad2 drive b device /dev/ad3 volume core plex org concat sd length 27g drive a plex org concat sd length 27g drive b RELEVANT DMESG BEFORE REBOOT ad0: 28629MB QUANTUM FIREBALLlct20 30 [58168/16/63] at ata0-master UDMA100 ad2: 28629MB QUANTUM FIREBALLlct20 30 [58168/16/63] at ata1-master UDMA100 ad3: 28629MB QUANTUM FIREBALLlct20 30 [58168/16/63] at ata1-slave UDMA100 acd0: CDROM LTN486S at ata0-slave PIO4 Mounting root from ufs:/dev/ad0s1a vinum: drive a is up vinum: drive b is up vinum: core.p0.s0 is up vinum: core.p0 is up vinum: core is up vinum: core.p1 is faulty vinum: core.p1.s0 is reviving, not up vinum: core.p1.s0 is up by force vinum: core.p1 is up vinum: core.p1.s0 is up RELEVANT DMESG AFTER REBOOT# ad0: 28629MB QUANTUM FIREBALLlct20 30 [58168/16/63] at ata0-master UDMA100 ad2: 28629MB QUANTUM FIREBALLlct20 30 [58168/16/63] at ata1-master UDMA100 ad3: 28629MB QUANTUM FIREBALLlct20 30 [58168/16/63] at ata1-slave UDMA100 acd0: CDROM LTN486S at ata0-slave PIO4 Mounting root from ufs:/dev/ad0s1a ###UNAME OUTPUT# $ uname -a FreeBSD thegibsor.thebeatbox.org 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Jun 5 02:55:42 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i3 86 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum concatenated raid setup problems
The problems: 1 - I am able to build the RAID, create a filesystem, and mount to a directory in the tree. But I am not able to figure out how to add an entry to my /etc/fstab file so that it is automatically mounted on reboot. I have looked in the handbook and all it says is to add the proper entries. I simple do not know what entry to add. Should be something like: /dev/vinum/yourvolume /mountpoint ufs rw 1 2 2 - On reboot, the vinum config is erased. (or at least thats what it looks like...see dmesg output for info) It is my understanding that on reboot, vinum reads it's configuration from each vinum drive. Since I was able to create and mount the RAID, I assume that the configuration would still be there on reboot, even thought it is not being mounted with fstab (see problem 1). I have tried this on several systems and have yet to be successful in having a vinum config survive reboot. I have re-read and re-read the vinum section in the handbook and have looked elsewhere but have had no luck :( Have you tried 'start_vinum=YES' in /etc/rc.conf? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum concatenated raid setup problems
start_vinum=YES is already in the /etc/rc.conf...see below: --- thegibsor# cat /etc/rc.conf # -- sysinstall generated deltas -- # Sun Oct 19 20:37:29 2003 # Created: Sun Oct 19 20:37:29 2003 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=thegibsor.thebeatbox.org sshd_enable=YES usbd_enable=NO start_vinum=YES # set to YES to start vinum Doh! My faux pas. I'm reading up a bit, but this one may be best left to Greg. Have you verified that the vinum module has loaded after boot? One other thing I just noticed, you didn't use setupstate in the volume line of your config file...did you do an init on the second plex/subdisk before you newfs'd and mounted the volume? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
