Date: Thu, 5 Aug 2004 09:28:03 -0500 From: David Kelly <dkelly@HiWAAY.net> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Moving vinum drives to a new system? Message-ID: <A8D2C47A-E6EB-11D8-A889-000393BB56F2@HiWAAY.net> In-Reply-To: <20040805055427.GG43462@pcwin002.win.tue.nl> References: <26ADC4B8-E691-11D8-9283-000393BB56F2@HiWAAY.net> <20040805055427.GG43462@pcwin002.win.tue.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 5, 2004, at 12:54 AM, Stijn Hoop wrote: >> # vinum list >> 2 drives: >> D vinumdrive1 State: up /dev/ad6s1d A: 156041/156041 MB (100%) >> D vinumdrive0 State: up /dev/ad4s1d A: 156041/156041 MB (100%) >> >> 0 volumes: >> 0 plexes: >> 0 subdisks: >> # > > How early in the boot is this? Have you done 'vinum start' yet? System is multiuser. "vinum start" has already been executed which was required to run "vinum list" shown above. vinum.ko is/was loaded. > If that doesn't work, does 'vinum read vinumdrive0 vinumdrive1' work? No. Vinum replies: ** no additional drives found: No such file or directory Can't save Vinum config: No such file or directory > before vinum can create devices. You can force vinum to recreate the > device > nodes by doing > > vinum makedev Vinum replies: makedev is not needed for a DEVFS-based system Am tempted to rerun "stripe -v /dev/ad4s1d /dev/ad6s1d" again but would rather not lose the data on the volume. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A8D2C47A-E6EB-11D8-A889-000393BB56F2>