scsi2: SCSI Error for target 1 sist0 - while Installing Tr64 5.1B system

[Jorge Zacarias_1]

Hi All,

I'm trying to start a Tru64 5.1B full installation on a DS10 Alphaserver. Just right on the boot from the installation CD a get some SCSI errors (check output). Does anybody has some ideas to resolve this? Thanks for your answers and help.

Jorge

>>>boot DQA0
(boot dqa0.0.0.13.0)
block 0 of dqa0.0.0.13.0 is a valid boot block
reading 15 blocks from dqa0.0.0.13.0
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 1e00(7680)
initializing HWRPB at 2000
initializing page table at 3ff2a000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

UNIX boot - Wednesday October 16, 2002

Loading vmunix ...
Loading at 0xffffffff00000000

Sizes:
text = 7922752
data = 2044560
bss = 2433008
Starting at 0xffffffff00011d70

bcm: DEGXA driver V1.0.6 NUMA lanlog
failed configuring ev7_ocla subsystem
Alpha boot: available memory from 0x290a000 to 0x3ff28000
Compaq Tru64 UNIX V5.1B (Rev. 2650); Wed Oct 16 17:45:54 EDT 2002
physical memory = 1024.00 megabytes.
available memory = 982.11 megabytes.
using 1289 buffers containing 10.07 megabytes of memory
Firmware revision: 7.2-1
PALcode: UNIX version 1.92-73
AlphaServer DS10 617 MHz
pci0 (primary bus:0) at nexus
isa0 at pci0
gpc0 at isa0
gpc1 not probed
Baud 0 is unsupported; setting console port to 9600 baud
ace0 at isa0
ace1 at isa0
lp0 at isa0
fdi0 at isa0
fd0 at fdi0 unit 0
tu0: DECchip 21143: Revision: 4.1
tu0: auto negotiation capable device
tu0 at pci0 slot 9
tu0: DEC TULIP (10/100) Ethernet Interface, hardware address: 08-00-2B-87-14-85
tu0: auto negotiation off: selecting 100BaseTX (UTP) port: full duplex
tu1: DECchip 21143: Revision: 4.1
tu1: auto negotiation capable device
tu1 at pci0 slot 11
tu1: DEC TULIP (10/100) Ethernet Interface, hardware address: 08-00-2B-87-14-86
tu1: auto negotiation off: selecting 100BaseTX (UTP) port: full duplex
ata0 at pci0 slot 13
ata0: ACER M1543C
scsi0 at ata0 slot 0 rad 0
scsi1 at ata0 slot 1 rad 0
itpsa0 at pci0 slot 15
IntraServer ROM Version V2.0 (c)1998
scsi2: SCSI Error for target 1 sist0 = 0x4
cam_logger: SCSI event packet
cam_logger: bus 2
itpsa SCSI HBA
SCSI Error for target 1 sist0 = 0x4

scsi2: SCSI Error for target 1 sist0 = 0x4
cam_logger: SCSI event packet
cam_logger: bus 2
itpsa SCSI HBA
SCSI Error for target 1 sist0 = 0x4

ITPSA: SCSIError found inactive request for BA 0xc0013e90
scsi2: SCSI Error for target 1 sist0 = 0x4
cam_logger: SCSI event packet
cam_logger: bus 2
itpsa SCSI HBA
SCSI Error for target 1 sist0 = 0x4

ITPSA: SCSIError found inactive request for BA 0xc0013e90
scsi2: SCSI Error for target 1 sist0 = 0x4
cam_logger: SCSI event packet
cam_logger: bus 2
itpsa SCSI HBA
SCSI Error for target 1 sist0 = 0x4

ITPSA: scsi2: SCSI Error for target 1 sist0 = 0x4
cam_logger: SCSI event packet
cam_logger: bus 2
itpsa SCSI HBA
SCSI Error for target 1 sist0 = 0x4

[Steven Schweda]

So, what's at SCSI ID 1 on the IntraServer
SCSI adapter? (And what happens if you
unplug it?)

[Jorge Zacarias_1]

Thank you for your answer Steven,

