ZFS on root booting broken somewhere after r270020
Steven Hartland
killing at multiplay.co.uk
Wed Sep 10 22:36:56 UTC 2014
----- Original Message -----
From: "Kimmo Paasiala" <kpaasial at icloud.com>
To: "Steven Hartland" <killing at multiplay.co.uk>
Cc: <freebsd-stable at freebsd.org>
Sent: Wednesday, September 10, 2014 8:26 PM
Subject: Re: ZFS on root booting broken somewhere after r270020
>
>> On 9.9.2014, at 19.03, Kimmo Paasiala <kpaasial at icloud.com> wrote:
>>
>>
>>> On 9.9.2014, at 18.53, Steven Hartland <killing at multiplay.co.uk> wrote:
>>>
>>> ----- Original Message ----- From: "Kimmo Paasiala" <kpaasial at icloud.com>
>>>> Hi it’s 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’m loading only the required zfs.ko and opensolaris.ko
>>>> modules. Also, the new vt(4) console that I’m using is not the culprit because the
>>>> same thing happens with kern.vty set to “sc”.
>>>
>>> I've just updated my stable/10 box to r271316 and no problems booting from a ZFS root.
>>>
>>> So first things first what error are you seeing?
>>>
>>> Next what is you're:
>>> * Hardware
>>> * Pool layout
>>>
>>> Regards
>>> Steve
>>
>> The error is the same as before:
>>
>> • Mounting from zfs:rdnzltank/ROOT/default failed with error 5.
>>
>> Followed by the mountroot prompt and I get only these devices to choose from, no sign of the ZFS pool:
>>
>> • mountroot>
>> • List of GEOM managed disk devices:
>> • gpt/fb10disk1 gpt/fb10swap1 diskid/DISK-S13UJDWS301624p3 diskid/DISK-S13UJDWS301624p2 diskid/DISK-S13UJDWS301624p1 ada0p3
>> ada0p2 ada0p1 diskid/DISK-S13UJDWS301624 ada0
>>
>> Hardware is a Gigabyte GA-D510UD Mini-ITX motherboard:
>>
>> http://www.gigabyte.com/products/product-page.aspx?pid=3343#ov
>>
>> 4GBs of RAM. One 750GB Samsung HD753LJ 3.5” SATA HD on the Intel SATA controller.
>>
>> Pool layout:
>>
>> pool: rdnzltank
>> state: ONLINE
>> scan: scrub repaired 0 in 1h7m with 0 errors on Wed Aug 20 09:27:48 2014
>> config:
>>
>> NAME STATE READ WRITE CKSUM
>> rdnzltank ONLINE 0 0 0
>> gpt/fb10disk1 ONLINE 0 0 0
>>
>> errors: No known data errors
>>
>> Output of ‘gpart show’:
>>
>> freebsd10 ~ % gpart show
>> => 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)
>>
>>
>> HTH,
>>
>> -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 at 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=revision&sortby=rev&sortdir=down&revision=271238
Investigating, had no reports of issues while this has been in head.
Regards
Steve
More information about the freebsd-stable
mailing list