From owner-freebsd-questions@FreeBSD.ORG Fri Apr 16 10:24:55 2004 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 B2D4F16A4CE for ; Fri, 16 Apr 2004 10:24:55 -0700 (PDT) Received: from moneo.upc.es (moneo.upc.es [147.83.2.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5BD343D5D for ; Fri, 16 Apr 2004 10:24:54 -0700 (PDT) (envelope-from joan@iaeste-catalunya.upc.es) Received: from localhost (localhost [127.0.0.1]) by moneo.upc.es (8.12.10/8.12.10) with ESMTP id i3GHOqxp007962 for ; Fri, 16 Apr 2004 19:24:52 +0200 (MEST) Received: from moneo.upc.es ([127.0.0.1]) by localhost (moneo [127.0.0.1]) (amavisd-new, port 10023) with LMTP id 06724-02-6 for ; Fri, 16 Apr 2004 19:24:51 +0200 (MEST) Received: from iaeste-catalunya.upc.es (iaeste-catalunya.upc.es [147.83.55.111]) by moneo.upc.es (8.12.10/8.12.10) with SMTP id i3GHDlbO003815 for ; Fri, 16 Apr 2004 19:15:07 +0200 (MEST) Received: (qmail 20277 invoked by uid 1001); 16 Apr 2004 17:11:15 -0000 Date: Fri, 16 Apr 2004 19:11:15 +0200 From: Joan Picanyol i Puig To: freebsd-questions@freebsd.org Message-ID: <20040416171115.GA19845@iaeste-catalunya.upc.es> Mail-Followup-To: joan-lists@iaeste-catalunya.upc.es, freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.5.1i Subject: vinum havoc X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Apr 2004 17:24:55 -0000 [please honour Mail-Followup-To:, can't read the list until I solve thi until I solve this] Hi, For unknown reasons, vinum has broken itself again (the only weird thing I did was booting from a different root partition). The only commands I have given are start/stop whatever (pretty much everything). Note how storage & worthless are apparently empty, plus an *invalid* drive at the bottom (long lines): # vinum ld D storage State: up Device /dev/ad0s1d Avail: 38166/381 66 MB (100%) D worthless State: up Device /dev/ad2s1d Avail: 38038/380 38 MB (100%) D barracuda State: up Device /dev/da0s1e Avail: 2/1280 MB (0%) D barracudaf State: up Device /dev/da0s1f Avail: 0/7210 MB (0%) D ultrastar State: up Device /dev/da1s1e Avail: 1279/1280 MB (100%) D ultrastarf State: up Device /dev/da1s1f Avail: 7210/7210 MB (100%) D *invalid* State: referenced Device Avail: 0/0 MB Any attempt to start the volume on storage/worthless fails like: vinum -> lv -r bulk V bulk State: down Plexes: 1 Size: 74 GB P bulk.p0 C State: faulty Subdisks: 2 Size: 74 GB S bulk.p0.s0 State: crashed PO: 0 B Size: 37 GB S bulk.p0.s1 State: crashed PO: 37 GB Size: 37 GB vinum -> start bulk.p0.s0 Can't start bulk.p0.s0: Drive is down (5) vinum -> start bulk.p0.s1 Can't start bulk.p0.s1: Drive is down (5) Now for the worst (more damage inflicting) part. Even though vinum says a mirrored volume is up, I can't even fsck it: # vinum lv home V home State: up Plexes: 2 Size: 4394 MB # fsck /dev/vinum/home ** /dev/vinum/home BAD SUPER BLOCK: MAGIC NUMBER WRONG /dev/vinum/home: NOT LABELED AS A BSD FILE SYSTEM (unused) # mount /fs/home/mount mount: /fs/home/dev-mount on /fs/home/mount: incorrect super block This is on RELENG_4_9, and I have already rebooted/restarted vinum many times. What should I do to make vinum come back to reason? tks -- pica