From owner-freebsd-questions Mon Dec 27 22:58:59 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mail.telestream.com (mail.telestream.com [205.238.4.5]) by hub.freebsd.org (Postfix) with ESMTP id AD7A314D7D for ; Mon, 27 Dec 1999 22:58:55 -0800 (PST) (envelope-from keith@mail.telestream.com) Received: from localhost (keith@localhost) by mail.telestream.com (8.9.3/8.9.3) with ESMTP id WAA12114 for ; Mon, 27 Dec 1999 22:58:53 -0800 Date: Mon, 27 Dec 1999 22:58:53 -0800 (PST) From: To: freebsd-questions@freebsd.org Subject: bad blocks 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 Well after reading through the mail archives I get the impression that if you have and error from fsck like this "BAD SUPER BLOCK. VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE." That the disk is swish cheeze.. I can't believe that since these are new drives as of two months ago. I run fsck and it's marked clean and I can mount it. Then on reboot I have to run fsck again to be able to mount it. It's on a RAID-5 array that up to now was working fine. A power failure forced the reboot and from then on fsck dies on boot forcing a manual fsck. Any idea? Keith To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message