ENTRY_INIT status = -13

[Snell Mills]

I have a 735/125 workstation running 10.20 with two 1GB C2247-012 fwscsi drives as vg00. I want to replace them with a A3353A ST15150WD 4GB drive. I have tried cold installing 10.20 to the A3353A from DAT and installing from a recovery tape made using make_recovery. Everything works fine until the system tries to reboot. Then I get the error;

Failed to initialize fwscsi.6.0
ENTRY_INIT status = -13

then some register dumps.....

The A3353A drive has HP07 firmware and passes a 24hr read/write exercise using STM. It has been configured in another system as a data volume group disk and worked fine.

Thanks for any ideas?

[S.K. Chan]

Code -13 means ..
"A protocol error was encountered on bus during data transfer to/from the target controller or device."

As long as you're not getting a "-4" (which means disk is faulty) you're still ok.

Are you able to interrupt and do a SEARCH and does it show up as bootable device ? If not you probably got cable/connection/termination problem.

[Snell Mills]

The disk shows up in the list of possible boot devices when I interupt the initial search. But does not show up in the list of bootable devices after using the s (seach) command.

[S.K. Chan]

Ok, the only explaination I can offer is that the "search" command will not be able to show the existence of the disk as bootable device if the SCSI controller's address is set to a higher priority than that of the disk.

SCSI priorities (fr highest to lowest) are 7 to 0 and 15 to 8

So if your controller is at say id 10 and your disk is at 6, the "search" can't see it. Is that your case ? Can you try setting the disk's SCSI id to lower priority (eg: 9 or 10) and see if it works.

[Snell Mills]

The controller is at 2/0/7.7.0 and the drive is at 2/0/7.6.0 according to ioscan.

[S.K. Chan]

Emm .. I assumed you have tried the "old-fashion-kick-start" method .. power off the server and all disks for a good 30-60secs, then power on the disks first, wait awhile and then power on the cpu ? In your case I'm assuming the disks are internal.
And if still doesn't work (ie SEARCH can't see it), I would go with "the disk is somewhat bad" even though it is indication a "non-destructive" error status. FYI the other ENTRY_INIT status ..

2 Recoverable Error. The call completed normally and the returned results are valid
0 OK.The call completed normally without error
-2 Nonexistent option. The call did not correspond to implemented options in entry_init
-3 Can not complete call without error. An error of unknown type prevented the call from completing correctly
-4 Unrecoverable Hardware Error. An unrecoverable hardware error has occurred between the processor PDC and IODC on the target controller or device
-5 Unrecoverable data error. ENTRY_INIT encountered an error while transferring data to/from the target controller or device
-6 Illegal device address. The device address supplied to ENTRY_INIT is invalid
-7 Nonexistent device. The device address supplied to ENTRY_INIT is valid, but, the target controller or device is not installed or is not responding
-8 Module/device not ready. The module or device is not ready to be initialized. The target is not ready because it has not completed its power on reset/selftest
-9 Cannot locate a console or boot device. ENTRY_INIT could not locate a console or boot device
-10 Invalid argument. ENTRY_INIT was passed an invalid command
-11 Data buffer too small
-12 Unsupported record size
-13 Protocol Error. A protocol error was encountered on bus during data transfer to/from the target controller or device.

You might want to hang on to this thread till someone else reply.

[Sanjay_6]

Hi,

You are trying to install the OS on a third party disk which is not supported by HP. Or if it an hp supplied disk, it is not supported by the hardware it is connected on.

Look at the thread below for more info on ENTR_INIT erros,

http://us-support3.external.hp.com/cki/bin/doc.pl/sid=7875c0ec051d30cfcc/screen=ckiDisplayDocument?docId=200000058670557

Hope this helps.

Regds

[Snell Mills]

This is an HP disk, model A3353A, made by Seagate, ST15150WD with HP firmware rev HP07. I have a narrow scsi drive, ST15150N, attached to this computer, 735/125, which boots just fine. I have several of these A3353A drive and all behave the same way. Is there a firmware update for the drive which might allow it to be used as a boot disk?

[Sanjay_6]

Hi,

Are you using a wide - narrow converter to use this disk into the system. If not, you can try and get one and can use this disk with the converter on the channel where your working narrow disk is connected.

Hope this helps.

Regds

[Snell Mills]

I am not using a converter. The drive is on the fwscsi bus. I don't really want to buy a converter, only paid $35 for the drive.

[S.K. Chan]

This is what I found out ..

The disk is only supported if you have the HP part has HP firmware on it.

A3353A Seagate SCSI Disk, 4 GB HH 3.5"
Fast/Wide, Vendor ID # ST15150W

Only HP supplied versions of these disks are supported. If you have the Seagate ST15150W with Seagate firmware it is not supported by HP as a boot disk on HP systems.

[Snell Mills]

Yep, this is the HP version, firmware revision HP07.

[Sandip Ghosh]

I don't think your Work station support FWD SCSI Drive. It is working with other drive as a Narrow SCSI Device. But whenever you are taking out other device or try to boot from this device it is not working. You may try with the converter as mentioned by Sanjay. It may work or may not. Try it out.

Sandip

[Snell Mills]

This workstation does support FWD SCSI drives. It boots fine with C2247-012 1GB FWD.