you should be able to find the entire bug and workaround on sunsolve.
Here' the workaround in case you're unable to find it:
"6687203 ssconsole cannot detect 3320/3120 jbod due to ses device seen
as processor device type
On Solaris 10, there is a bug 6635664 which prevents a 3320 jbod or 3120
jbod from being seen.
Bug ID: 6635664 - SES and SCCLI access is lost on SE3120 connected to
Rhea hba's with s10u5 and special Maramba build.
Both sccli and ssconsole need a ses device to see the jbod.
Anyway, the workaround was to do the following:
1. Add one line below into /etc/driver_aliases:
ses "scsiclass,03"
2. then reboot the machine.
The SES will show up again.
sccli will then be able to see the jbod."
this should allow you to see your JBOD.
The fix for this is schedule to go into 2.5 of the sscs package which is
not yet released.
John-Paul Drawneek wrote on 07/17/09 15:08:
Hi thanks for the reply on this thread.
Where can I find any details on CR 6687203?
Is this fix likely to sovle my problem?
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
