Date: Wed, 24 Feb 2010 22:12:25 -0500 From: Chris <behrnetworks@gmail.com> To: Matt Reimer <mattjreimer@gmail.com> Cc: Scot Hetzel <swhetzel@gmail.com>, freebsd-current@freebsd.org, Pegasus Mc Cleaft <ken@mthelicon.com> Subject: Re: Seeing the dreaded "ZFS: i/o error - all block copies unavailable" on 9.0-CURRENT Message-ID: <64aa03031002241912t396b3001ub89fec82a020f891@mail.gmail.com> In-Reply-To: <f383264b1002231003i51fe2bbdr155a06d10097315d@mail.gmail.com> References: <64aa03031002161803h667734cal4d668b9eb9c0a1a8@mail.gmail.com> <64aa03031002181921m2d00966cx6a3bb2c6e761970d@mail.gmail.com> <64aa03031002181938rb9355a3sae56e9d854bdcf78@mail.gmail.com> <201002231120.54401.jhb@freebsd.org> <f383264b1002231003i51fe2bbdr155a06d10097315d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
So it sounds like somehow my system is trying to use the old boot2 method when I don't hit F12. I'm guessing the difference is due to how the hard drive is getting presented to the boot loader by the BIOS. How can I get rid of the legacy boot system and use only the ZFS bootloader? On Tue, Feb 23, 2010 at 1:03 PM, Matt Reimer <mattjreimer@gmail.com> wrote: > On Tue, Feb 23, 2010 at 8:20 AM, John Baldwin <jhb@freebsd.org> wrote: >> >> On Thursday 18 February 2010 10:38:38 pm Chris wrote: >> > > I'm seeing some difference in the bootloader output between using th= e >> > > F12 workaround or not: >> > > >> > > F12 workaround mode: >> > > >> > > FreeBSD/i386 boot >> > > Default: zroot:/boot/zfsloader >> > > boot: status >> > > config: >> > > >> > > =A0 =A0 =A0 =A0 =A0 =A0 NAME =A0 =A0 STATE >> > > =A0 =A0 =A0 =A0 =A0 =A0 zroot =A0 =A0ONLINE >> > > =A0 =A0 =A0 =A0gpt/disk0 =A0 ONLINE >> > > >> > > >> > > No F12 key pressed: >> > > >> > > FreeBSD/i386 boot >> > > Default: zroot:/boot/kernel/kernel >> > > config: >> > > >> > > =A0 =A0 =A0 =A0 =A0 =A0 =A0NAME =A0 =A0 STATE >> > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 zroot =A0 =A0ONLINE >> > > =A0 =A0 =A0 =A0 =A0gpt/disk0 =A0 ONLINE >> > > >> > > >> > > What's up with the differences between the Default boot setting? >> > > >> > >> > Sorry for the spam but I'm seeing something else very interesting.... >> > If I boot to Good Mode (F12) and break to the "boot:" prompt, the >> > system boots if I type /boot/zfsloader. However, if I type >> > /boot/kernel/kernel (as was seen in the Default setting when I didn't >> > hit F12), =A0I get a crash that looks like the following: >> > ----------------------------------------- >> > FreeBSD/i386 boot >> > Default: zroot:/boot/zfsloader >> > boot: /boot/kernel/kernel >> > int=3D00000006 =A0 =A0err=3D00000000 =A0efl=3D00010882 =A0eip=3D002000= 00 >> > eax=3D0018b070 =A0ebx=3Ded7706bd ecx=3Dc72e2ca8 edx=3D00000000 >> > esi=3D00000040 =A0 edi=3D000929d0 =A0ebp=3D0009279c esp=3D00009401 >> > cs=3D0008 =A0ds=3D0010 =A0 es=3D0010 =A0fs=3D0010 =A0gs=3D0010 =A0ss= =3D0010 >> > cs:eip=3Dff ff ff ff ff ff ff ff 7f-00 00 00 00 00 00 00 00 >> > =A0 =A0 =A0 =A0 =A0 =A000 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 >> > ss:esp=3D36 80 0d 07 90 00 00 01-e9 c4 fc ff ff aa ac 84 >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0c0 0f 84 86 00 00 00 a8-80 74 f2 88 c5 b0 3= d aa >> > BTX halted >> > ----------------------------------------- >> >> I'm not sure how well we support booting a kernel from boot2 anymore, mu= ch >> less from zfsboot. =A0Using /boot/loader (or /boot/zfsloader) is probabl= y >> the >> only tested (and realistically supported) case. > > Yeah, the last time I tried this it didn't work, but I didn't hunt down w= hy. > Matt >> >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?64aa03031002241912t396b3001ub89fec82a020f891>