From owner-freebsd-geom@FreeBSD.ORG Mon Feb 27 20:57:25 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FE4416A420 for ; Mon, 27 Feb 2006 20:57:25 +0000 (GMT) (envelope-from cochard@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEE5E43D73 for ; Mon, 27 Feb 2006 20:57:15 +0000 (GMT) (envelope-from cochard@gmail.com) Received: by nproxy.gmail.com with SMTP id k26so743242nfc for ; Mon, 27 Feb 2006 12:57:14 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:sender:to:subject:mime-version:content-type; b=LXRyX8bOZlYlzyRr8AhPlI410Cl+FfDlAKAgfq76L/QrkGTcilWc8OHmLPAfu3wYxabT3ux/hPi8gDf8AAH65QTIx0PtB9CrcWT5EtCI1/eUvlSssu/dib/YKXwrDEkc8ZR9uZZJ3ZDhc9kgXxG761mHezV5O7oGaeZWR96Vtmk= Received: by 10.48.14.12 with SMTP id 12mr322960nfn; Mon, 27 Feb 2006 12:50:18 -0800 (PST) Received: by 10.48.216.14 with HTTP; Mon, 27 Feb 2006 12:50:18 -0800 (PST) Message-ID: <3131aa530602271250r458dd9fep@mail.gmail.com> Date: Mon, 27 Feb 2006 21:50:18 +0100 From: "Olivier Cochard" Sender: cochard@gmail.com To: freebsd-geom@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Gvinum RAID5 volume don't work after a simple reboot X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Olivier Cochard List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 20:57:25 -0000 Hi all, One of my user have a big problem with gvinum and RAID5: He builts a RAID 5 volume that worked great for two days. But, when he reboot the PC it takes about 2 hours to get the disks to the "UP" state: Here is an example of output during the starting of the volume: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D 3 drives: D disk_ad1 State: up /dev/ad1s1 A: 0/238475 MB (0%) D disk_ad2 State: up /dev/ad2s1 A: 0/238475 MB (0%) D disk_ad3 State: up /dev/ad3s1 A: 0/238475 MB (0%) 1 volume: V fatty State: down Plexes: 1 Size: 465 GB 1 plex: P fatty.p0 R5 State: down Subdisks: 3 Size: 465 GB 3 subdisks: S fatty.p0.s2 State: I 70% D: disk_ad3 Size: 232 GB S fatty.p0.s1 State: I 70% D: disk_ad2 Size: 232 GB S fatty.p0.s0 State: up D: disk_ad1 Size: 232 GB =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D But, Once it gets to "UP", it's impossible to mount the volume: mount: /dev/gvinum/fatty on /mnt/home1: incorrect super block. then, I try an fsck: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D fsck -t ufs /dev/gvinum/fatty Cannot find file system superblock ** /dev/gvinum/fatty /dev/gvinum/fatty: CANNOT FIGURE OUT FILE SYSTEM PARTITION =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D How could he retrieves all the data stored on the RAID volume ? Thanks, Olivier -- Olivier Cochard FreeNAS main developer http://www.freenas.org Skype: callto://ocochard