From owner-freebsd-stable@FreeBSD.ORG Wed Aug 17 13:54:42 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECED51065670 for ; Wed, 17 Aug 2011 13:54:42 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id A92CE8FC0A for ; Wed, 17 Aug 2011 13:54:42 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id DEEFA28429 for ; Wed, 17 Aug 2011 15:35:16 +0200 (CEST) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 0DFED28424 for ; Wed, 17 Aug 2011 15:35:10 +0200 (CEST) Message-ID: <4E4BC38D.1050808@quip.cz> Date: Wed, 17 Aug 2011 15:35:09 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: can not boot from RAIDZ with 8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2011 13:54:43 -0000 I tried mfsBSD installation on Dell T110 with PERC H200A and 4x 500GB SATA disks. If I create zpool with RAIDZ, the boot immediately hangs with following error: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS ZFS: unexpected object set type 0 ZFS: unexpected object set type 0 FreeBSD/x86 boot Default: tank0:/boot/kernel/kernel boot: ZFS: unexpected object set type 0 FreeBSD/x86 boot Default: tank0:/boot/kernel/kernel boot: The system is FreeBSD 8.2-STABLE #0: Sat Aug 13 20:33:31 CEST 2011 GENERIC amd64 Built from sources from Aug 13 2011. Identical system is booting fine from external (USB) drive and I can use data on zpool RAIDZ tank0 without any problems. So the pool and disks are fine, only boot failed. Disks (da0 - da3) are using GPT: => 34 976773101 da0 GPT (465G) 34 128 1 freebsd-boot (64k) 162 8388608 2 freebsd-swap (4.0G) 8388770 964689920 3 freebsd-zfs (460G) 973078690 3694445 - free - (1.8G) I also tried to create the pool manually instead of script from mfsBSD, but the result is the same. This was my manual method: gpart create -s GPT da0 gpart add -b 34 -s 128 -t freebsd-boot da0 gpart add -s 4g -t freebsd-swap -l swap0 da0 gpart add -s 460g -t freebsd-zfs -l tank0 da0 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 gpart create -s GPT da1 gpart add -b 34 -s 128 -t freebsd-boot da1 gpart add -s 4g -t freebsd-swap -l swap1 da1 gpart add -s 460g -t freebsd-zfs -l tank1 da1 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da1 gpart create -s GPT da2 gpart add -b 34 -s 128 -t freebsd-boot da2 gpart add -s 4g -t freebsd-swap -l swap2 da2 gpart add -s 460g -t freebsd-zfs -l tank2 da2 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da2 gpart create -s GPT da3 gpart add -b 34 -s 128 -t freebsd-boot da3 gpart add -s 4g -t freebsd-swap -l swap3 da3 gpart add -s 460g -t freebsd-zfs -l tank3 da3 gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da3 gmirror label -F -h -b load gmswap0 /dev/gpt/{swap0,swap1,swap2,swap3} zpool create -O mountpoint=/mnt -O atime=off -O setuid=off -O canmount=off tank0 raidz /dev/gpt/tank0 /dev/gpt/tank1 /dev/gpt/tank2 /dev/gpt/tank3 zfs create -o mountpoint=legacy -o setuid=on tank0/root zpool set bootfs=tank0/root tank0 (...then zfs create for about 10 filesystems according to http://blogs.freebsdish.org/pjd/2010/08/06/from-sysinstall-to-zfs-only-configuration/ ) zfs set mountpoint=/ system (...then rsync data from external USB disk with working system...) And after reboot, the same error as above. Has somebody any suggestions? Miroslav Lachman PS: I can't try 8.2-RELEASE, because there is no support for PERC H200A which was commited after RELEASE.