From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 12 06:35:56 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D204E16A41F for ; Thu, 12 Jan 2006 06:35:56 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 233E643D46 for ; Thu, 12 Jan 2006 06:35:56 +0000 (GMT) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.sv.meer.net (8.12.10/8.12.6) with ESMTP id k0C6Xq21012268 for ; Wed, 11 Jan 2006 22:35:56 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: from mail.meer.net (localhost [127.0.0.1]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id k0C6Xe4n086407 for ; Wed, 11 Jan 2006 22:33:40 -0800 (PST) (envelope-from jrhett@mail.meer.net) Received: (from jrhett@localhost) by mail.meer.net (8.13.3/8.13.3) id k0C6XeEE086406 for freebsd-hardware@freebsd.org; Wed, 11 Jan 2006 22:33:40 -0800 (PST) (envelope-from jrhett) Date: Wed, 11 Jan 2006 22:33:40 -0800 From: Jo Rhett To: freebsd-hardware@freebsd.org Message-ID: <20060112063340.GA84964@svcolo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: svcolo.com User-Agent: Mutt/1.5.9i Subject: gvinum in 6.0-rel -- how to attach plexes? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2006 06:35:57 -0000 I've got a (home) server that I was using vinum for instead of the hardware raid controllers we use at the shop. Unfortunately it died pretty hard, and I'm trying to recover data from the hard disk on the replacement system. Old Hard Disk: 4.10-rel with a vinum root New Hard Disk: 6.0-rel I've added geom_vinum_load="YES" to /boot/loader.conf and now when I boot I can run "gvinum" and I see gvinum -> list 1 drive: D ibm1 State: up /dev/ad2s1e A: 58131/58131 MB (100%) 5 volumes: V space State: up Plexes: 0 Size: 0 B V tmp State: up Plexes: 0 Size: 0 B V var State: up Plexes: 0 Size: 0 B V usr State: up Plexes: 0 Size: 0 B V root State: up Plexes: 0 Size: 0 B 5 plexes: P space.p0 C State: up Subdisks: 0 Size: 0 B P tmp.p0 C State: up Subdisks: 0 Size: 0 B P var.p0 C State: up Subdisks: 0 Size: 0 B P usr.p0 C State: up Subdisks: 0 Size: 0 B P root.p0 C State: up Subdisks: 0 Size: 0 B 5 subdisks: S space.p0.s0 State: up D: ibm1 Size: 48 GB S tmp.p0.s0 State: up D: ibm1 Size: 256 MB S var.p0.s0 State: up D: ibm1 Size: 4096 MB S usr.p0.s0 State: up D: ibm1 Size: 4096 MB S root.p0.s0 State: up D: ibm1 Size: 256 MB What do I need to do to get the subdisks/plexs/volumes reattached or restarted? How can I get to this data? The vast majority of the commands listed in gvinum's help aren't working... gvinum -> attach tmp.p0.s0 tmp.p0 unknown command 'attach' gvinum -> start tmp gvinum: can't start: cannot start volume 'tmp'; errno: 6 gvinum -> start -w tmp gvinum: illegal option -- w There is no man page for gvinum, and no /dev/gvinum directory list various mailing list postings refer to. Where can I go from here? -- Jo Rhett senior geek SVcolo : Silicon Valley Colocation