Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Feb 2004 09:08:27 +1030
From:      Greg 'groggy' Lehey <grog@FreeBSD.org>
To:        Danny Carroll <danny@dannysplace.net>
Cc:        freebsd-questions@FreeBSD.org
Subject:   Re: Help with Vinum disk crash...
Message-ID:  <20040217223827.GM33797@wantadilla.lemis.com>
In-Reply-To: <00ed01c3f559$d7f1ac20$8052260a@capgemini.nl>
References:  <00ed01c3f559$d7f1ac20$8052260a@capgemini.nl>

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

--gB+ITVRz/u3k8hJv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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

Log output wrapped.

On Tuesday, 17 February 2004 at 14:27:51 +0100, Danny Carroll wrote:
> Hello,
>
> About 6 weeks ago one of the disks in my Vinum array crashed.
> However, the major problem is now that the file system is corrupt.  It
> appears I have lost all of my 300Gb virtual disk...
>
> This is what I found in the message log.
>
> Jan  2 04:13:07 guard /kernel: ad4s1a: hard error reading fsbn 317875665 of 150983369-150983370 (ad4s1 bn 317875665; cn 19786 tn 215 sn 30) trying PIO mode
> Jan  2 04:13:08 guard /kernel: ad4s1a: hard error reading fsbn 317875665 of 150983369-150983370 (ad4s1 bn 317875665; cn 19786 tn 215 sn 30) status=59 error=40
> Jan  2 04:13:08 guard /kernel: vinum: data.p0.s0 is crashed by force
> Jan  2 04:13:08 guard /kernel: vinum: data.p0 is degraded
> Jan  2 04:13:08 guard /kernel: fatal:data.p0.s0 read error, block 150983369 for 1024 bytes
> Jan  2 04:13:08 guard /kernel: data.p0.s0: user buffer block 452942752 for 1024 bytes
> Jan  2 04:13:09 guard /kernel: vinum: data.p0.s0 is stale by force
>
> I had not had time to look at this till now....
>
> When I do try and mount the volume, it says the following:
>
> [02:25 PM root@guard:/var/log]#mount /dev/vinum/data /usr/jails/ftp/data
> mount: /dev/vinum/data on /usr/jails/ftp/data: incorrect super block
>
> I suspect that the physical disk is dead, but I should be able to re-mount
> the volume with only 3 (out of 4 ) disks right?

I answered an almost identical question yesterday: it depends on the
volume structure, which you haven't stated.  Look at
http://www.vinumvm.org/vinum/how-to-debug.html and supply in
particular the output of 'vinum list', unless the following applies:

If this volume has only one plex, you're lost, unless you can bring up
the failed disk long enough to make a backup.

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.

--gB+ITVRz/u3k8hJv
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAMpfjIubykFB6QiMRAilqAJ9iuuyhSQf69SFr+48VoSuJSBtY+gCfXrj8
ycUF+ZgML/cHy0XHKq5vThc=
=WSfU
-----END PGP SIGNATURE-----

--gB+ITVRz/u3k8hJv--



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