From owner-freebsd-hackers@FreeBSD.ORG Sat Oct 9 00:19:20 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4EDF616A4CE for ; Sat, 9 Oct 2004 00:19:20 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id C97C743D49 for ; Sat, 9 Oct 2004 00:19:19 +0000 (GMT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net ([141.153.249.79]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041009001918.ZKNL24594.out001.verizon.net@bellatlantic.net>; Fri, 8 Oct 2004 19:19:18 -0500 Sender: root@FreeBSD.ORG Message-ID: <41672E84.9DE09887@bellatlantic.net> Date: Fri, 08 Oct 2004 20:19:16 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.7-RELEASE i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Doug Russell References: <20041007204943.S27627-100000@mxb.saturn-tech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [141.153.249.79] at Fri, 8 Oct 2004 19:19:17 -0500 cc: freebsd-hackers@freebsd.org cc: John Von Essen Subject: Re: hacking SCO.... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Oct 2004 00:19:20 -0000 Doug Russell wrote: > > On Thu, 7 Oct 2004, John Von Essen wrote: > > > Well, I eventually got this SCO system working. But today, some errors > > appeared: > > > > 505k:unrecover error reading SCSI disk on 0 Dev - 1/42 > > cha = 0 id = 0 1 on = 0 > > Block 6578 > > medium error unrecovered read error > > HTFS i/o failure occurred while trying to upgrade 1 node 26302 on > > HTFS. Dev hd 1/42 > > Error log over flow block 6578 medium error unrecovered read error . > > > > Do these sound likes hardware errors for the drive or the adaptec card > > Drive errors. > Did you do a new low-level format before you put it in service? > > sformat is your friend. Try to use the "Verify" menu from the Adaptec BIOS. It finds and tries to re-map the bad sectors (it tries to preserve data during this too, unless the sector is completely unreadable). > I do the full 14 pattern tests before I put a SCSI disk in service. When a disk starts losing blocks like this, usually they only multiply over time. The best thing you can do is replace the disk and move the data before you lost more of it. -SB