From owner-freebsd-questions@FreeBSD.ORG Tue Mar 31 12:22:46 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 233541065672 for ; Tue, 31 Mar 2009 12:22:46 +0000 (UTC) (envelope-from jmiscaro@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by mx1.freebsd.org (Postfix) with ESMTP id CBA3C8FC29 for ; Tue, 31 Mar 2009 12:22:45 +0000 (UTC) (envelope-from jmiscaro@gmail.com) Received: by qw-out-2122.google.com with SMTP id 9so1766258qwb.7 for ; Tue, 31 Mar 2009 05:22:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=utnQ8VcKhkH/A3kQ18745yQp8n4iHqAf6c/HIC+Vd/8=; b=DeMWMdFRibBTqsO7Za3RWOIF4ERjna8v6VBy+0xlZF/8NlCTV+64guDcgGlFI5KrGx EeXZaPQCAtdGuYKJCti5Xhgr2gp6s+GyF/MqtG7FkUOFftK5Kta074LSb8W0yDjpC16o 3pI59tUjzNIqWIh3hgkBp+JomIl6j2T68pdYA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=AzPoZ+1QcvYX2+yuCNgeNvxPDRaOHROQ/jvNrcfavs+92TuRVm7nAhpQ8FdhZJSGEf 9pz0ZJjJ+/+Zp2gGq2FMrMD4XZqWz/xPkuyzSc/beS+FGnnZL/BvXOw4cVLJM9SHOvxB 1/TUlOOnOX0rZ9T30DhoNkq98I4jJd/9db7zs= MIME-Version: 1.0 Received: by 10.229.81.139 with SMTP id x11mr2357352qck.14.1238502164981; Tue, 31 Mar 2009 05:22:44 -0700 (PDT) In-Reply-To: References: Date: Tue, 31 Mar 2009 08:22:44 -0400 Message-ID: From: Juan Miscaro To: Ivan Voras Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: Recovering a GEOM RAID0 array X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 12:22:46 -0000 2009/3/31 Ivan Voras : > Juan Miscaro wrote: >> Hi gang, >> >> I'm running a remote 6.2 system which recently got shut down >> unexpectedly (tower was physically nudged and apparently lost power). >> I am running a 2-disk striped array with the geom_stripe.ko module. >> >> So my fstab line is >> >> /dev/stripe/st0a =C2=A0 =C2=A0 =C2=A0 =C2=A0/data =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 ufs =C2=A0 =C2=A0 rw,acls =C2=A0 =C2=A0 =C2=A0 =C2=A0 2 =C2= =A0 =C2=A0 =C2=A0 2 >> >> Thing is, the /dev/stripe directory no longer exists. =C2=A0The system w= as >> running for well over 2 years with several reboots in there. =C2=A0I hav= e a >> lot of data that I want to recover on these 2 disks. =C2=A0Is there any = way >> to regain access to the data? =C2=A0I can' t seem to find anything unusu= al >> in the logs. > > You need to see if the drives that have made the array still exist and > are accessible. See if they are recognized in dmesg - maybe a cable was > knocked out from one of them. This is the end of dmesg (the drives in question are ad1 and ad3): acd0: CDROM at ata0-master PIO4 ad1: 305244MB at ata0-slave UDMA100 ad3: 305245MB at ata1-slave UDMA100 GEOM_STRIPE: Device st0 created (id=3D3091204740). GEOM_STRIPE: Disk ad1 attached to st0. ad4: 152626MB at ata2-master SATA150 WARNING: Expected rawoffset 0, found 63 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) Trying to mount root from ufs:/dev/ad4s1a WARNING: R/W mount of /backups denied. Filesystem is not clean - run fsck WARNING: R/W mount of /backups denied. Filesystem is not clean - run fsck rl0: link state changed to UP arp: 10.9.1.204 moved from 00:0f:ea:56:4c:11 to 00:0d:87:b4:00:3e on rl0 arp: 10.9.1.204 moved from 00:0d:87:b4:00:3e to 00:0f:ea:56:4c:11 on rl0 GEOM_STRIPE: Disk ad1 removed from st0. GEOM_STRIPE: Device st0 destroyed. GEOM_STRIPE: Device st0 created (id=3D3091204740). GEOM_STRIPE: Disk ad1 attached to st0. # bsdlabel ad1 # /dev/ad1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 1250280640 16 4.2BSD 2048 16384 28552 c: 1250280656 0 unused 0 0 # "raw" part, don't edit partition a: partition extends past end of unit partition c: partition extends past end of unit bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities # bsdlabel ad3 # /dev/ad3: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 625142432 16 4.2BSD 2048 16384 28552 c: 625142448 0 unused 0 0 # "raw" part, don't edit These drives should appear to be identical. I have since run fsck on the other drive (ad4, an external USB drive). -- jm