Operating System - Tru64 Unix
1751711 Members
5573 Online
108781 Solutions
New Discussion юеВ

"finder -q" failure file "/tmp/finder.abort" exists

 
SOLVED
Go to solution
Roro_2
Regular Advisor

"finder -q" failure file "/tmp/finder.abort" exists

Hello,

Our cutomer haked to prepare a new disk 18GB (SCSI 68 pins ) with TRU64 Unix 4.0F on Alpha DS10 server.
I connected the disk to KZPCA-AX SCSI card.
When booting from Unix CD , i am getting the following :
----------------------------------------------
>>>show dev
dka0.0.0.12.0 DKA0 IBM DDRS-34560D DC1B
dqb0.0.1.13.0 DQB0 TSSTcorp CD-R/RW SH-R522C TS03
dva0.0.0.0.0 DVA0
ewa0.0.0.9.0 EWA0 00-10-64-30-4C-1E
ewb0.0.0.11.0 EWB0 00-10-64-30-4C-1C
pka0.7.0.12.0 PKA0 SCSI Bus ID 7
>>> b DQB0

Digital UNIX boot - Mon Apr 12 12:39:50 EDT 1999
Loading vmunix ...
Loading at 0xffffffff00000000
Current PAL Revision <0x1005300010162>
Switching to OSF PALcode Succeeded
New PAL Revision <0x100490002015c>
Mapping Image Address Space
Mapping complete
Sizes:
text = 5711664
data = 1789744
bss = 3435216
Starting at 0xffffffff00212580

Alpha boot: available memory from 0x1da0000 to 0x3ff28000
Digital UNIX V4.0F (Rev. 1229); Mon Apr 12 13:33:38 EDT 1999
physical memory = 1024.00 megabytes.
available memory = 994.32 megabytes.
using 1307 buffers containing 10.21 megabytes of memory
emx: dynamic addressing enabled
Firmware revision: 7.3-1
PALcode: Digital UNIX version 1.92-73
AlphaServer DS10 466 MHz
gpc0 at isa0
pci0 at nexus
isa0 at pci0
ace0 at isa0supported; setting console port to 9600 baud
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: 00-10-64-30-4C-1E
tu0: auto negotiation off: selecting 10BaseT (UTP) port: half 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: 00-10-64-30-4C-1C
tu1: auto negotiation off: selecting 10BaseT (UTP) port: half duplex
itpsa0 at pci0 slot 12
IntraServer ROM Version V2.0 (c)1998
ITPSA0: interrupt handler_add failed
hba_dme_attach: (0/n/n) - hba 'itpsa' attach failed.
ccfg_simattach(): SIM Attach Failed, sim_init() reported FAILURE - Retry.
ITPSA: ccfg_simattach error
- Failed to configure device in PCI bus 0, slot 12 with driver itpsa
ata0 at pci0 slot 13
ata0: ACER M1543C
cam_logger: CAM_ERROR packet
cam_logger: bus 0
ata_probe
cntlr already probed
cam_logger: CAM_ERROR packet
cam_logger: bus 0
ata_probe
cntlr already probed diff CSR
ataconfl1: scsi0 on ata0 probe failed
scsi1 at ata0 slot 1
rz8 at scsi1 target 0 lun 0 (LID=0) (TSSTcorpCD-R/RW SH-R522C TS03)
Created FRU table binary error log packet
kernel console: ace0
i2c: Server Management Hardware Present
vm_swap_init: warning /sbin/swapdefault swap device not found
vm_swap_init: swap is set to lazy (over commitment) mode
INIT: SINGLE-USER MODE
Initializing system for Digital UNIX installation. Please wait...
*** Performing CDROM Installation

Loading installation process and scanning system hardware.
Welcome to the DIGITAL UNIX Installation Procedure
This procedure installs DIGITAL UNIX onto your system. You will
be asked a series of system configuration questions. Until you
answer all questions, your system is not changed in any way.
During the question and answer session, you can go back to any
previous question and change your answer by entering: history
You can get more information about a question by entering: help

/isl/Install [ccii_initialize], FATAL ERROR:
"finder -q" failure file "/tmp/finder.abort" exists

The installation procedure failed or was intentionally exited. To restart
the installation, halt and reboot the system or enter: restart
#
----------------------------------------------

Please could someone help me.

Thanks
Roger
5 REPLIES 5
Steven Schweda
Honored Contributor
Solution

Re: "finder -q" failure file "/tmp/finder.abort" exists

How much of this hardware was working before
you started to change things?

What, exactly, did you change?

> [...] TRU64 Unix 4.0F on Alpha DS10 server.
> I connected the disk to KZPCA-AX SCSI card.

Does Tru64 V4.0F know what a KZPCA is? It
looks unhappy:

> itpsa0 at pci0 slot 12
> IntraServer ROM Version V2.0 (c)1998
> ITPSA0: interrupt handler_add failed
> hba_dme_attach: (0/n/n) - hba 'itpsa' attach failed.
> ccfg_simattach(): SIM Attach Failed, sim_init() reported FAILURE - Retry.
> ITPSA: ccfg_simattach error
> - Failed to configure device in PCI bus 0, slot 12 with driver itpsa

Or is this a _generic_ IntraServer card, and
not a genuine DEC/Compaq IntraServer card, so
that it doesn't have the right firmware?

(I know how VMS complains when it sees an
unofficial IntraServer card. I don't know
what Tru64 does, but this looks as if it
might be the Tru64 edition of "I don't like
that card.")

Have you tried a KZPBA? (As I recall, VMS
would work with some generic/other-vendor
KZPBA-like (Qlogic) cards, but Tru64 wanted
a genuine KZPBA, so you'd need a real KZPBA,
too.)
cnb
Honored Contributor

Re: "finder -q" failure file "/tmp/finder.abort" exists

Roger,

If you have a true 3X-KZPCA-AA with Alpha Firmware, then you need the required patches for 4.0F:

http://h18000.www1.hp.com/alphaserver/options/asds10/asds10_3x-kzpca-aa.html

http://www13.itrc.hp.com/service/patch/tru64AggrKitPage.do?BC=main|tru64AggrIndexPage|&aggrId=DUV40FB22AS0008-20030730

There are other versions of this card with firmware that won't work in this system. So you'll need to verify the exact part number on the module.


Rgds,

Roro_2
Regular Advisor

Re: "finder -q" failure file "/tmp/finder.abort" exists

Hello,

The card is labeled as the following :

P/N KZPCA-AX
S/N CD94703951
REV A01

Regards

Roger
Steven Schweda
Honored Contributor

Re: "finder -q" failure file "/tmp/finder.abort" exists

> P/N KZPCA-AX

That sounds like the real thing. Now all you
need is some software which knows what it is.

I've read about NHD (New Hardware Delivery)
kits (CD-ROM) which provide device support
for older Tru64 versions, but I've never
needed to use one, so I know nothing. (I
never used Tru64 V4.x, either.) Does that
patch kit include any useful instructions for
this situation?
Pieter 't Hart
Honored Contributor

Re: "finder -q" failure file "/tmp/finder.abort" exists

like Steven allready said : "Does Tru64 V4.0F know what a KZPCA is?"

Even Tru64 V5.1 OS CD won't recognize the DS10 controler by itself, and you must boot from the NHD CD!
This CD will make a preinistall disk with OS and additional drivers for the DS10 and controler.
If it also works with V4.0F I cannot say.
This you'll have to try yourself.