Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Sep 2014 22:26:24 +0300
From:      Kimmo Paasiala <kpaasial@icloud.com>
To:        Steven Hartland <killing@multiplay.co.uk>
Cc:        "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Subject:   Re: ZFS on root booting broken somewhere after r270020
Message-ID:  <9315C209-701A-49EF-85D3-ACCCD1513EC3@icloud.com>
In-Reply-To: <CC276D59-F83C-4C78-BD9B-84040D3DE3E4@icloud.com>
References:  <51AD1F36-1089-481F-8784-8BD8E6EF020F@icloud.com> <71DEB316-3CDD-4403-A397-BCE684725ABD@icloud.com> <25886C53-39C1-47A8-95F7-494FA6E7ABA2@icloud.com> <20140819071045.GS2737@kib.kiev.ua> <99FB0662-1954-4ECB-939B-06D0AA49C1A1@icloud.com> <20140819074643.GU2737@kib.kiev.ua> <FE64613E-B083-436C-8A08-13923ED88797@icloud.com> <7F008C560B48412AB66A1EBD9382DDAE@multiplay.co.uk> <CC276D59-F83C-4C78-BD9B-84040D3DE3E4@icloud.com>

next in thread | previous in thread | raw e-mail | index | archive | help

> On 9.9.2014, at 19.03, Kimmo Paasiala <kpaasial@icloud.com> wrote:
>=20
>=20
>> On 9.9.2014, at 18.53, Steven Hartland <killing@multiplay.co.uk> =
wrote:
>>=20
>> ----- Original Message ----- From: "Kimmo Paasiala" =
<kpaasial@icloud.com>
>>> Hi it=E2=80=99s me again. Something that was committed in stable/10 =
after r271213 up to
>>> and including r271288 broke ZFS on Root booting in exactly the same =
way again.
>>> I know the problem is no longer related to extra kernel modules =
loaded in
>>> /boot/loader.conf because I=E2=80=99m loading only the required =
zfs.ko and opensolaris.ko
>>> modules. Also, the new vt(4) console that I=E2=80=99m using is not =
the culprit because the
>>> same thing happens with kern.vty set to =E2=80=9Csc=E2=80=9D.
>>=20
>> I've just updated my stable/10 box to r271316 and no problems booting =
from a ZFS root.
>>=20
>> So first things first what error are you seeing?
>>=20
>> Next what is you're:
>> * Hardware
>> * Pool layout
>>=20
>>  Regards
>>  Steve=20
>=20
> The error is the same as before:
>=20
> 	=E2=80=A2 Mounting from zfs:rdnzltank/ROOT/default failed with =
error 5.
>=20
> Followed by the mountroot prompt and I get only these devices to =
choose from, no sign of the ZFS pool:
>=20
> 	=E2=80=A2 mountroot>
> 	=E2=80=A2 List of GEOM managed disk devices:
> 	=E2=80=A2   gpt/fb10disk1 gpt/fb10swap1 =
diskid/DISK-S13UJDWS301624p3 diskid/DISK-S13UJDWS301624p2 =
diskid/DISK-S13UJDWS301624p1 ada0p3 ada0p2 ada0p1 =
diskid/DISK-S13UJDWS301624 ada0
>=20
> Hardware is a Gigabyte GA-D510UD Mini-ITX motherboard:
>=20
> http://www.gigabyte.com/products/product-page.aspx?pid=3D3343#ov
>=20
> 4GBs of RAM. One 750GB Samsung HD753LJ 3.5=E2=80=9D SATA HD on the =
Intel SATA controller.
>=20
> Pool layout:
>=20
> pool: rdnzltank
> state: ONLINE
>  scan: scrub repaired 0 in 1h7m with 0 errors on Wed Aug 20 09:27:48 =
2014
> config:
>=20
>        NAME             STATE     READ WRITE CKSUM
>        rdnzltank        ONLINE       0     0     0
>          gpt/fb10disk1  ONLINE       0     0     0
>=20
> errors: No known data errors
>=20
> Output of =E2=80=98gpart show=E2=80=99:
>=20
> freebsd10 ~ % gpart show   =20
> =3D>        34  1465146988  ada0  GPT  (699G)
>          34        2014        - free -  (1.0M)
>        2048        1024     1  freebsd-boot  (512K)
>        3072        1024        - free -  (512K)
>        4096    16777216     2  freebsd-swap  (8.0G)
>    16781312  1448365710     3  freebsd-zfs  (691G)
>=20
>=20
> HTH,
>=20
> -Kimmo


More information. This version still works:

FreeBSD freebsd10.rdnzl.info 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 =
r271237: Wed Sep 10 11:00:15 EEST 2014     =
root@buildstable10amd64.rdnzl.info:/usr/obj/usr/src/sys/GENERIC  amd64

The next higher version r271238 breaks booting for me. The commit in =
question is this one:

=
http://svnweb.freebsd.org/base?view=3Drevision&sortby=3Drev&sortdir=3Ddown=
&revision=3D271238

-Kimmo




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9315C209-701A-49EF-85D3-ACCCD1513EC3>