Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Jun 2002 09:15:22 +0930
From:      Greg 'groggy' Lehey <grog@FreeBSD.org>
To:        Chris Bolt <chris-lists@bolt.cx>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: vinum problems
Message-ID:  <20020619234522.GI29978@wantadilla.lemis.com>
In-Reply-To: <3D1051FA.8030400@bolt.cx>
References:  <3D1051FA.8030400@bolt.cx>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 19 June 2002 at  3:42:18 -0600, Chris Bolt wrote:
> I've been having nothing but problems with vinum ever since a disk died
> two days after getting a RAID 5 array online. When I try vinum start, I
> get the following:
>
> root@warhol:/home/chris# vinum start
> *** Warning: configuration updates are disabled. ***
> Warning: defective objects
>
> D d2               State: referenced       Device  Avail: 0/0 MB
> P raid5.p0      R5 State: degraded Subdisks:     2 Size:       55 GB
> S raid5.p0.s0      State: empty    PO:        0  B Size:       55 GB
> S raid5.p0.s1      State: crashed  PO:        0  B Size:       55 GB
> S raid5.p0.s2      State: empty    PO:     1024 kB Size:       55 GB
> *** Warning: configuration updates are disabled. ***
>
> I don't get a warm fuzzy feeling when I see "empty" on my definitely not
> empty RAID array. So let's try a list:

That's what you just had.

> What the? How do I fix d2?

Is it there?  Does dmesg see it?

> Keep in mind configuration updates are disabled, so I can't really
> change anything...

Read the manual.  You can issue a saveconfig.  But you don't want to yet.

> And at one point, dumpconfig gave me the following, but I'm too scared
> to reproduce it:
>
> vinum -> dumpconfig
> Drive d1:       Device /dev/ad1s1e
>                 Created on warhol.deviantart.com at Tue Jun  4 23:13:18
> 2002
>                 Config last updated Wed Jun 14 18:20:35 2000
>                 Size:      60019835904 bytes (57239 MB)
> volume raid5 state down
> plex name raid5.p0 state down org raid5 1024s vol raid5
> sd name raid5.p0.s0 drive d1 plex raid5.p0 len 117225472s driveoffset
> 265s state empty plexoffset 0s
> sd name raid5.p0.s1 drive d2 plex ò²u!±ðððÔÁüòÀðвðò°0ñðððàô
> h`ñÆòòð0°ðàòòÄÞpøÜðòð
> ²°âò`ðä xðùôäàú´ðñq°ðbô´Ððüpðèôðpòиøqàüè ôðñÈ0TððåyðpØôðpôÐòppñ°°rpðÐÈ
> ðõòàðð±pôqðÒqðùôðòøøøôèðÐPðøððqòØÉÕøðñø°|ðð0°ö°à¨ÚrXðÐðòÐ ðö2ðàØÙôðàØô°
> ±òsðó6øtxðôð40ðqraid5.p0 len 117225472s driveoffset
> 18446744073709551615s state crashed detached
> sd name raid5.p0.s2 drive d3 plex raid5.p0 len 117225472s driveoffset
> 265s state empty plexoffset 2048s

Please don't wrap computer output.  It changes the meaning.  There's
no reason to be afraid of this, though it looks strange.

> Any ideas?

Yes.  They're at http://www.vinumvm.org/vinum/how-to-debug.html and in
the man pages.

Greg
--
See complete headers for address and phone numbers

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020619234522.GI29978>