I bought a solid state disk HVD fast and wide 14 us access time 40 Mbytes/s throughput.

I configured the HP3000 979/400 as if it saw a 4 or a 9 Gbytes Seagate drive.  The SSD is actually 5 Gbytes. When the system boots into MPEiX I get the above error.

The ODE RUN MAPPER sees SDS 800S ULTRA SCSI  firmw US0  (from Solid Data).  The unit is plugged into a A28696A full height FW HVD scsi card adapter.

I tried SCSI address 0, 6, 14.  I tried the unit by itself and with a IBM3490E tape drive in daisy chain.  Strange thing is that my cassettes no longer mounts on LDEV 220 and yet that the tape drive used to work before.   The operating system is MPEix 6.0 with PDC 39.43.  I tried rebooting several times, it did not clear the problem. When the disk is not configured in SYSGEN, no errors show up. I tried driver : ST34573WD and ST39173WD.  I did a similar test with a 1 Gbytes (by M-System) solid state disk and driver ST31230N (single ended) and it worked.  On the web site, I got the reference below, but rebooting did not help.


 I would appreciate it any help,
Sincerely,

Jean Huot
Northern Credit Bureaus Inc.
(819) 762-4351
(819) 762-0675 fax


: Just happened to notice our SCSI tape drive (7980SX) is no longer showing up on the system. I went back and checked console messages at boot time and found: 
LLIO Error - subsys: 213, proc num: -49, error_num: -28
Leaving - System I/O configuration.
ERROR - LLIO device configuration error: -11

SYSTEM I/O AT BOOT TIME

The path 10/4/20.9.0 was configured but is not available.

ldev: 1 ST34371W configured available 10/4/24.6.0
ldev: 2 ST34371W configured available 10/4/24.5.0
ldev: 6 HPTCPJD configured available NONE
ldev: 7 HPC1533A configured available 10/4/20.0.0
ldev: 8 Not added to configuration; LLIO device configuration error: -11

A: Bill Cadier replied:

This problem might be described in service request 1653-164749. This SR states that 7980SX's produce this error after a reboot where the system has been powered down. It states that the problem can also occur if the device itself is power cycled if the system is down. Subsequent reboots (with no power cycle) appear to clear up the problem according to the SR.

The problem was resolved by a new rev. of firmware 8.67 and this was back in June of 1998. FYI, the error -28 from procedure -49 is a time-out during device binding.

[Editor's note: I've seen this very same error and can confirm the situation that produces it and that a subsequent reboot clears up the problem.]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *