From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 5 00:34:01 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78C6B16A4CE; Tue, 5 Oct 2004 00:34:01 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 576B243D41; Tue, 5 Oct 2004 00:34:01 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (8.12.6/MantshX 2.0) with ESMTP id i950Y05D017324; Mon, 4 Oct 2004 17:34:00 -0700 (PDT) Received: from [192.168.1.6] (pool-68-160-246-51.ny325.east.verizon.net [68.160.246.51]) (authenticated bits=0)i950XwGe009866; Mon, 4 Oct 2004 17:33:59 -0700 (PDT) In-Reply-To: <4161DEAB.8070803@pythonemproject.com> References: <20041004112027.GA1692@dyn202-hg.nbw.tue.nl> <4161DEAB.8070803@pythonemproject.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <3E8556EA-1666-11D9-B1D0-003065A20588@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Mon, 4 Oct 2004 20:33:57 -0400 To: Rob X-Mailer: Apple Mail (2.619) cc: questions@freebsd.org cc: freebsd-hardware@freebsd.org Subject: Re: harddisk dying? / How do I fix superblock on SCSI drive? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Oct 2004 00:34:01 -0000 On Oct 4, 2004, at 7:37 PM, Rob wrote: > Your post may be timely for me. How do you copy an alternate > superblock on a SCSI hard drive to replace the main superblock? > Mine got corrupted. I did this routine once before on an IDE drive > and it worked great. But on SCSI, I understand less of how the drive > works, so I don't know whether to use fsck or camcontrol or what. You can feed fsck the -b 32 (or some other superblock) option to clean the filesystem using an alternate superblock. If possible, you want to try to do a SCSI "REASsign Block" command ("reasb") to use any available spare sectors to replace the bad one. It's possible that one of the following might be helpful: /usr/ports/sysutils/sformat /usr/ports/sysutils/smartmontools I suggest running a long self-test and checking the SMART status on the drive. Modern drives are supposed to reassign bad blocks themselves, so it is quite possible that your drive has already used up all of its spare sectors and is going to fail completely very soon. -- -Chuck