Hi Henning,
Am Mittwoch, 9. Februar 2005 11:16 schrieb Henning
Kropp:> [...]
> The result I at boot time is a screen continuously printing out:
> GEOM_VINUM: plex request failed for gvinum/plex/myvolume.p
>
> Does anybody know where to start from here?
There are some points to check:
a) Is this a RAID-5 Volume under 5.3-RELEASE? -> Upgrade to 5-STABLE!
gvinum RAID-5 is known *not* to work under 5.3-RELEASE. The error was
fixed during the freeze of the source tree for 5.3-RELEASE, so it was
committed shortly ( 1 week or so) *after* the release was built.
b) Check your vinum partitions with bsdlabel.
In your case:
bsdlabel /dev/ad0s1e
bsdlabel /dev/ad1s1d
bsdlabel /dev/ad2s1d
Check if any of the vinum-type partitions have an offset of "0"
(zero).
Partitions with an offset of "0" are known *not* to work with
GEOM_vinum. I consider this a feature and not a bug, because with
gvinum you can use whole disks or slices without the need of BSD- or
DOS-partitiontables. The back side of this is, that gvimum *must* be
able to distinguish a BSD-Partition from a DOS-Slice, which is not the
case if the BSD-Partition has an offset of "0". The partition type is
not evaluated by gvinum at all, because it doesn't need one.
If that's the case, you're in trouble. Suck the data on tape and rebuild
your volume with gvinum on partitions with an offset of "16" (the
default).
I had all these problems during my migration to gvinum but no more...
...but im using SCSI-Disks only, so the whole ATA-Stuff is possibly a
further source of trouble. Any errors from this direction? All disk are
masters? Parralel- or S-ATA?
Besides: You *can* use classic-vinum under FreeBSD-5 if you hold vinum
until the system has come up and the main partitions are mounted.
If all these points don't leed to an solution, perhaps contact Lukas
Ertl (le@freebsd.org) directly, which is the maintainer of gvinum...
--
Ciao/BSD - Matthias
Matthias Schuendehuette <msch [at] snafu.de>, Berlin (Germany)
PGP-Key at <pgp.mit.edu> and <wwwkeys.de.pgp.net> ID: 0xDDFB0A5F