Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Mar 2018 06:27:35 -0600 (MDT)
From:      Warren Block <wblock@wonkity.com>
To:        Victor Sudakov <vas@mpeks.tomsk.su>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Solved. Re: Dualboot and ZFS
Message-ID:  <alpine.BSF.2.21.1803210626040.85475@wonkity.com>
In-Reply-To: <20180319025914.GA57490@admin.sibptus.transneft.ru>
References:  <VI1PR02MB12007D071EA5398373D2189CF6EB0@VI1PR02MB1200.eurprd02.prod.outlook.com> <20180115125241.GB60956@admin.sibptus.transneft.ru> <VI1PR02MB1200C7F0066F361E60A6CBEDF6EB0@VI1PR02MB1200.eurprd02.prod.outlook.com> <20180115144747.GA65526@admin.sibptus.transneft.ru> <VI1PR02MB120018D174817F8FFB2981D5F6EB0@VI1PR02MB1200.eurprd02.prod.outlook.com> <20180115151526.GA66342@admin.sibptus.transneft.ru> <a7920f859b666cff48f4f73ee1b2f954@dweimer.net> <20180116034929.GB89443@admin.sibptus.transneft.ru> <20180131082738.GA46395@admin.sibptus.transneft.ru> <547e65d16ef16667f61d88463ca73079@roundcube.fjl.org.uk> <20180319025914.GA57490@admin.sibptus.transneft.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 19 Mar 2018, Victor Sudakov wrote:

> On 2018-01-31 08:27, Victor Sudakov wrote:
>>> My pool works successfully in a bhyve environment, but in VirtualBox
>>> 5.0.14
>>> (to test the real boot sequence) I get this message from zfsboot:
>>>
>>> zfsboot: No ZFS pools located, can't boot
>>>
>>> However, if I boot from LiveCD, the pool is there, it's healthy and
>>> can be imported.
>
> Finally, and thanks to Eugene Grossbein, the problem is solved.
>
> The gist of the problem was the presence of a BSD label in the slice
> where the bootable zfs pool was located. It turns out that zfsboot
> ignores the slice if it finds a BSD label therein. The bootable zpool
> should be directly on the slice (like on da1s1, and not da1s1a).
>
> This means that both zfsboot(8) and the articles in the FreeBSD wiki
> are erroneous because they all suggest "gpart create -s BSD ada0s1" -
> in fact, it's fatal.
>
>
> Below is the final working example:
>
> ================================================
> #!/bin/sh
>
> sysctl kern.geom.debugflags=0x10

Please reconsider doing this without it being required.  It means "allow 
destroying mounted partitions" and is usually not necessary.



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