From owner-freebsd-questions Tue Jun 8 15:12: 3 1999 Delivered-To: freebsd-questions@freebsd.org Received: from fw2.roguewave.com (fw2.roguewave.com [208.151.233.2]) by hub.freebsd.org (Postfix) with ESMTP id 8AA6814E1F for ; Tue, 8 Jun 1999 15:12:02 -0700 (PDT) (envelope-from carey@roguewave.com) Received: by fw2.roguewave.com; id XAA23934; Tue, 8 Jun 1999 23:15:11 -0700 (PDT) Received: from cvo1.cvo.roguewave.com(10.68.4.36) via SMTP by hub.FreeBSD.ORG, id smtpd023930; Tue Jun 8 23:15:08 1999 Received: by cvo1.cvo.roguewave.com with Internet Mail Service (5.5.1960.3) id ; Tue, 8 Jun 1999 15:13:20 -0700 Message-ID: From: Woody Carey To: "'Todd Hansen'" , freebsd-questions@FreeBSD.ORG Subject: RE: bad block scans Date: Tue, 8 Jun 1999 15:13:18 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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