From owner-freebsd-questions Tue Jun 8 15:14: 0 1999 Delivered-To: freebsd-questions@freebsd.org Received: from oceana.nlanr.net (oceana.sdsc.edu [132.249.40.200]) by hub.freebsd.org (Postfix) with ESMTP id 7B6F11582C for ; Tue, 8 Jun 1999 15:13:57 -0700 (PDT) (envelope-from tshansen@oceana.nlanr.net) Received: from localhost (tshansen@localhost) by oceana.nlanr.net (8.8.6/8.8.6) with SMTP id PAA16571; Tue, 8 Jun 1999 15:13:55 -0700 (PDT) Date: Tue, 8 Jun 1999 15:13:55 -0700 (PDT) From: Todd Hansen To: Woody Carey Cc: freebsd-questions@FreeBSD.ORG Subject: RE: bad block scans In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG agreed. but it only seems to happen when we are accessing the disks and we are using well-known adaptec scsi cards. Anyway, it is one of our suspicions that we would like to get out of the way. -todd On Tue, 8 Jun 1999, Woody Carey wrote: > Someone please correct me if I am way off base here, but this sounds > like > flaky hardware, not necessarily the disk itself. > > Why would bad disk blocks cause a crash? > > > > > is there anyway to scan a disk for new bad blocks without > > destroying the > > data already on the disk? We are looking into this because we > > are getting > > a problem where our server will randomly just die and reboot > > while doing > > some disk work but it doesn't put any errors on the screen or in the > > kernel logs. :( > > Thanks. > > Todd Hansen > > NLANR > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message