Iâ m not sure but I think is the PCI-to Ultra2 SCSI host adapter.

My system has 2 72.8 GB Ultra320 SCSI disk, 1 PCI to Ultra2 SCSI host adapter, 2 network interfaces and 1 CD-ROM. This is the output of the verify command using my firmware CD

***** Loadable Firmware Update Utility *****
------------------------------------------------------------------------------
Function Description
------------------------------------------------------------------------------
Display Displays the system's configuration table.
Exit Done exit LFU (reset).
List Lists the device, revision, firmware name, and update revision.
Readme Lists important release information.
Update Replaces current firmware with loadable data image.
Verify Compares loadable and hardware images.
? or Help Scrolls this function table.
------------------------------------------------------------------------------

UPD> verify

nt Verifying 5.71... PASSED.
srm Verifying 7.2-1... PASSED.

UPD> display
AlphaServer DS10 617 MHz

SRM Console: V7.2-2
PALcode: OpenVMS PALcode V1.98-83, Tru64 UNIX PALcode V1.92-73

Processors
CPU 0 Alpha EV67 pass 2.2.3 617 MHz
SROM Revision: V1.18.208
Bcache size: 2 MB

Core Logic
Cchip DECchip 21272-CA Rev 2
Dchip DECchip 21272-DA Rev 2
Pchip 0 DECchip 21272-EA Rev 2

TIG Rev 2.1
Arbiter Rev 7.30 (0xfe)

MEMORY

Array # Size Base Addr
------- ---------- ---------
0 1024 MB 000000000

Total Bad Pages = 0
Total Good Memory = 1024 MBytes


PCI Hose 00
Bus 00 Slot 01: Acer Labs M1543C USB
Bus 00 Slot 07: Acer Labs M1543C
Bridge to Bus 1, ISA
Bus 00 Slot 09: DE500-BA Network Controller
ewa0.0.0.9.0 08-00-2B-87-14-85
Bus 00 Slot 11: DE500-BA Network Controller
ewb0.0.0.11.0 08-00-2B-87-14-86
Bus 00 Slot 13: Acer Labs M1543C IDE
dqa.0.0.13.0
dqa0.0.0.13.0 CD-224E
Bus 00 Slot 15: NCR 53C895
pka0.7.0.15.0 SCSI Bus ID 7
dka0.0.0.15.0 COMPAQ BD07285A25
dka100.1.0.15.0 COMPAQ BD072863B2


ISA
Slot Device Name Type Enabled BaseAddr IRQ DMA
0
0 MOUSE Embedded Yes 60 12
1 KBD Embedded Yes 60 1
2 COM1 Embedded Yes 3f8 4
3 COM2 Embedded Yes 2f8 3
4 LPT1 Embedded Yes 3bc 7
5 FLOPPY Embedded Yes 3f0 6 2

UPD>

[Steven Schweda · Accepted solution]

I'd expect "show config" at the console
prompt (">>>") to give you similar info --
no CD required. But anyway, ...

Ok. That looks like the only (real) SCSI
adapter ("scsi0" and "scsi1" being the
IDE/ATA interfaces), so "dka100.1.0.15.0
COMPAQ BD072863B2" would be the device at ID
("target") 1, and that's the one which seems
to be causing all the complaints.

Are there valuable data on the disks, or were
you planning to overwrite them? If the plan
was to do a clean install of Tru64 on dka0,
I'd probably just go ahead and do that.
Then, assuming that that goes well, I'd try a
few more diagnostic things with dka100.
Assuming that the cables are ok, the
terminator didn't get eaten by a fan, and so
on, I'd suspect that second disk drive.

If you start seeing complaints about the disk
at ID ("target") 0 (dka0), then I'd think
again.

[Jorge Zacarias_1]

OK Steven,

The machine is a new purchase so there are no data on the disks.
OK, I'll do the tests, check the cables, terminators and will do a test just unplugging the disk dka100.
I'll get back to you after my tests.

Thanks

[Jorge Zacarias_1]

Thank's for your help. Installation was able to start after checking the connectors, terminators and unplug and plug the scsi disks. There was something loose somewhere.