zfs discuss - Sep 2010 - onnv_142 - vfs_mountroot: cannot mount root

Hi,

After upgrade from snv_138 to snv_142 or snv_145 I''m unable to boot the
system.
Here is what I get.

Any idea why it''s not able to import rpool?

I saw this issue also on older builds on a different machines.

-- 
Piotr Jasiukajtis | estibi | SCA OS0072
http://estseg.blogspot.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: onnv_142_kmdb_msgbuf.png
Type: image/png
Size: 109042 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100907/6859fa88/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: onnv_142_kmdb_01.png
Type: image/png
Size: 63959 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100907/6859fa88/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: onnv_142_kmdb_02.png
Type: image/png
Size: 75937 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100907/6859fa88/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: onnv_142_kmdb_03.png
Type: image/png
Size: 87729 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100907/6859fa88/attachment-0007.png>

Did you run installgrub before rebooting?

On Tue, 7 Sep 2010, Piotr Jasiukajtis wrote:
> Hi,
>
> After upgrade from snv_138 to snv_142 or snv_145 I''m unable to
boot the system.
> Here is what I get.
>
> Any idea why it''s not able to import rpool?
>
> I saw this issue also on older builds on a different machines.
>
> --
> Piotr Jasiukajtis | estibi | SCA OS0072
> http://estseg.blogspot.com
>

On 07.09.10 17:26, Piotr Jasiukajtis wrote:
> Hi,
> 
> After upgrade from snv_138 to snv_142 or snv_145 I''m unable to
boot the system.
> Here is what I get.
> 
> Any idea why it''s not able to import rpool?
Provided output tells that it was able to read device labels, construct 
configuration and add it into spa namespace, but then spa_open() called as part 
of bootfs property processing returned EINVAL.

I think you can step through spa_open() to find out where exactly and why.

for that you''ll have to place a breakpoint in rootconf() somewhere
close but
before call to vfs_mountroot() and continue, and when it stops in rootconf() 
you''ll be able to set another breakpoint(s) anywhere you like in the
ZFS code.

regards
victor

> 
> I saw this issue also on older builds on a different machines.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> 
> ------------------------------------------------------------------------
> 
> 
> ------------------------------------------------------------------------
> 
> 
> ------------------------------------------------------------------------
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

-- 
--
Victor Latushkin                   phone: x11467 / +74959370467
TSC-Kernel EMEA                    mobile: +78957693012
Sun Services, Moscow               blog: http://blogs.sun.com/vlatushkin
Sun Microsystems

On 09/07/10 23:26, Piotr Jasiukajtis wrote:
> Hi,
>
> After upgrade from snv_138 to snv_142 or snv_145 I''m unable to
boot the system.
> Here is what I get.
>
> Any idea why it''s not able to import rpool?
>
> I saw this issue also on older builds on a different machines.
This sounds (based on the presence of cpqary) not unlike:

6972328 Installation of snv_139+ on HP BL685c G5 fails due to panic during auto
install process

which was introduced into onnv_139 by the fix for this

6927876 For 4k sector support, ZFS needs to use DKIOCGMEDIAINFOEXT

The fix is in onnv_148 after the external push switch-off, fixed via

6967658 sd_send_scsi_READ_CAPACITY_16() needs to handle SBC-2 and SBC-3 response
formats

I experienced this on data pools rather than the rpool, but I suspect on the
rpool
you''d get the vfs_mountroot panic you see when rpool import fails.  My
workaround
was to compile a zfs with the fix for 6927876 changed to force the default
physical block size of 512 and drop that into the BE before booting to it.
There was no simpler workaround available.

Gavin

Hi,

The issue here was using DKIOCGMEDIAINFOEXT by ZFS introduced in
changeset 12208.
Forcing DKIOCGMEDIAINFO solved that.

On Tue, Sep 7, 2010 at 4:35 PM, Gavin Maltby <gavin.maltby at oracle.com>
wrote:
> On 09/07/10 23:26, Piotr Jasiukajtis wrote:
>>
>> Hi,
>>
>> After upgrade from snv_138 to snv_142 or snv_145 I''m unable to
boot the
>> system.
>> Here is what I get.
>>
>> Any idea why it''s not able to import rpool?
>>
>> I saw this issue also on older builds on a different machines.
>
> This sounds (based on the presence of cpqary) not unlike:
>
> 6972328 Installation of snv_139+ on HP BL685c G5 fails due to panic during
> auto install process
>
> which was introduced into onnv_139 by the fix for this
>
> 6927876 For 4k sector support, ZFS needs to use DKIOCGMEDIAINFOEXT
>
> The fix is in onnv_148 after the external push switch-off, fixed via
>
> 6967658 sd_send_scsi_READ_CAPACITY_16() needs to handle SBC-2 and SBC-3
> response formats
>
> I experienced this on data pools rather than the rpool, but I suspect on
the
> rpool
> you''d get the vfs_mountroot panic you see when rpool import fails.
?My
> workaround
> was to compile a zfs with the fix for 6927876 changed to force the default
> physical block size of 512 and drop that into the BE before booting to it.
> There was no simpler workaround available.
>
> Gavin
>


-- 
Piotr Jasiukajtis | estibi | SCA OS0072
http://estseg.blogspot.com