Date: Fri, 17 Jul 2009 18:22:13 +0200 From: Stefan Bethke <stb@lassitu.de> To: Arnaud Houdelette <arnaud.houdelette@tzim.net> Cc: freebsd-fs@freebsd.org Subject: Re: Booting from ZFS raidz Message-ID: <BFDEAF9B-B586-4EBD-A2DD-D386C6A1C0B3@lassitu.de> In-Reply-To: <4A6097BA.8030305@tzim.net> References: <9461581F-F354-486D-961D-3FD5B1EF007C@rabson.org> <20090201072432.GA25276@server.vk2pj.dyndns.org> <246ecf0c87f944d70c5562eeed4165c9@mail.rabson.org> <9cc826f0720e1624489dd6e6d384babc.squirrel@www.noacks.org> <e6a5ee8d701b0d3393a6d3966ebfe634.squirrel@www.noacks.org> <e255c2534239be5cfec8e301b887f752.squirrel@www.noacks.org> <67089745-3E3B-45CF-B4E8-91F3B52C8A4C@lassitu.de> <3F75A414-1D5F-4692-B3B1-41EBCC1A22D2@lassitu.de> <4A6097BA.8030305@tzim.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 17.07.2009 um 17:24 schrieb Arnaud Houdelette: > Stefan Bethke a =E9crit : >> Am 16.07.2009 um 14:06 schrieb Stefan Bethke: >> >>> Am 12.07.2009 um 09:06 schrieb Jonathan Noack: >>> >>>> Anyone know how I should proceed? I'm really frustrated that I =20 >>>> haven't >>>> been able to get this working. >>> >>> Me too. I just decided to revisit this, and unfortunatly, I'm =20 >>> still stuck with the loader having trouble reading blocks off the =20= >>> raidz1 volume. I've updated the creation script (see below). =20 >>> This is on r195709, with LOADER_ZFS_SUPPORT?=3DYES in = /etc/make.conf. >> >> I just checked that my basic procedure is sane by creating a single =20= >> vdev pool (zpool create /dev/gpt/zfs0), and that is booting and =20 >> working just fine. >> >> >> Stefan >> > I got the same kind of errors with 8.0-BETA1 (rebuilt loader with =20 > ZFS_SUPPORT) with raidz on a VirtualBox. > I however got some hints : > Tried with single disk on pool : works like a charm. > Tried with a mirror : the loader only 'sees' the first disk. Could =20 > that be the source of our problems ? > > BTX loader only shows drives A: and C: > > lsdev -v gives : > cd devices: > disk devices: > disk0: BIOS drive A: > disk1: BIOS drive C: > disk1p1: FreeBSD boot 64KB > disk1p2: FreeBSD ZFS 19GB > pxe devices: > zfs devices: > pool: zroot > config: > > NAME STATE > zroot DEGRADED > mirror DEGRADED > gpt/zfs1 ONLINE > gpt/zfs2 OFFLINE > > As the mirror is degraded but readable, the loader is able to boot. > Could it be a BIOS or boot0 problem ? In VMware Fusion, it appears the loader sees all disks (with my UFS =20 disk attached, and with ZFS on raw devices: OK lsdev -v cd devices: disk devices: disk0: BIOS drive A: disk1: BIOS drive C: disk1s1a: FFS 30GB (2097215 - 67103505) disk1s1b: swap 1024MB (63 - 2097215) disk2: BIOS drive D: disk2: FFS bad disklabel disk3: BIOS drive E: disk3: FFS bad disklabel disk4: BIOS drive F: disk4: FFS bad disklabel pxe devices: zfs devices: pool: zroot config: NAME STATE zroot ONLINE raidz1 ONLINE da1 ONLINE da2 ONLINE da3 ONLINE OK When detaching the first disk, so that only the three ZFS disks are =20 available, I get the same output (but loader error on trying to read =20 the kernel, as posted previously). Stefan --=20 Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BFDEAF9B-B586-4EBD-A2DD-D386C6A1C0B3>