From owner-freebsd-questions@FreeBSD.ORG Mon Oct 13 23:49:12 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A15E16A4B3 for ; Mon, 13 Oct 2003 23:49:12 -0700 (PDT) Received: from mail.hacknslash.org (bdsl.66.14.88.171.gte.net [66.14.88.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39EDA43F93 for ; Mon, 13 Oct 2003 23:49:09 -0700 (PDT) (envelope-from octavian@hacknslash.org) Received: (qmail 45159 invoked from network); 14 Oct 2003 06:49:21 -0000 Received: from phobos.lexis.int (10.0.0.15) by mail.hacknslash.org with RC4-MD5 encrypted SMTP; 14 Oct 2003 06:49:21 -0000 From: Octavian Hornoiu To: freebsd-questions@freebsd.org Content-Type: text/plain Message-Id: <1066113972.1915.36.camel@phobos.lexis.int> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 13 Oct 2003 23:46:12 -0700 Content-Transfer-Encoding: 7bit Subject: big vinum problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: octavian@hacknslash.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2003 06:49:12 -0000 After a power loss last night i restarted my server with a 425 gig or so RAID-5 array and expected to go through a length fsck after which the system would come up. However, one of the vinum subdisks was down. So, i rebooted into single user mode, i restarted the home.p0.s3 subdisk and then i ran a manual fsck. What followed was a series of hard errors that said: ad7s1e: hard error reading fsbn 86482817 of 43241337-43241448 (ad7s1 bn 86482817; cn 5383 tn 78 sn 8) status=59 error=40 vinum: home.p0.s3 is crashed by force vinum: home.p0 is degraded fatal: home.p0.s3 read error, block 43241337 for 57344 bytes home.p0.s3 user buffer block 30268632 for 57344 bytes ** Phase 2 - Check Pathnames ad11s1e hard error etc then home.p0.s7 becomes corrupt and crashes by force and then i find myself staring at a screen that says: CANNOT READ: BLK 297103054 CONTINUE [yn] I have done this twice now and every time vinum successfully initializes the subdisk and the plex comes up and is in the "up" state but once i run fsck it crashes again. What exactly can i do to remedy this. If it's a bad disk i'll replace it but can't vinum work around bad blocks? My system is FreeBSD 4.9 RC from RELEASE branch with all the latest patches, i'm fully up to date. I have 8 subdisks in vinum home.p0.s0-s7 with a 55 GB partition on each drive used by vinum. All the drives are identical and all they contain is the vinum partitions. Please CC me in any emails you send as I am not on the list. Thanks for your help! octavian