From owner-freebsd-fs@FreeBSD.ORG Wed May 22 15:02:22 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1E59DDBD for ; Wed, 22 May 2013 15:02:22 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.78]) by mx1.freebsd.org (Postfix) with ESMTP id ADEE9A8D for ; Wed, 22 May 2013 15:02:21 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1UfAYO-0002EQ-N0; Wed, 22 May 2013 17:02:13 +0200 Received: from [81.21.138.17] (helo=ronaldradial.versatec.local) by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1UfAYM-0004o4-C5; Wed, 22 May 2013 17:02:10 +0200 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-fs@freebsd.org, "Leslie Jensen" Subject: Re: Upgrading from 8.3 to 9.1 zfs pool can't attach References: <519CA3A5.3020109@eskk.nu> Date: Wed, 22 May 2013 17:02:09 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: <519CA3A5.3020109@eskk.nu> User-Agent: Opera Mail/12.15 (Win32) X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: 0.8 X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=disabled version=3.3.1 X-Scan-Signature: 448baf4759cd3283a5930955cc61e1db X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 May 2013 15:02:22 -0000 On Wed, 22 May 2013 12:53:25 +0200, Leslie Jensen wrote: > > I've upgraded a machine with freebsd-update from 8.3 to 9.1. > > After the first restart I edited /etc/fstab in single user mode because > the names on the disks had changed. But the zfs pool I have seem to have > a problem and I'm sure on how to recover it. > > > May 22 12:00:39 kernel: ZFS WARNING: Unable to attach to ada0. > May 22 12:00:39 kernel: ZFS WARNING: Unable to attach to ada1. > May 22 12:00:39 kernel: ZFS WARNING: Unable to attach to ada4. > May 22 12:00:40 kernel: ZFS WARNING: Unable to attach to ada5. > > > camcontrol devlist > at scbus0 target 0 lun 0 (ada0,pass0) > at scbus1 target 0 lun 0 (ada1,pass1) > at scbus2 target 0 lun 0 (ada2,pass2) > at scbus2 target 1 lun 0 (ada3,pass3) > at scbus3 target 0 lun 0 (ada4,pass4) > at scbus3 target 1 lun 0 (ada5,pass5) > > ada2 and ada3 are configured as raid/r0 holding the system. > > ada0, ada1, ada4 and ada5 should be a zfs pool with /home > > > cat /etc/fstab > > # Device Mountpoint FStype Options Dump Pass# > /dev/raid/r0s1b none swap sw 0 0 > /dev/raid/r0s1a / ufs rw 1 1 > /dev/raid/r0s1e /tmp ufs rw 2 2 > /dev/raid/r0s1f /usr ufs rw 2 2 > /dev/raid/r0s1d /var ufs rw 2 2 > > > I'm not sure but shouldn't the mount point for /home also appear in > fstab? > > Maybe I messed up during the manual editing of files during the update > process? > > > Can I recover or shall I destroy the pool and rebuild it? > > Thanks > > /Leslie Mounts from zfs do not have to be in fstab. You can set a mountpoint on a zfs volume which kind of mounts itself. Can you send more information about the 'Unable to attach to ada[0-4]' messages? Maybe a complete dmesg (/var/run/dmesg.boot). And how are these disks configured/partitioned? Output from 'gpart list ada0' or 'gpart show ada0' and for the other disks. Are you using stuff like glabel? Ronald.