On Thu, May 21, 2009 at 9:46 PM, Sean Sprague <[email protected]> wrote:
> Hello Martin,
>
>> Hello Sean,
>>
>> this is a known bug since 3 weeks.
>> Please see more information below.
>
> I don't think this is related to my panic, as it doesn't appear to relate to
> ZFS root at boot time. Also my panic happens on raw tin, thus ruling out
> Virtualbox.
>
> Thanks anyways; and regards... Sean.
>


Sorry Sean, I only saw snv_114 + VirtualBox and the red  ...
So I did not even read the backtrace and just responded in a hurry.

What I can tell you: I'm successfully using SXCE snv_114 with ZFS root
on external USB2 Enclosure with USB2 <--> Sata_II bridge on a Laptop
(real hardware).

Works well for me, my config.


$ df -h
Filesystem             size   used  avail capacity  Mounted on
rpool__SXCE__snv_114/ROOT/snv_114
                       914G   9.9G   288G     4%    /
/devices                 0K     0K     0K     0%    /devices
/dev                     0K     0K     0K     0%    /dev
ctfs                     0K     0K     0K     0%    /system/contract
proc                     0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
swap                   7.6G   444K   7.6G     1%    /etc/svc/volatile
objfs                    0K     0K     0K     0%    /system/object
sharefs                  0K     0K     0K     0%    /etc/dfs/sharetab
/usr/lib/libc/libc_hwcap2.so.1
                       298G   9.9G   288G     4%    /lib/libc.so.1
fd                       0K     0K     0K     0%    /dev/fd
swap                   7.8G   191M   7.6G     3%    /tmp
swap                   7.6G    48K   7.6G     1%    /var/run
rpool__SXCE__snv_114/export
                       914G    23K   288G     1%    /export
rpool__SXCE__snv_114/export/home
                       914G   604G   288G    68%    /export/home
rpool__SXCE__snv_114   914G    33K   288G     1%    /rpool__SXCE__snv_114
/dev/dsk/c0t1d0s2      3.3G   3.3G     0K   100%    /media/SOL_11_X86
bash-3.2$ uname -a
SunOS AMILO-Pa3515 5.11 snv_114 i86pc i386 i86pc
bash-3.2$ isainfo -k
amd64


As you see I provided an extra name for the zpool during text mode installation.
So (un)fortunately I cannot reproduce your scenario.
With UFS you would have gotten the same panic if root could not be
mounted (e.g. due to invalid boot device path).
That's the issue, as you said yourself.
The question is to find out _why_.
Is there a mapping for the error code somewhere? What might "error 2" stand for?


Much luck.


--
%martin
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to