Moving vinum drives to a new system?
dkelly at HiWAAY.net
Thu Aug 5 07:28:09 PDT 2004
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
> nodes by doing
> vinum makedev
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 at HiWAAY.net
Whom computers would destroy, they must first drive mad.
More information about the freebsd-questions