Vinum subdisk crash

[Greg 'groggy' Lehey]

[Format recovered--see http://www.lemis.com/email/email-format.html]

Broken wrapping, unclear attribution, incorrect quotation levels.  It
took five minutes of my time fixing this message to a point where I
could reply to it.

On Thursday, 30 June 2005 at 15:37:56 +0200, Gareth Bailey wrote:
> Hello everyone,
>
> Just to add, I had to type out the above message manually since I can't get
> access to anything with the crashed subdisk on /usr.
> With regard to Greg's requests for information when reporting vinum problems
> as stated on vinumvm.org <http://vinumvm.org>'s website, I can provide the
> following info:
>
>> What problems are you having?
>
> My usr.p0.s0 subdisk reports a 'crashed' status
>
>> Supply the output of the *vinum list* command. If you can't start
>> Vinum, supply the on-disk configuration, as described below. If you
>> can't start Vinum, then (and only then) send a copy of the
>> configuration file.
>
> I can't get anything off the system, and its too long to type out!
> (I have the same layout as in the Van Valzah article.)

Would you like a reply like "I have an answer, but it's too long to
type out"?  Do you really expect me to go and re-read Bob's article?
This, along with your hard-to-read message, is a good way to be
ignored.

>> Supply an *extract* of the file */var/log/messages*. Restrict the
>> extract to the same time frame as the history file. Again, each
>> line contains a timestamp at the beginning, so you will have no
>> difficulty in establishing which data is of relevance.
>
> 30 Jun server /kernel: ad0s1h: hard error reading fsbn 59814344 of 29126985-29127080 (ad0s1 bn 59814344; cn 3723 tn 69 sn 2) trying PIO mode
> 30 Jun server /kernel: ad0s1h: hard error reading fsbn 59814344 of 29126985-29127080 (ad0s1 bn 59814344; cn 3723 tn 69 sn 2) status=59 error=40

You have a hardware problem with /dev/ad0.

> 30 Jun server /kernel: vinum: usr.p0.s0 is crashed by force
> 30 Jun server /kernel: vinum: usr.p0 is faulty
> 30 Jun server /kernel: vinum: usr is down

And this suggests that your configuration is  non-resilient.

> I hope this information helps, and that someone can give me some
> advice!

Yes.  Replace the disk.

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
The virus contained in this message was detected by LEMIS anti-virus.

Finger grog at FreeBSD.org for PGP public key.
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/20050701/aa4f1ea1/attachment.bin