Typically the format reports the 'driver not available' status when the
disks are not available but the associated
device nodes didn't go offline. You can check 'prtconf -v' output.
The devfs -C command only cleans up the /dev link for already offlined
devices.
I assume that the disks were
Robert Milkowski wrote:
Hello James,
Tuesday, February 26, 2008, 11:27:56 PM, you wrote:
JCM But that doesn't help Robert much, or anybody else who wants
JCM to be able to get the info without having to learn any mdb-fu.
prtconv/mdb is good enough workaround.
JCM It shouldn't be too
David Hollister wrote:
With S10U4+patches, PCIe SAS card, I get:
SAS ?! Can this be a problem ? AFAIK, fcinfo looks
specifically for FC HBA. (In fact it uses
libHBAAPI,
which routes the actual call via /etc/hba.conf)
Odds are that your HBA does not provide a library
For those who have followed up the Solaris iSNS server project,
the server and administration CLI have been integrated to Solaris Nevada
build 77
which will be next openSolaris NWS build.
I have updated the project webpage
http://www.opensolaris.org/os/project/isns with
the latest status.
---BeginMessage---
Fully implemented binaries available to download.
Please refer to the project website for installation directions.
http://opensolaris.org/os/project/isns/
In a nutshell,
- download the tarball and enable SMF service for the iSNS server.
- add RBAC related entries to
For those who are interested in iSNS server project,
the project had been reviewed and was approved as an open case by PSARC.
http://opensolaris.org/os/community/arc/caselog/2006/319/
The server utilizes a SMF service to start/stop, RBAC for access
control. Also an XML schema
is developed for
It looks that the driver doesn't recognize the device with sequence #7
that the upper layer library has quried.
We need to check the state of the device. The sequence number is
assoicated with instance numer of devices
under scsi_vhci. You may check 'prtconf -v' and see the device is in
Leon Koll wrote:
It looks that the driver doesn't recognize the device
with sequence #7
that the upper layer library has quried.
We need to check the state of the device. The
sequence number is
assoicated with instance numer of devices
under scsi_vhci. You may check 'prtconf -v' and
The error may occur in mulple places. Please follow the steps below and
rerun
the failing command. The log contians API layer debug info. If you
send the log I will take a look at it.
1) Add this line to /etc/syslog.conf
*.debugtab char/var/adm/mp-api_debug.log
2) ps -aef | grep syslogd
