From owner-freebsd-questions@FreeBSD.ORG Sat Jan 17 15:30:59 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 48526C59 for ; Sat, 17 Jan 2015 15:30:59 +0000 (UTC) Received: from mail.ssr.com (mail.ssr.com [199.4.235.6]) by mx1.freebsd.org (Postfix) with SMTP id 0BD83668 for ; Sat, 17 Jan 2015 15:30:58 +0000 (UTC) Received: (qmail 367 invoked from network); 17 Jan 2015 15:20:45 -0000 Received: from pool-108-27-192-213.nycmny.fios.verizon.net (HELO irelay.ssr.com) (sdb@108.27.192.213) by 199.4.235.6 with SMTP; 17 Jan 2015 15:20:45 -0000 Received: (qmail 1902 invoked by uid 103); 17 Jan 2015 15:13:32 -0000 Date: 17 Jan 2015 15:13:32 -0000 Message-ID: <20150117151332.1901.qmail@irelay.ssr.com> From: Scott Ballantyne To: freebsd-questions@freebsd.org Subject: ZFS Missing Pool after upgrade to 9.2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Jan 2015 15:30:59 -0000 I have been running 9.0 with zfs. two pools, both mirrors. One holds the boot file systems (zroot) and the other just holds a huge amount of data (zdata). After upgrading to 9.2, I can still reboot, but the zdata pool is not available. I am quite certain that there is no hardware issue (such as a disk failure). So how screwed am I? Is there a simple fix? Can I use freebsd-update rollback to go back to 9.0 and hopefully get my data back? I've done both the kernel, then reboot and freebsd-update the userland? Here are some more details, if any kind and knowledgeable soul out there can help: Zroot is currently running on disks ada0 and ada2. For some reason, zfs is trying to use ada2 as part of the ZDATA mirror: >config: > > NAME STATE READ WRITE CKSUM > zdata UNAVAIL 0 0 0 > mirror-0 UNAVAIL 0 0 0 > 1285589115166012386 UNAVAIL 0 0 0 was /dev/ada2 > 15986629349166314315 UNAVAIL 0 0 0 was /dev/ada3 Here is the gpart output: => 34 3907029101 ada0 GPT (1.8T) 34 128 1 freebsd-boot (64k) 162 25165824 2 freebsd-swap (12G) 25165986 3881863149 3 freebsd-zfs (1.8T) => 34 3907029101 ada2 GPT (1.8T) 34 128 1 freebsd-boot (64k) 162 25165824 2 freebsd-swap (12G) 25165986 3881863149 3 freebsd-zfs (1.8T) These are the disks that are running zroot. There are three other disks on the computer. One went bad, and is awaiting replacement. The other two belong in zdata. I'm not sure how all of these are being mapped to device names, but the bad one is reported as 'port0' on boot. I get these weird messages during boot: Jan 17 09:38:53 gigawattmomma kernel: link_elf_obj: symbol ata_controlcmd undefined Jan 17 09:38:53 gigawattmomma kernel: KLD file atapicam.ko - could not finalize loading And these: Jan 17 09:38:53 gigawattmomma kernel: GEOM_RAID: Intel-c3703415: Array Intel-c3703415 created. Jan 17 09:38:53 gigawattmomma kernel: GEOM_MIRROR: Device mirror/swap launched (2/2). Jan 17 09:38:53 gigawattmomma kernel: Root mount waiting for: GRAID-Intel usbus7 Jan 17 09:38:53 gigawattmomma last message repeated 20 times Jan 17 09:38:53 gigawattmomma kernel: GEOM_RAID: Intel-c3703415: Force array start due to timeout. Jan 17 09:38:53 gigawattmomma kernel: GEOM_RAID: Intel-c3703415: Disk ada3 state changed from NONE to ACTIVE. Jan 17 09:38:53 gigawattmomma kernel: GEOM_RAID: Intel-c3703415: Subdisk SYSTEM_RELIABLE:1-ada3 state changed from NONE to ACTIVE. Jan 17 09:38:53 gigawattmomma kernel: GEOM_RAID: Intel-c3703415: Subdisk DATA_RELIABLE:1-ada3 state changed from NONE to ACTIVE. Jan 17 09:38:53 gigawattmomma kernel: GEOM_RAID: Intel-c3703415: Disk ada4 state changed from NONE to FAILED. Jan 17 09:38:53 gigawattmomma kernel: GEOM_RAID: Intel-c3703415: Subdisk SYSTEM_RELIABLE:0-ada4 state changed from NONE to FAILED. Jan 17 09:38:53 gigawattmomma kernel: GEOM_RAID: Intel-c3703415: Subdisk DATA_RELIABLE:0-ada4 state changed from NONE to FAILED. Jan 17 09:38:53 gigawattmomma kernel: GEOM_RAID: Intel-c3703415: Array started. Jan 17 09:38:53 gigawattmomma kernel: GEOM_RAID: Intel-c3703415: Volume SYSTEM_RELIABLE state changed from STARTING to BROKEN. Jan 17 09:38:53 gigawattmomma kernel: GEOM_RAID: Intel-c3703415: Volume DATA_RELIABLE state changed from STARTING to BROKEN. Jan 17 09:38:53 gigawattmomma kernel: Trying to mount root from zfs:zroot []... Jan 17 09:38:53 gigawattmomma kernel: ZFS WARNING: Unable to attach to ada3. Jan 17 09:38:53 gigawattmomma kernel: ZFS WARNING: Unable to attach to ada4. Jan 17 09:38:53 gigawattmomma kernel: ZFS WARNING: Unable to attach to ada3. Jan 17 09:38:53 gigawattmomma kernel: ZFS WARNING: Unable to attach to ada4. Jan 17 09:38:53 gigawattmomma kernel: ZFS WARNING: Unable to attach to ada3. Jan 17 09:38:53 gigawattmomma kernel: ZFS WARNING: Unable to attach to ada4. Thanks in advance to anyone who can help here. Scott -- sdb@ssr.com