Date: Thu, 7 Jul 2011 08:22:34 +0200 From: Berczi Gabor <freebsd@berczi.be> To: freebsd-current@freebsd.org Cc: Volodymyr Kostyrko <c.kworr@gmail.com> Subject: Re: ZFS boot fails with two pools Message-ID: <2040FCF6-2CA2-4CF3-BB78-F5A3069297FF@berczi.be> In-Reply-To: <4E14C0D9.9040503@gmail.com> References: <12DA9EAC-8677-49AD-BA6C-5A155D2A6122@berczi.be> <4E14C0D9.9040503@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 6, 2011, at 10:08 PM, Volodymyr Kostyrko wrote: > 1. Check that pools have up-to-date boot code. I tried 8.2 and HEAD. You mean gpart+gptzfsboot+pmbr, right? > 2. Try to convince bios to boot from the disk of pool2. There is no disk with a singular ZFS pool. > 3. You can possibly try deploying /boot/boot0 MBR selector code over = disks of data pool. Supplied boot0 code can be used to choose another = disk to jump to it during boot process and will remember the last = choice. I'm not really sure how to do this with GPT. Should I use boot0 instead = of pmbr? However, this = (http://freebsd.1045724.n5.nabble.com/Booting-from-ZFS-raidz-td4032461.htm= l) may be related to the problem: > You can boot from any of the drives and as long as the BIOS can see =20= > enough drives you should be able to boot. In my case, the BIOS certainly can not see all members of the raid-z = pool. The question is: why does it want to boot from raid-z at all, and = how could it be persuaded to use the mirrored pool instead?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2040FCF6-2CA2-4CF3-BB78-F5A3069297FF>