Prepare the disks:
Done:
# disklabel /dev/ad4s1
# /dev/ad4s1:
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
a: 398283401 16unused0 0
c: 3982834170unused0 0 # raw part,
don't edit
# disklabel /dev/ad4s1
#
On 6/20/06, Travis H. [EMAIL PROTECTED] wrote:
It was there last time... what happened?
My mistake. In fooling around with it I had set the state to
something invalid, and I thought that loader.conf went in /etc, not
/boot. I used rm on everything, saved, created via a config file,
and now
On Tue, Jun 13, 2006 at 09:31:22AM -0500, Travis H. wrote:
I put
start_vinum=YES
start_gvinum=YES
in /etc/rc.conf, per the handbook, and it doesn't appear that there
are any startup files for it, which means my filesystems won't boot.
Is there any code I can download to do this, or
I also put these in /etc/loader.conf:
vinum.autostart=YES
gvinum.autostart=YES
Per the handbook. Neither seems to work.
Now I can't seem to get the disks started, and /dev/gvinum doesn't
exist, so I can't access my data. Can someone lend me a hand here?
The state of [g]vinum is completely
On 6/13/06, Peter A. Giessel [EMAIL PROTECTED] wrote:
#1) Do NOT attempt to use both vinum and gvinum at the same time. They
conflict with each other.
vinum doesn't exist in my fbsd distro.
#2) You don't say which version of FreeBSD you are using. (It matters
for which one [vinum/gvinum]
