Re: vinum software raid as boot drive
On Sep 20, 2004, at 8:52 PM, Greg 'groggy' Lehey wrote: We could not find stated exactly anywhere, but we are presuming the description file that you use with vinum create becomes /etc/vinum.conf Well, you need to call it that. The name isn't critical, but it's a good choice. I use vinum only for a data volume. I've seen /etc/vinum.conf mentioned in the handbook and other documentation but didn't understand its use. Was under the impression that recent vinum stored this information in the headers on the drives? That it found its drives by reading the volume types off BSD partitions. Vinum in 5.2.1 often fails to remember its configuration on boot. But sometimes remembers on a cold boot. Would vinum printconfig /etc/vinum.conf help? When we execute vinum create it appears to work fine. The Devices are created in /dev/vinum/ and we can do a fsck -n -t ufs /dev/vinum/root which outputs no errors The problem is when we reboot the devices in /dev/vinum are destroyed ( presume this is normal behaviour ) but they are not created on boot. Take a look at http://www.vinumvm.org/vinum/how-to-debug.html. It might help; otherwise supply the information asked for there. This is a problem I too have been having since 5.2.1, which was the first time I used vinum. Was only out of desperation, Its broken, everything is lost, did something wrong, lets start over that I re-ran vinum stripe -v /dev/ad4s1d /dev/ad6s1d and then on a lark rather than newfs I ran fsck and found my /dev/vinum/vinum0 intact! Sometimes vinum finds its configuration and boots. Then something changed and vinum behaved on 3 boots in a row. Had composed a lengthy email in answer to Greg's debugging checklist above. Was tricked into deleting it unsent. I think Beastie's last name might be Murphy. Upgraded to 5.3-BETA and developed a new problem: vinum causes a kernel panic when started from the rc scripts. http://www.freebsd.org/cgi/query-pr.cgi?pr=71824 I suspect the issues are related because I always lose vinum configuration after a panic, but usually do not if I let the mount fail during boot (for lack of vinum_start=YES in /etc/rc.conf) and drop me into single user. Then vinum start and exit typed manually usually brings the system up. Drops me into single user again if vinum lost its configuration. -- David Kelly N4HHE, [EMAIL PROTECTED] Whom computers would destroy, they must first drive mad. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum software raid as boot drive
On Tuesday, 21 September 2004 at 8:24:44 -0500, David Kelly wrote: On Sep 20, 2004, at 8:52 PM, Greg 'groggy' Lehey wrote: We could not find stated exactly anywhere, but we are presuming the description file that you use with vinum create becomes /etc/vinum.conf Well, you need to call it that. The name isn't critical, but it's a good choice. I use vinum only for a data volume. I've seen /etc/vinum.conf mentioned in the handbook and other documentation but didn't understand its use. Was under the impression that recent vinum stored this information in the headers on the drives? That it found its drives by reading the volume types off BSD partitions. Yes, that's correct. But when setting up Vinum, you need to create a configuration file. Vinum in 5.2.1 often fails to remember its configuration on boot. You're reporting that. But sometimes remembers on a cold boot. Would vinum printconfig /etc/vinum.conf help? No. That would destroy your configuration file. You could save it elsewhere. But it would be better to find out why it's not working. Note that Vinum under 5.2.1 is in transition to a rewrite. I can't help you with the new version Sometimes vinum finds its configuration and boots. Then something changed and vinum behaved on 3 boots in a row. Had composed a lengthy email in answer to Greg's debugging checklist above. Was tricked into deleting it unsent. This won't help find your problem. I suspect the issues are related because I always lose vinum configuration after a panic, Until proof of the contrary, don't make this assumption. 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. pgpnELEuBJuhz.pgp Description: PGP signature
vinum software raid as boot drive
We are currently trying to set up server with software raid using vinum on 5.3. We plan to use it as a Mirrored root filesystem So far we have followed Greg Lehey's instructions from http://www.daemonnews.org/22/vinum.html and the handbook on vinum: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-root.html note we are only using a single / partition. output of bsdlabel: #size offsetfstype [fsize bsize bps/cpg] a: 141315997 20480004.2BSD 2048 16384 28552 b: 2047719 281 swap c: 1433639970unused0 0 # raw part, don't edit h: 143363981 16 vinum vinum Description File drive rootdev device /dev/da0s1h volume root plex org concat sd len 141315997s driveoffset 2047984s drive rootdev volume swap plex org concat sd len 2047719s driveoffset 265s drive rootdev We could not find stated exactly anywhere, but we are presuming the description file that you use with vinum create becomes /etc/vinum.conf When we execute vinum create it appears to work fine. The Devices are created in /dev/vinum/ and we can do a fsck -n -t ufs /dev/vinum/root which outputs no errors The problem is when we reboot the devices in /dev/vinum are destroyed ( presume this is normal behaviour ) but they are not created on boot. /boot/loader.conf vinum_load=YES vinum.autostart=YES Have also tried /boot/loader.conf with: vinum_load=YES vinum.autostart=YES vinum_root=root vinum_drives=/dev/da0s1h both with exactly the same result. When booting we get the message vinum: loaded vinum: no drives found any help much appreciated. please cc me in replies. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum software raid as boot drive
On Tuesday, 21 September 2004 at 9:13:23 +1200, Bruce Harding wrote: We are currently trying to set up server with software raid using vinum on 5.3. We plan to use it as a Mirrored root filesystem So far we have followed Greg Lehey's instructions from http://www.daemonnews.org/22/vinum.html and the handbook on vinum: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-root.html note we are only using a single / partition. ... We could not find stated exactly anywhere, but we are presuming the description file that you use with vinum create becomes /etc/vinum.conf Well, you need to call it that. The name isn't critical, but it's a good choice. When we execute vinum create it appears to work fine. The Devices are created in /dev/vinum/ and we can do a fsck -n -t ufs /dev/vinum/root which outputs no errors The problem is when we reboot the devices in /dev/vinum are destroyed ( presume this is normal behaviour ) but they are not created on boot. Take a look at http://www.vinumvm.org/vinum/how-to-debug.html. It might help; otherwise supply the information asked for there. 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. pgpKQBjXUSjh4.pgp Description: PGP signature
