Date: Thu, 13 May 2010 08:50:31 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Volodymyr Kostyrko <c.kworr@gmail.com> Cc: freebsd-fs@FreeBSD.org Subject: Re: bin/144214: zfsboot fails on gang block after upgrade to zfs v14 Message-ID: <4BEB9327.6040405@icyb.net.ua> In-Reply-To: <4BE09F5D.2080100@gmail.com> References: <201004291220.o3TCK3Bo029643@freefall.freebsd.org> <4BE09F5D.2080100@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 05/05/2010 01:27 Volodymyr Kostyrko said the following: > On 29.04.2010 15:20, Andriy Gapon wrote: >> Just to be on the sure side: have you guys actually updated bootblocks on >> your system? I.e. the code that runs before loader and that resides beyond >> filesystems. > > Yes, I do. Pardon me, but please clarify what you mean by this answer. See below for explanation of my confusion. > Actually I was hit by the same bug recently one more time. After rebuild > machine refuses to boot because of some gang blocks. I've tried to use i386 > for the restoration purpose and set up a virtualbox in which I more then ten > times tried to rewrite /boot and reboot from pool. Possible results were: > > * instant crash with colorful junk on the screen, just after the wiggling > dash appear - seems like corrupted zfsloader; * refusing to load kernel > showing the error; * lotsa gibberish about forth words unknown - seems like > loader or some config files corrupted. > > Having played for 1 day with the disk I find that amount of luck for me to > boot should be heavy, so I switched virtualbox to amd64 and just after the > first rewrite of /boot system was up and running. > > 1. I used the same FreeBSD version to rewrite the data: > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201004/FreeBSD-8.0-STABLE-201004-amd64-livefs.iso > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201004/FreeBSD-8.0-STABLE-201004-i386-livefs.iso > > > 2. I used the same boot code and haven't changed it. This is what I am confused about. What do you mean by the same 'boot code'? I originally asked if you have the *latest* bootcode installed, but you seem to be giving contradicting answers... You detailed your magic workaround of re-writing data, but you haven't mentioned how you updated your boot code. Could you please report the actual commands that you use to update the boot blocks? Just so we are sure that the problem is indeed present in the latest code. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BEB9327.6040405>