From owner-freebsd-questions Fri Oct 5 2:53:51 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.living-source.com (sgw-fr.living-source.com [212.2.36.144]) by hub.freebsd.org (Postfix) with SMTP id 8F05E37B403 for ; Fri, 5 Oct 2001 02:53:47 -0700 (PDT) Received: (qmail 10709 invoked by uid 0); 5 Oct 2001 09:53:56 -0000 Received: from shaman.fr.living-source (192.168.0.25) by mail.living-source.com with SMTP; 5 Oct 2001 09:53:56 -0000 From: Adi Sieker To: freebsd-questions@FreeBSD.ORG Subject: Re: recovering a vinum volume Date: Fri, 05 Oct 2001 11:54:27 +0200 Organization: living source GmbH Reply-To: adi@living-source.com Message-ID: References: <20011005105803.G15533@wantadilla.lemis.com> <20011005180438.I19977@wantadilla.lemis.com> In-Reply-To: <20011005180438.I19977@wantadilla.lemis.com> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Greg, On Fri, 5 Oct 2001 18:04:38 +0930, Greg Lehey wrote: >On Friday, 5 October 2001 at 10:02:22 +0200, Adi Sieker wrote: >> >> Well I tried both and 'yes' it goes down again when reading data from >> the drive. > >*sigh* > >> 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?. > >Well, getting the data off is simple. Just dd from the surviving >subdisk. There won't be much you can do with it, though, especially >if the plex was striped. > hehe, doesn't really help much... >You could try some of these methods; I'd certainly recommend backing >up the accessible subdisk before trying anything. It's possible that >you can use fsck with an alternate superblock to recover something, >but if the first half is gone, the best you can hope for is a maze of >twisty little lost+found files, all different. Well I after some playing around the broken disc barfs only when reading certain files. Well, at least on a ls -lR it does. So my thinking is going in the following direction: Write a script that trys to read in all the filenames and yop the file to /tmp or whatever. When the read or copy fails remember the position of the file. unmount the volume set the state of the vinum volume to uo again remount the partition and start all over again leaving out the file which made the volume barf. And so on and so on. Once I have made my way through all files I have a list of OK files which I can then copy over on to a new hard drive. Assuming that mount the volumen read-only doesn't break anything else and the harddrive doesn't get more damaged. Thanks Adi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message