Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 31 May 2003 12:28:08 +0930
From:      Greg 'groggy' Lehey <grog@FreeBSD.org>
To:        "Michael G. Jung" <mikej@confluenttech.com>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: Vinum / 4.8 / Referenced disk / Recovery
Message-ID:  <20030531025808.GF56538@wantadilla.lemis.com>
In-Reply-To: <9D7F0DF3FB16D41184010050DA90E000BF6668@neo.confluentasp.local>
References:  <9D7F0DF3FB16D41184010050DA90E000BF6668@neo.confluentasp.local>

next in thread | previous in thread | raw e-mail | index | archive | help

--Y/WcH0a6A93yCHGr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Friday, 30 May 2003 at 18:21:53 -0400, Michael G. Jung wrote:
> After a reboot on 4.8 I ended up with a degraded raid 5 partition...
>
> The only thing special about my setup is.... 4944 drives spread over 3 ch=
annels,
> running SMP kernel.....

That's a lot of drives.

> One sub disk was down and the and the drive was referenced... in scouring=
 the
>  mailing lists I saw where a referenced disk means you have referenced a
>  non-existent drive - I read this as one  vinum didn't think was defined.=
. in my
> case it was drive29  --> /dev/da29s1e
>
> I don't know how this got referenced !!! =20

It's part of your configuration.  From the printconfig output:

> drive drive29 device /dev/da29s1e

> It's been reboot many times and this has not happened.

It probably hasn't failed for.

>
> So I boldly created a config file for vinum and re-created the drive.....
>
> --- config file ----
> drive drvie29 device /dev/da29e
> --- end ----
>
> but I still can not start the sub disk.....
>
> (root@jammin) /home/staff/mikej# vinum start raid5-1.p0.s15
> Can't start raid5-1.p0.s15: Drive is down (5)
> (root@jammin) /home/staff/mikej#
>
> Here is what vinum thinks...... Do I rm the sub disk and re-create
> it?????

No.

> Will this kill my raid-5 partition ??

If you do enough messing around with the configuration, yes, you can
kill your RAID-5 plex.

In all probability, your drive has failed and requires replacement.
You'll see that from the system log file.  Look at
http://www.vinumvm.org/vinum/how-to-debug.html and
http://www.vinumvm.org/vinum/replacing-drive.html.  You don't need to
submit the information if you can understand it and take the
appropriate action.

Greg
--
See complete headers for address and phone numbers

--Y/WcH0a6A93yCHGr
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (FreeBSD)

iD8DBQE+2BpAIubykFB6QiMRAlL4AJ949n0b6TrzdH6hkgRyM8wqe869vgCfc4J1
1swXGq5SQ8oM+ERS3K7x0ZQ=
=JeV9
-----END PGP SIGNATURE-----

--Y/WcH0a6A93yCHGr--


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