From owner-freebsd-questions Thu Jul 16 15:57:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10738 for freebsd-questions-outgoing; Thu, 16 Jul 1998 15:57:02 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from rm-rstar.sfu.ca (root@rm-rstar.sfu.ca [142.58.120.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10731 for ; Thu, 16 Jul 1998 15:57:00 -0700 (PDT) (envelope-from wolstena@sfu.ca) Received: from beaufort.sfu.ca (wolstena@beaufort.sfu.ca [192.168.0.110]) by rm-rstar.sfu.ca (8.8.7/8.8.7/SFU-4.0H) with SMTP id PAA08940 for ; Thu, 16 Jul 1998 15:56:48 -0700 (PDT) From: Paul Wolstenholme Received: by beaufort.sfu.ca (951211.SGI.8.6.12.PATCH1502/SFU-2.7C) id PAA21410 for freebsd-questions@freebsd.org (from wolstena@sfu.ca); Thu, 16 Jul 1998 15:56:47 -0700 Message-Id: <199807162256.PAA21410@beaufort.sfu.ca> Subject: Filesystem recovery nightmare To: freebsd-questions@FreeBSD.ORG Date: Thu, 16 Jul 1998 15:56:47 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I have been having some SCSI problems on a new FreeBSD 2.2.6 box. Not knowing exactly what the problme was I thought I would start from scratch. The thought was that I had a good backup of my data. It know appears that my tape archive may be corrupt. The archive was made via: tar cvfz /dev/nrst0 / However, when I try to restore (eg. tar xvfz /dev/nrst0 /etc) I get the following errors: gzip: stdin: unexpected end of file tar unxexpected EOF on archive file The SCSI error reported in the log is: Jul 16 14:46:34 alpha /kernel: st0(aic0:5:0): timed out Is there any way I can get the data off this tape. I sure would like to get the /etc directory and some of the stuff off /usr/local. Any assistance would be much, much appreciat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message