From owner-freebsd-questions  Thu Feb 10 20: 0:29 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from ducky.nz.freebsd.org (chilled.unixathome.org [203.79.82.27])
	by builder.freebsd.org (Postfix) with ESMTP id BFE684662
	for <freebsd-questions@FreeBSD.ORG>; Thu, 10 Feb 2000 20:00:21 -0800 (PST)
Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99])
	by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id QAA22480;
	Fri, 11 Feb 2000 16:59:38 +1300 (NZDT)
Message-Id: <200002110359.QAA22480@ducky.nz.freebsd.org>
From: "Dan Langille" <dan@freebsddiary.org>
Organization: The FreeBSD Diary
To: Greg Lehey <grog@lemis.com>
Date: Fri, 11 Feb 2000 16:59:19 +1300
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: vinum volume dies.  fsck can help?
Reply-To: dan@freebsddiary.org
Cc: freebsd-questions@FreeBSD.ORG
In-reply-to: <20000211121558.E76521@freebie.lemis.com>
References: <200002102051.JAA20685@ducky.nz.freebsd.org>
X-mailer: Pegasus Mail for Win32 (v3.12b)
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On 11 Feb 00, at 12:15, Greg Lehey wrote:

> On Friday, 11 February 2000 at  9:51:06 +1300, Dan Langille wrote:
> > I have a box with three SCSI drives (da0 - da2).   da1 and da2 are a
> > single vinum volume
> >
> > vinum: loaded
> > Can't open history file /var/tmp/vinum_history: No such file or directory
> > (2)
> > vinum: reading configuration from /dev/da2s1e
> > vium: updating configuration from /dev/da1s1e
> > vium: /dev is mounted read-only, not rebuilding /dev/vinum
> > Waring defective object
> >
> > p nzmirror.p0        S State: corrupt    Subdisk:        2 Size:      2002MB
> > S nzmirrot.p0.s1       State: stale      Po:        256 kB Size:      1001MB
> > swapon: adding /dev/da0s1b as swap device
> > Automatic reboot in progress...
> >
> > [stuff about /dev/rda0s1* snipped]
> >
> > /dev/vinum/nzmirror: CANNOT READ: BLK 1247904
> > /dev/vinum/nzmirror: UNEPECTED INCONSISTENCY: run fsck
> > MANUALLY.
> > THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED
> > INCONSISTENCY:
> >     /dev/vinum/rnzmirror (/nsmirror)
> >
> > It then drops to single user mode.
> >
> > Should I be running fsck -y /nzmirror or fsck -y
> > /dev/vinum/rnzmirror ?
> 
> /dev/vinum/rnzmirror, if you're running 3.x..

Yes, this is 3.3-stable.

> > Offhand, It sounds to me like the disk is dead.
> 
> Yes, or it died.  Do a 'camcontrol devlist' to see if it's even
> recognized.  'vinum l -V nzmirrot.p0.s1' will tell you which device
> should be up.  If it's there, you're going to have to start the drive
> and the subdisk.

'camcontrol devlist' lists all expected disks: da0, da1, and da2.

Which I hope is good news?

the rest is typed by hand:

# vinum
vinum-> l -V nzmirror.p0.s1
Subdisk nzmirror.p0.s1:
size:		1049624576 bytes(1001MB)
state: stale
plex nzmirror.p0 at offset 262144 (266 KB)
drive d2 (/dev/da2s1se) at offset 135600 (132KB)

vinum-> start nzmirror.p0.s1
can't start nzmirror.p0.s1: device busy (16)

vinum-> stop

# vinum start
Can't open history file /var/tmp/vinum_history: No such file or directory
vinum: already read config from d1

I'll come back to this later tonight.  cheers.
--
Dan Langille - DVL Software Limited [I'm looking for more work]
The FreeBSD Diary     - http://www.freebsddiary.org/
NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/
The Racing System     - http://www.racingsystem.com/
unix @ home           - http://www.unixathome.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message