vinum volume manager

[Tomas Palfi]

Hi All,

I have used the following message as a template, I have exactly the same
problem with vinum, and wonder if someone knows the solution to it. 

-----------------------------------------------------------------------
 
I've been trying to get a bootstrapped vinum volume up and running on a
5.4
release system (generic kernel, minimal install), based this How-to:
http://devel.reinikainen.net/docs/how-to/Vinum/
But I've managed to run into a problem that no amount of Googling,
reading
the archive of this list, or reading the manual seems help me get by.
Basically, I have Vinum configured fine and can successfully run:
 
vinum > create -f /etc/vinum.conf
 
The Vinum volume is all fine and a vinum > list shows no problems.  I
can
also successfully do a fsck on each of the mounts.
 
However, it appears that the vinum config isn't being saved, as
rebooting
the machine can't find the vinum root partition, and after manually
booting
to the pre-vinum root (ufs:ad0s1a) running vinum > list shows no volume
information.
 
During the reboot, vinum appears to load ok, but it can't find the root
(as
shown by the last bit of the dmesg):
 
vinum: loaded
vinum: no drives found
Mounting root from ufs:/dev/vinum/root
setrootbyname failed
ffs_mountroot: can't find rootvp
Root mount failed: 6
 
The relevant config files look like this:
 
/etc/fstab
 
/boot/loader.conf
 
vinum_load="YES"
vinum.autostart="YES"

----------------------------

I know that David Kelly attempted to rectify the problem gvinum,
however, does the problem still persists with vinum?
 
Many thanks

Tomas

--
tp





PRIVACY & CONFIDENTIALITY

This e-mail is private and confidential.  If you have, or suspect you have received this message in error please notify the sender as soon as possible and remove from your system.  You may not copy, distribute or take any action in reliance on it. Thank you for your co-operation.

Please note that whilst best efforts are made, neither the company nor the sender accepts any responsibility for viruses and it is your responsibility to scan the email and attachments (if any).

This e-mail has been automatically scanned for viruses by MessageLabs.