Date: Fri, 05 Oct 2001 10:02:22 +0200 From: Adi Sieker <adi@living-source.com> To: freebsd-questions@FreeBSD.ORG Subject: Re: recovering a vinum volume Message-ID: <kipqrto006d2birh4m1pv4q0hmcmhaccme@4ax.com> In-Reply-To: <20011005105803.G15533@wantadilla.lemis.com> References: <sdmortskp3q0h5innpfrbq5tuct345jovt@4ax.com> <20011005105803.G15533@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 5 Oct 2001 10:58:03 +0930, Greg Lehey <grog@FreeBSD.org> wrote: >On Thursday, 4 October 2001 at 14:52:28 +0200, Adi Sieker wrote: > >If you can't read the data, you can't read the data. =20 Well obvioulsy. :)) >You can get the objects back sort of "up" with the 'setstate'=20 >maintenence command, but >there's a good chance it'll go down again during fsck. You could try >mounting read only. Well I tried both and 'yes' it goes down again when reading data from the drive. I would be happy to only get half the data back i.e. the data from the working 75GB hard drive. Is there any way to accomplish this?. Like replacing the broken hard drive with a new one and creating a new plex on that or even removing the broken hard drive from the vinum volume to only run the working hard drive? I am asking this stuff before trying anything, because I would like to know what chance I have before trying to change anything on the vinum config and have it totally screw the data on the discs. Thanks Adi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?kipqrto006d2birh4m1pv4q0hmcmhaccme>