From owner-freebsd-hackers Wed Jun 9 6:11:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scorpion.bugsoft.hik.se (scorpion.bugsoft.hik.se [194.47.165.105]) by hub.freebsd.org (Postfix) with ESMTP id 5DC1414C13 for ; Wed, 9 Jun 1999 06:11:30 -0700 (PDT) (envelope-from yottaman@writeme.com) Received: from te31002 ([194.47.173.15]) by scorpion.bugsoft.hik.se (Netscape Messaging Server 3.5) with SMTP id 169 for ; Wed, 9 Jun 1999 15:13:14 +0200 Message-ID: <003901beb279$92b169c0$0fad2fc2@te.hik.se> From: "John Andersson" To: Subject: Bad sectors on vinum volym Date: Wed, 9 Jun 1999 15:11:23 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to have some bad sectors on my vinum volume, fsck reports the following and does not seem to be able to fix it: THE FOLLOWING SECTORS COULD NOT BE WRITTEN: 44609178, 44609179, ***** FILE SYSTEM STILL DIRTY ***** ***** FILE SYSTEM WAS MODIFIED ***** ***** PLEASE RERUN FSCK ***** This was just a cut of the fsck output, it totally reports about 10 sectors that it can't read or write to. I tried to execute the badsect program (badsect /xxx/BAD 44609178 44609179), but it reports: Cannot find dev 061004206 corresponding to /xxx/BAD The volym in question consists of a 5 disc striped plex. Is it possible to run badsect on a vinum volym to fix this? I would prefer not to lose all data on the volym, and since it's about 40G of data I can't backup all data. I run FreeBSD 3.2-Release. It is possible to force a mount and continue to use the volym, but some directories are unaccessible. Any help would be most appreciated, John. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message