| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 8565.1 | | SMURF::KNIGHT | Fred Knight | Thu Jan 23 1997 16:49 | 9 |
| 8565.2 | scu output | GEMEVN::CSIKESZ | | Fri Jan 24 1997 10:08 | 8 |
| Following your instructions about scu ...
gypsy.zko.dec.com> /sbin/scu
scu> set nexus bus 0 target 5 lun 0
scu: [0/5/0] CAM CCB function 'XPT_GDEV_TYPE' failed,
CAM status = CAM_DEV_NOT_THERE (0x8) - Device not installed/there
scu: 'get device type' failed, EIO (5) - I/O error
scu>
|
| 8565.3 | It's broken | SMURF::KNIGHT | Fred Knight | Fri Jan 24 1997 19:33 | 5 |
| Sure looks broken to me. Make sure the console
can see it (and if it can't, start checking/replacing
cables or the drive itself).
Fred
|
| 8565.4 | Checking console | GEMEVN::CSIKESZ | | Thu Jan 30 1997 15:43 | 9 |
|
Fred,
You suggest ..
"Make sure the console can see it, and if it can't ..."
How do I make sure the console can see it?
|
| 8565.5 | | netrix.lkg.dec.com::thomas | The Code Warrior | Thu Jan 30 1997 15:46 | 3 |
| >>> show dev
Do you see a RRD??
|
| 8565.6 | Show dev ... | GEMEVN::CSIKESZ | | Fri Jan 31 1997 18:17 | 15 |
| Did I do what you said correctly?
(I did this as myself and as superuser, as well with the same result).
Does this indicate the problem?
What can I tell my sysadmin to do about it?
Thanks,
gypsy.zko.dec.com> /sbin/scu
scu> show dev
scu: All or part of device nexus information (bus/target/lun) is NOT setup!.
scu>
|
| 8565.7 | at >>> | KYOSS1::GREEN | | Mon Mar 10 1997 14:37 | 4 |
| I believe Fred meant to shut down the system and at the >>>
do "show device" you should see a dev dkxx that says it is a RRD
device.
|
| 8565.8 | Cause of Xmcd problems with 4.0b | NNTPD::"[email protected]" | Gary Field | Fri May 09 1997 14:59 | 21 |
| I have investigated the problem with running xmcd on Digital UNIX 4.x and
found that the cause is a bug in the CAM subsystem introduced in 4.x.
xmcd uses the User Agent SCSI passthrough driver to issue commands to the
CDROM
drive. It does this with the DISABLE AUTOSENSE flag set and this is what
triggers the bug. When a command (like eject) causes a CHECK CONDITION
the SIM queue is frozen. If AUTOSENSE is enabled, the SIM queue unfreeze
command works OK, but with AUTOSENSE DISABLED, no more commands can be
sent to that device until the system is rebooted.
I modified a version of os_dec.c that works around this problem by
not setting the AUTOSENSE DISABLE flag and providing a buffer for the
sense data.
I can provide this source file to anyone who wants it.
Eventually, the problem will be fixed in the O/S.
Gary
[Posted by WWW Notes gateway]
|