Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 02 Aug 2013 18:14:16 +0300
From:      Volodymyr Kostyrko <c.kworr@gmail.com>
To:        =?UTF-8?B?xYF1a2FzeiBXxIVzaWtvd3NraQ==?= <lukasz@wasikowski.net>
Cc:        freebsd-fs@freebsd.org, freebsd-stable@freebsd.org
Subject:   Re: ZFS: can't read MOS of pool
Message-ID:  <51FBCCC8.6040805@gmail.com>
In-Reply-To: <51FBC8B3.4010304@wasikowski.net>
References:  <51ED5B69.8050200@wasikowski.net> <51FBC24B.5030609@gmail.com> <51FBC4DC.4090506@wasikowski.net> <51FBC6F1.9030408@gmail.com> <51FBC8B3.4010304@wasikowski.net>

next in thread | previous in thread | raw e-mail | index | archive | help
02.08.2013 17:56, Łukasz Wąsikowski wrote:
>> Can you also try what Trond suggests about boot order? You can also list
>> your boot fs in /boot/loader.conf like
>
> I listed ROOTFS in /boot/loader.conf, didn't helped. I'm using this boot
> order on 20+ boxes and never had any issues with it, but I'll check it
> as I don't have better idea what to do next.

I'm almost out of suggestions...

1. Can you try to removing 'canmount' property from klawisz fs and 
'bootfs' property from pool?

2. Can you try fetching late nexenta or illumos and give your pool a 
full scrub?

3. Can you try disablng/enabling features? I assume you haven't used 
compression and have no snapshots.

>> vfs.root.mountfrom=zfs:klawisz/ROOTFS. Or you can just add this at
>> loader prompt.
>>
>> There's also a ${SRC}/tools/tools/zfsboottest script that can tell you
>> something about booting from your pool.
>
> This tools doesn't compile on 9.2-BETA2 r253884
>
> # cd /usr/src/tools/tools/zfsboottest/ && make
>
> Warning: Object directory not changed from original
> /usr/src/tools/tools/zfsboottest
> ln -sf /usr/src/tools/tools/zfsboottest/../../../sys/i386/include machine
> cc -O1  -I/usr/src/tools/tools/zfsboottest/../../../sys/boot/zfs
> -I/usr/src/tools/tools/zfsboottest/../../../sys/cddl/boot/zfs  -I.
> -fdiagnostics-show-option  -W -Wextra -Wno-sign-compare
> -Wno-unused-parameter  -Werror -std=gnu99 -fstack-protector  -c
> zfsboottest.c
> cc1: warnings being treated as errors
> In file included from
> /usr/src/tools/tools/zfsboottest/../../../sys/cddl/boot/zfs/zfssubr.c:122,
>                   from
> /usr/src/tools/tools/zfsboottest/../../../sys/boot/zfs/zfsimpl.c:38,
>                   from zfsboottest.c:55:
> /usr/src/tools/tools/zfsboottest/../../../sys/cddl/boot/zfs/lz4.c: In
> function 'lz4_decompress':
> /usr/src/tools/tools/zfsboottest/../../../sys/cddl/boot/zfs/lz4.c:45:
> warning: implicit declaration of function 'htonl'
> In file included from zfsboottest.c:55:
> /usr/src/tools/tools/zfsboottest/../../../sys/boot/zfs/zfsimpl.c: In
> function 'spa_status':
> /usr/src/tools/tools/zfsboottest/../../../sys/boot/zfs/zfsimpl.c:817:
> error: 'ZFS_MAXNAMELEN' undeclared (first use in this function)
> /usr/src/tools/tools/zfsboottest/../../../sys/boot/zfs/zfsimpl.c:817:
> error: (Each undeclared identifier is reported only once
> /usr/src/tools/tools/zfsboottest/../../../sys/boot/zfs/zfsimpl.c:817:
> error: for each function it appears in.)
> *** [zfsboottest.o] Error code 1
>
> Stop in /usr/src/tools/tools/zfsboottest.

Ahem, sorry. Never used that.

-- 
Sphinx of black quartz, judge my vow.



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