Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Dec 2013 10:13:30 -0800
From:      Artem Belevich <art@freebsd.org>
To:        Andriy Gapon <avg@freebsd.org>
Cc:        freebsd-fs <freebsd-fs@freebsd.org>, freebsd-stable stable <freebsd-stable@freebsd.org>, Florent Peterschmitt <florent@peterschmitt.fr>
Subject:   Re: 10.0-BETA4 (upgraded from 9.2-RELEASE) zpool upgrade -> boot failure
Message-ID:  <CAFqOu6g1ih3Z70Z4gip0BowmSAJ6dE4X8WgR0au1Rx5udmtZXw@mail.gmail.com>
In-Reply-To: <52A9ABEF.8080509@FreeBSD.org>
References:  <52A6EB67.3000103@peterschmitt.fr> <52A99917.2050200@FreeBSD.org> <52A9AA45.2000907@peterschmitt.fr> <52A9ABEF.8080509@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 12, 2013 at 4:28 AM, Andriy Gapon <avg@freebsd.org> wrote:
>> Yes, sorry. You can find here the script I use to install:
>>
>> https://github.com/Leryan/freebsd-zfs-install/blob/master/zfs.sh
>>

>From zfs.sh:
># Zero ZFS sectors
>dd if=/dev/zero of=/dev/${ada}p3 count=560 bs=512

That destroys only half of ZFS uberblocks. The other half is placed at
the top of the vdev slices in the pool.
There were few reports recently that such 'orphan' ZFS uberblocks were
messing up boot on recent FreeBSD versions.

Considering lack of details on how exactly your boot fails, this may
or may not be the issue in your case.

do  "zdb -l /dev/ada0" (and all other slices on ada0) and check
whether it reports anything unexpected.

--Artem



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFqOu6g1ih3Z70Z4gip0BowmSAJ6dE4X8WgR0au1Rx5udmtZXw>