Very Computer

Trying to make a Solaris 10 router out of Netra AC200 T1.

In a nutshell:
Solaris 10 3/05 Reduced Networking Software Group installed
Right out of the box. No patch clusters yet applied.
Installed the SVM missing pkg SUNWmdu not part of the Group install.
Got the boot disk mirrored/attached/sync'd up. All ok.

To test the the failover I shutdown the system, pull disk number 2 out
and power up.

On boot, the kernel loads, and then I get:

WARNING: md: d102 (Unavailable)
          Error writing ufs log state
          ufs log for / changed state to error
          Please unmount(1M) and run fsck (1M)

panic[cpu0]/thread=180e000: could not install the isa driver
....
syncing files systems ...done

I googled on the "ufs log" error but all I could find where references
to Disksuite for Solaris 7/8, maybe 9 and possibly a patch for it.
Nothing about Solaris 10.

What really irks me is that I practiced SVM for Solaris 10 on an extra
E450 where I could give a rats ass whether it worked or not (of course
it all worked and no problems, recoveries and all!). Now that it is for
real,I get problems. Been pissing away 7+ days on this beast and I need
help!

The AC200 has the latest OBP prom (4.0.17 IIRC) and the latest lom lite
firmware in it.

inetd and svcs looks ok to me. All enabled and not any problems.
I cannot give listsings as it is a work and isolated to a Wyse 60 for a
console.

Quick searching on sunsolve didn't reveal anything specific.
Anyone have some experience on this?

Thanks.
-Roger

Quote:> Trying to make a Solaris 10 router out of Netra AC200 T1.

> In a nutshell:
> Solaris 10 3/05 Reduced Networking Software Group installed
> Right out of the box. No patch clusters yet applied.
> Installed the SVM missing pkg SUNWmdu not part of the Group install.
> Got the boot disk mirrored/attached/sync'd up. All ok.

> To test the the failover I shutdown the system, pull disk number 2 out
> and power up.

> On boot, the kernel loads, and then I get:

> WARNING: md: d102 (Unavailable)
>           Error writing ufs log state
>           ufs log for / changed state to error
>           Please unmount(1M) and run fsck (1M)

This might be related:

Bug ID 6215065.

One of the SVM people suggested disabling ufs logging (remove 'logging'
from /etc/vfstab) for only the / filesystem, if my recollection is correct.

I don't think there's a patch for it yet to fully fix that problem.

I ran into the same thing during my Sol10/x86 SVM testing, too. ;)

I then found comments by Jerry Jelinek about that bug and I can tell you
his suggested workaround did indeed avoid this panic.

-Dan

I stumbled upon that "solution" also, but forgot all about it when
writing the post. UFS logging is on by default on in Solaris 10. I did a
"nologging" in vfstab and got the same thing. But know I see I had the
wrong syntax for that test. Ugh.

Quote:

> I don't think there's a patch for it yet to fully fix that problem.

I'll try a cluster patch. I see the topic was during the timeframe of
March 2005. That's about the release time for the Solaris 3/05 version....

Quote:

> I ran into the same thing during my Sol10/x86 SVM testing, too. ;)

> I then found comments by Jerry Jelinek about that bug and I can tell you
> his suggested workaround did indeed avoid this panic.

This must be it (Jerry Jelinek):
http://forum.sun.com/thread.jspa?threadID=23759&messageID=83728

Quote:> -Dan

Thanks for the tips Dan.