Date: Fri, 24 Oct 2003 12:47:52 -0400 (EDT) From: "Alvin Gunkel" <gunkel@oneofum.net> To: "Roland Wells" <freebsd@thebeatbox.org> Cc: freebsd-questions@freebsd.org Subject: RE: vinum concatenated raid setup problems - SOLVED Message-ID: <41018.198.151.13.15.1067014072.squirrel@mail.oneofum.net> In-Reply-To: <PDEILHPKMOIPFPKCGAPBOEGMCMAA.freebsd@thebeatbox.org> References: <20031024073656.GR6073@wantadilla.lemis.com> <PDEILHPKMOIPFPKCGAPBOEGMCMAA.freebsd@thebeatbox.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41018.198.151.13.15.1067014072.squirrel>