vinum crashed disk error

[Greg 'groggy' Lehey]

On Tuesday, 23 September 2003 at 11:21:49 -0700, John Fox wrote:
> Hello,
>
> Three IDE drives multiplexed together to make one large "partition"
> (for mounting as /usr/local).
>
> We were messing with hardware in the box and when we rebooted
> vinum spat out errors about defective objects and the boot
> came to a halt.  We figured we had left something loose or
> unplugged on the motherboard, so we shut it down and took
> a look.  Sure enough, the plug in the mobo's secondary IDE
> channel was loose, so we reseated it and powered the machine
> up again.
>
> We saw that the kernel found all the IDE drives and figured
> the problem was over.  But vinum had the same problem.  It
> said (loose quotation): "/dev/ mounted read-only.  vinum config
> not being rebuilt".  And then spit out the same errors it had
> the first time.

These messages have a purpose.  You shouldn't just ignore them.

> Unfortunately, the vinum.org domain is having problems of some sort,

What sort?  More error messages?  I have no problem accessing it (and
no, it's not here, it's at the other end of the world).

> and the vinum help pages on lemis.com are redirected to the
> vinum.org site,

They're on the same server.

> so I am deprived of a great trouble-shooting resource.

There are still the man pages.

> output of 'vinum start':
> ----------------------------------------------------------------------------
> Warning: defective objects
>
> V bigdisk               State: down		Plexes:       1	Size:         23 GB
> P big_plex            C State: faulty		Subdisks:     3	Size:         23 GB
> S drive0                State: down		PO:        0  B Size:       8063 MB
> S drive2                State: crashed	PO:     8063 MB Size:       8063 MB
> S drive3                State: crashed	PO:       15 GB Size:       8063 MB
> ----------------------------------------------------------------------------

> Any suggestions as to fixing this problem would be greatly
> appreciated, as we do make production use of this box.

Do these objects have any relationship to each other?  The naming is
confusing to say the least.  In general, though, if your drives are up
again, and the volume only has one plex, you can use the 'vinum
setupstate' command to explicitly set the state to up.  You'll then
need to save the configuration with saveconfig after you've confirmed
that the data is OK.

Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20030924/c950d8f1/attachment.bin