Date: Thu, 23 Oct 2003 23:10:01 -0500 From: "RWELLS@THEBEATBOX.ORG" <rwells@thebeatbox.org> To: <freebsd-questions@freebsd.org> Subject: vinum concatenated raid setup problems Message-ID: <PDEILHPKMOIPFPKCGAPBKEGHCMAA.rwells@thebeatbox.org>
next in thread | raw e-mail | index | archive | help
Hello all,
I have been trying without success to implement a simple vinum
concatenated RAID system made up of 2 IDE drives. The boot drive is
located on another physical drive and is not part of the RAID.
The problems:
1 - I am able to build the RAID, create a filesystem, and mount to a
directory in the tree. But I am not able to figure out how to add an
entry to my /etc/fstab file so that it is automatically mounted on
reboot. I have looked in the handbook and all it says is to "add the
proper entries". I simple do not know what entry to add.
2 - On reboot, the vinum config is erased. (or at least thats what it
looks like...see dmesg output for info) It is my understanding that on
reboot, vinum reads it's configuration from each vinum drive. Since I
was able to create and mount the RAID, I assume that the configuration
would still be there on reboot, even thought it is not being mounted
with fstab (see problem 1). I have tried this on several systems and
have yet to be successful in having a vinum config survive reboot. I
have re-read and re-read the vinum section in the handbook and have
looked elsewhere but have had no luck :(
Relevent Info:
I have not made any changes to system or vinum sources. The system is a
generic 5.1 installed from FTP today.
>From the box:
####VINUM STATE BEFORE REBOOT ######
vinum -> l
2 drives:
D a State: up /dev/ad2 A: 981/28629 MB
(3%)
D b State: up /dev/ad3 A: 981/28629 MB
(3%)
1 volumes:
V core State: up Plexes: 2 Size: 27
GB
2 plexes:
P core.p0 C State: up Subdisks: 1 Size: 27
GB
P core.p1 C State: up Subdisks: 1 Size: 27
GB
2 subdisks:
S core.p0.s0 State: up D: a Size: 27
GB
S core.p1.s0 State: up D: b Size: 27
GB
####################################
#####VINUM STATE AFTER REBOOT ######
vinum -> l
0 drives:
0 volumes:
0 plexes:
0 subdisks:
####################################
#########VINUM CONFIG FILE##########
thegibsor# cat vinum_config
drive a device /dev/ad2
drive b device /dev/ad3
volume core
plex org concat
sd length 27g drive a
plex org concat
sd length 27g drive b
####################################
####RELEVANT DMESG BEFORE REBOOT####
ad0: 28629MB <QUANTUM FIREBALLlct20 30> [58168/16/63] at ata0-master
UDMA100
ad2: 28629MB <QUANTUM FIREBALLlct20 30> [58168/16/63] at ata1-master
UDMA100
ad3: 28629MB <QUANTUM FIREBALLlct20 30> [58168/16/63] at ata1-slave
UDMA100
acd0: CDROM <LTN486S> at ata0-slave PIO4
Mounting root from ufs:/dev/ad0s1a
vinum: drive a is up
vinum: drive b is up
vinum: core.p0.s0 is up
vinum: core.p0 is up
vinum: core is up
vinum: core.p1 is faulty
vinum: core.p1.s0 is reviving, not up
vinum: core.p1.s0 is up by force
vinum: core.p1 is up
vinum: core.p1.s0 is up
####################################
####RELEVANT DMESG AFTER REBOOT#####
ad0: 28629MB <QUANTUM FIREBALLlct20 30> [58168/16/63] at ata0-master
UDMA100
ad2: 28629MB <QUANTUM FIREBALLlct20 30> [58168/16/63] at ata1-master
UDMA100
ad3: 28629MB <QUANTUM FIREBALLlct20 30> [58168/16/63] at ata1-slave
UDMA100
acd0: CDROM <LTN486S> at ata0-slave PIO4
Mounting root from ufs:/dev/ad0s1a
####################################
###########UNAME OUTPUT#############
$ uname -a
FreeBSD thegibsor.thebeatbox.org 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu
Jun 5
02:55:42 GMT 2003
root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i3
86
####################################
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PDEILHPKMOIPFPKCGAPBKEGHCMAA.rwells>