System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Tru64 installation fails on DS20L

Steven L Guberman
Occasional Advisor

Tru64 installation fails on DS20L

I am trying to install Tru64 5.1A on a DS20L. The operating system cdrom is in dqb0 and a small 4GB SCSI disk is connected to the motherboard. One of the eleven fans is not working. The boot proceeds to a kn600 message and then stops at the point shown below. When the boot stops on the console screen, the cdrom is active for about another 30 seconds and then it also stops. The boot is shown below:
COMPAQ AlphaServer DS20L 833 MHz Console V5.9-17, Nov 28 2001 09:20:22
P00>>>set boot_file ""
P00>>>b dqb0
(boot dqb0.0.1.16.0 -flags a)
block 0 of dqb0.0.1.16.0 is a valid boot block
reading 15 blocks from dqb0.0.1.16.0
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 1e00
initializing HWRPB at 2000
initializing page table at 3ff48000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

UNIX boot - Wednesday August 01, 2001

Loading vmunix ...
Loading at 0xffffffff00000000

Sizes:
text = 7074304
data = 1718352
bss = 2258496
Starting at 0xffffffff000104c0

kn600_get_func_supported(): Unrecognized KN600 member_id: 0xc
Forcing defaults:
Power Management not supported
Server Management not supported
4 PCI busses configured
Alpha boot: available memory from 0x2038000 to 0x3ff46000
Compaq Tru64 UNIX V5.1A (Rev. 1885); Wed Aug 1 15:16:14 EDT 2001
physical memory = 1024.00 megabytes.
available memory = 991.05 megabytes.
using 1290 buffers containing 10.07 megabytes of memory

The boot does not continue beyond here. Any suggestions on what is wrong?
24 REPLIES
Hein van den Heuvel
Honored Contributor

Re: Tru64 installation fails on DS20L

I would first upgrade the firmware to something from this century. Why not 7.3 ?

I could not readily find a minimum firmware version for v5.1A. The installation guide points to the release notes. The release notes just mention 'use the CD that came with the OS' and point to an FTP side which does not work.

If that does not do it, check for the exact option placement and versions.
P00>> SHOW CONFIG
and/or SHOW FRU


The kn600 was a message documented to be ignored for Tru64 4.0G... One would think that would have been fixed by 5.1A:
Search for kn600 in:
http://h18002.www1.hp.com/alphaserver/download/ds20e_gr_rn_b02.pdf

ftp://ftp.hp.com/pub/alphaserver/firmware/current_platforms/v7.3_release/DOC/ds20_v73_fw_relnote.pdf


Good luck!
Hein.
Steven L Guberman
Occasional Advisor

Re: Tru64 installation fails on DS20L

Thanks for the response. Below is the output of sh fru and sh config. I have tried to update the firmware on this machine. However, this is not a trivial task. The firmware for the ds20L is not on the firmware CD that comes with Tru64 5.1A. (The ds20L is not the ds20 or ds20e.) One can download from HP a *.exe file for the ds20L but my understanding is that this can only be used via bootp and a RIS server. While I have other Tru64 machines, I do not currently have a unix-server license needed to set up the RIS server. I have tried downloading the v73.iso file and burning it to a cdrom on a pc. However, booting from the cd gives the message:"block 0 of dqa0.0.0.16.0 is not a valid boot block."

The minimum firmware table that I have seen indicates that the 5.9 firmware is OK for Tru64 5.1a. However, the boot shown in my prior message stops just at the point at which the firmware is read. So installing new firmware is a good idea but how is it done?
There is a users guide for this machine,DS20L.ek-ds20l-ug-b01.pdf, but it does not mention of kn600.

P00>>>sh fru
FRUname E Part# Serial# Model/Other Alias/Misc
SMB0 00
SMB0.CPU0 00 API Unknown Slot B Mod Alpha Proc
SMB0.CPU0.FAN 00 - CPU Fan
SMB0.CPU1 00 API Unknown Slot B Mod Alpha Proc
SMB0.CPU1.FAN 00 - CPU Fan
P00>>>sh config
COMPAQ AlphaServer DS20L 833 MHz

SRM Console: V5.9-17
PALcode: OpenVMS PALcode V1.90-71, Tru64 UNIX PALcode V1.86-68

Processors
CPU 0 Alpha 21264B-4 833 MHz (EV68A pass 2.2)SROM Revision: V3
Bcache size: 4 MB

CPU 1 Alpha 21264B-4 833 MHz (EV68A pass 2.2)SROM Revision: V3
Bcache size: 4 MB

Core Logic
Cchip DECchip 21272-CA Rev 2.1
Dchip DECchip 21272-DA Rev 2.0
Pchip 0 DECchip 21272-EA Rev 2.2
Pchip 1 DECchip 21272-EA Rev 2.2

TIG Rev 4.15
Arbiter Rev 2.8 (0x1)
Power EPLD Rev 9
Reset EPLD Rev 1

MEMORY

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

Total Bad Pages = 0
Total Good Memory = 1024 MBytes


PCI Hose 00
Bus 00 Slot 03: SYM 53C1000
pka0.7.0.3.0 SCSI Bus ID 7
dka0.0.0.3.0 RZ1CC-BA
Bus 00 Slot 04: Intel 8255x Ethernet
eib0.0.0.4.0 00-02-56-00-17-78
Bus 00 Slot 07: Acer Labs M1543C
Bridge to Bus 1, ISA
Bus 00 Slot 16: Acer Labs M1543C IDE
dqa.0.0.16.0
dqa0.0.0.16.0 TOSHIBA CD-ROM XM-61
dqb0.0.1.16.0 CD-224E
Bus 00 Slot 17: Acer Labs M1543C PMU


PCI Hose 01
Bus 00 Slot 03: Intel 8255x Ethernet
eia0.0.0.3.1 00-02-56-00-17-79


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

6 EIDE Embedded Yes 1f0 14
3f6 15
170
376

7 PWR_MANAGEMENT Embedded Yes
8 USB Embedded No

marsh_1
Honored Contributor

Re: Tru64 installation fails on DS20L

hi,

you could try a ctrl t while the boot is hanging this should give you the background processes going on (have used on ds10, ds20e and es45).

HTH

marsh_1
Honored Contributor

Re: Tru64 installation fails on DS20L

apologies - that probably won't work once the boot has started.
Steven Schweda
Honored Contributor

Re: Tru64 installation fails on DS20L

> I have tried downloading the v73.iso file
> and burning it to a cdrom on a pc.

How, exactly?

> However, booting from the cd gives the
> message:"block 0 of dqa0.0.0.16.0 is not a
> valid boot block."

Sounds like a bad CD image file and/or a bad
disc-writing method. I've heard that some CD
software for Windows thinks that it's smarter
than it really is, and tries to "fix" a disc
image for you according to its own
(imperfect) ideals. I normally use cdrtools
(cdrecord) on a VMS system to do these tasks,
and it works for me.

> So installing new firmware is a good idea
> but how is it done?

I've always used a Firmware Update CD. Never
needed to explore the exotic methods.

> [...] but my understanding is that this can
> only be used via bootp and a RIS server.

I'd not expect that bootp (and, perhaps tftp)
needed any exotic software licenses. RIS?
It's only firmware, not the OS.

I've found a V7.2 Firmware Update CD in my
collection, which also seems to have the
latest (2003-4, V6.6) stuff for a DS20L. I
could supply an image of that, but I don't
see why anything I might supply would work
any better than a disc image from HP.
Perhaps you should look for a "please don't
help me" option in your CD-writing software,
and try that again.
Rob Leadbeater
Honored Contributor

Re: Tru64 installation fails on DS20L

Hi,

The latest available firmware for the DS20L is 6.6, not 7.3.

You can find that here:

ftp://ftp.hp.com/pub/alphaserver/firmware/retired_platforms/servers/DS20L

although it doesn't look like there's an ISO there :-(

You might want to try with the 6.5 ISO which you can find here:

ftp://ftp.hp.com/pub/alphaserver/firmware/iso_images/V65.iso

Cheers,

Rob
Steven Schweda
Honored Contributor

Re: Tru64 installation fails on DS20L

> The latest available firmware for the DS20L
> is 6.6, not 7.3.

But that doesn't mean that the latest (final)
kit for the DS20L is not included on later
Firmware Update CDs. As I said, my V7.2 CD
includes it.

> You might want to try with the 6.5 ISO
> which you can find here:

Why that one, and not one of the post-V6.6
ones (which would be more likely to include
the latest DS20L stuff)?

I'd say that the CD problem probably lies in
the kit download and CD writing methods, not
in the choice of CD image.
Hein van den Heuvel
Honored Contributor

Re: Tru64 installation fails on DS20L

Hmmmm... just found a note on the web which suggests you MUST have an IDE system disk for that box ?!
http://howto.unixdev.net/Tru64-CS20-HOWTO.html
I have attached it here, in case that web page expires.

Hein.

fwiw... Here is the reply I was about to post before seeing that:

The booklet with my firmware CD's suggest that 5.9 is good enough vor Tru64 V5.1a.

The SHOW FRU is not what I expected, but I don't have have a DS20L to compare against.
I'll paste the output from my (running... just hit ^P, SHOW FRU, CONT) DS10 below.

The SHOW CONFIG looks like many I've seen before. I found a very comparable one on the web in Google's cache, looking for:
"COMPAQ AlphaServer DS20L 833 MHz "
http://webserver-1.wescorp.com/wescorp-library/OARS/DISK1/HW/SYS/ALPHA/SRM/DS20L/show.html

That output reminded me about
P00>>> show power [ - verbose ]
That might be interesting.
Also try P00>>> SHOW DEVICE
but I don't expect new insights.

Do you have an old harddrive with OS to try?
An alternative CD to try?
(OpenVMS!?... not supposed to work according to Hoff back in 2005: " The AlphaServer DS20L and the AlphaServer SC20 series are not supported by OpenVMS Alpha, and are similar to the AlphaServer DS20 series boxes in their model names only.
IIRC, the bridge chipset in this box is not supported by OpenVMS Alpha. ")




What is the history of the motherboard?
Did it ever run Tru64 before?
Could there be a obscure console variable set wrong like "console_memory_allocation old/new"
Perhaps attach the output from P00>> SHOW *

Sorry, not much help.
Hein.


>>>show fru
FRUname E Part# Serial# Model/Other Alias/Misc
SMB0 00 ?????????????????? al???_____ ?????????? ??????????
SMB0.PCI1 00 KGPSA-C
SMB0.PCI2 00 NCR 53C895
SMB0.PCI3 00 10268086/1333103C
SMB0.DIMM0 00
SMB0.DIMM1 00
SMB0.DIMM2 00
SMB0.DIMM3 00
PWR0 00 **-*****-** - Power
FAN1 00 12-49806-01 - PCI Fan
FAN2 00 12-24701-35 - System Fan
SMB0.CPU0.FAN 00 12-33279-15 - CPU Fan


Steven L Guberman
Occasional Advisor

Re: Tru64 installation fails on DS20L

I want to thank Hein van den Heuvel, Mark Hunt, Steven Schweda and
Rob Leadbeater for your generosity in suggesting possible solutions. I
have made some progress but the DS20L still does not boot. I have updated the
the firmware to the latest level (6.6) by not using the cd writing software I had
used previously but by using the pc program, Cute CD DVD Burner, which I downloaded from
www.tucows.com. The program handled the v73.iso file correctly and made a bootable
firmware cdrom. (Steve Schweda's suggestion was very helpful on this point).
I have also replaced the inoperative single fan so that all fans are now OK.
The boot shown below is the same as before except that it now ends with
the statement "kn600: Can't allocate error log buffer."

P00>>>b dqb0
(boot dqb0.0.1.16.0 -flags a)
block 0 of dqb0.0.1.16.0 is a valid boot block
reading 15 blocks from dqb0.0.1.16.0
bootstrap code read in
base = 290000, image_start = 0, image_bytes = 1e00(7680)
initializing HWRPB at 2000
initializing page table at 3ffec000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

UNIX boot - Wednesday August 01, 2001

Loading vmunix ...
Loading at 0xffffffff00000000

Sizes:
text = 7074304
data = 1718352
bss = 2258496
Starting at 0xffffffff000104c0

kn600_get_func_supported(): Unrecognized KN600 member_id: 0xc
Forcing defaults:
Power Management not supported
Server Management not supported
4 PCI busses configured
Alpha boot: available memory from 0x203a000 to 0x3ffea000
Compaq Tru64 UNIX V5.1A (Rev. 1885); Wed Aug 1 15:16:14 EDT 2001
physical memory = 1024.00 megabytes.
available memory = 991.68 megabytes.
using 1291 buffers containing 10.08 megabytes of memory
(The boot stops here and then resumes after about 3 minutes with the following
repeated ad infinitum).
kn600: Can't allocate error log buffer

Answer to Hein van den Heuvel:
This ds20L was probably running Tru64 before I started using it since
sysvar was set to 12 (for Tru64). It came with no hard disk or cdrom.
The hard disk that I am using is from an old alphastation. I can boot from that
disk up to "Using xxx buffers ontaining xxx megabytes of memory" at which point
the boot stops with a message indicating that the configuration of the boot disk is inconsistent with that of the ds20L.
I have tried changing some environmental variables in the boot but
nothing has been effective. While sh * lists many variables, it does not appear to
be the complete set so there are probably many that I am not aware of.

Below is output from sh * |more, sh power and sh dev.
P00>>>sh * |more
ac_action BOOT
api_debug 0
auto_action HALT
boot_dev dqb0.0.1.16.0
boot_file
boot_osflags a
boot_reset OFF
bootbios
bootdef_dev dqb0.0.1.16.0
booted_dev
booted_file
booted_osflags
char_set 0
com1_baud 9600
com1_flow SOFTWARE
com1_modem OFF
com2_baud 9600
com2_flow SOFTWARE
com2_modem OFF
console serial
console_memory_allocation new
controlp ON
cpu_enabled 2
d_bell off
d_cleanup on
d_complete off
d_eop off
d_group field
d_harderr halt
d_loghard on
d_logsoft off
d_omit
d_oper on
d_passes 1
d_quick off
d_report full
d_runtime 0
d_softerr continue
d_startup off
d_status off
d_trace off
d_verbose 0
diags_action off
dimm_zmdi 0
dump_dev
eia0_arp_tries 3
eia0_bootp_file ds20l_v6_6.exe
eia0_bootp_server 00:10:64:30:1c:47
eia0_bootp_tries 3
eia0_def_ginetaddr 192.168.123.254
eia0_def_inetaddr 192.168.123.20
eia0_def_inetfile
eia0_def_sinetaddr 192.168.123.70
eia0_def_subnetmask 255.255.255.0
eia0_ginetaddr 0.0.0.0
eia0_inet_init bootp
eia0_inetaddr 0.0.0.0
eia0_inetfile
eia0_loop_count 3e8
eia0_loop_inc a
eia0_loop_patt ffffffffffffffff
eia0_loop_size 2e
eia0_lp_msg_node 1
eia0_mode FastFD (Full Duplex)
eia0_protocols MOP
eia0_sinetaddr 0.0.0.0
eia0_tftp_blocksize 1024
eia0_tftp_tries 3
eib0_arp_tries 3
eib0_bootp_file
eib0_bootp_server
eib0_bootp_tries 3
eib0_def_ginetaddr 0.0.0.0
eib0_def_inetaddr 0.0.0.0
eib0_def_inetfile
eib0_def_sinetaddr 0.0.0.0
eib0_def_subnetmask 0.0.0.0
eib0_ginetaddr 0.0.0.0
eib0_inet_init bootp
eib0_inetaddr 0.0.0.0
eib0_inetfile
eib0_loop_count 3e8
eib0_loop_inc a
eib0_loop_patt ffffffffffffffff
eib0_loop_size 2e
eib0_lp_msg_node 1
eib0_mode FastFD (Full Duplex)
eib0_protocols MOP
eib0_sinetaddr 0.0.0.0
eib0_tftp_blocksize 1024
eib0_tftp_tries 3
enable_audit OFF
ffauto OFF
ffnext OFF
full_powerup_diags OFF
heap_expand NONE
kbd_hardware_type PCXAL
language 36
language_name English (American)
license MU
memory_test full
N1
N2
N3
N4
oem_string
os_type UNIX
page_table_levels 3
pal OpenVMS PALcode V1.98-74, Tru64 UNIX PALcode V1.92-71
pci_parity ON
pka0_disconnect 1
pka0_fast 0
pka0_host_id 7
prompt >>>
reset_boot_arg0
reset_boot_arg1
reset_boot_arg2
scsi_poll ON
scsi_reset ON
srm2ctrl
srm2dev
sys_serial_num 4211KRCZA095
system_monitor OFF
sysvar 12
tt_allow_login 1
tty_dev 0
version V6.6-10 Nov 11 2003 09:10:13
wol_enable ON
wwid0
wwid1
wwid2
wwid3

P00>>>sh power
Processor Module Information

CPU 0 CPU 1 Dimm I/O Riser PSU
Fan1 Status OK OK OK OK OK OK
Fan2 Status OK OK OK OK OK
2.5V OK OK OK
Vccp1 OK OK OK
3.3V OK OK OK OK OK
5.0V OK OK OK OK
12.0V OK OK OK OK OK OK
Vccp2
Temperature 30.00 33.00 43.00 32.00 34.00 38.00
Revision 0x08 0x08 0x05 0x00 0x06 0x0e

Power status: all OK

Dimm 1 2 3 4 5 6 7 8
Megabytes 256 256 256 256 X X X X

System fail LED Extinguished
System enters standby on AC power
Normal SROM deselected

P00>>>sh dev
dka0.0.0.3.0 DKA0 RZ1CC-BA 883F
dqb0.0.1.16.0 DQB0 CD-224E A.8D
eia0.0.0.3.1 EIA0 00-02-56-00-17-79
eib0.0.0.4.0 EIB0 00-02-56-00-17-78
pka0.7.0.3.0 PKA0 SCSI Bus ID 7

Many thanks for your help.
Steven Schweda
Honored Contributor

Re: Tru64 installation fails on DS20L

> [...] you MUST have an IDE system disk for
> that box ?!

Where "that box" is an API CS20, not a Compaq
DS20L (as I read it).
Hein van den Heuvel
Honored Contributor

Re: Tru64 installation fails on DS20L

Steven wrote>> > [...] you MUST have an IDE system disk for that box ?!
>Where "that box" is an API CS20, not a Compaq DS20L (as I read it).

I agree. I thought it odd, but just wanted an explanation.

For the console variable, I don't see anything odd, but that does not mean much. My gutfeel suspect ones would be
'heap_expand', set to none, can be set to 2mb or 4mb? and 'console_memory_allocation' set to new, alternative 'old'. Supposedly genvmunix (which the CD image surely is) can deal with either and the wrong setting would give an "bootstrap address collision" messages

Steven>>I can boot from that disk up
:
>> configuration of the boot disk is inconsistent with that of the ds20L.

Can you boot genvmunix from that disk?
-fi genvmunix
If that works... doconfig.

Hein.
Pieter 't Hart
Honored Contributor

Re: Tru64 installation fails on DS20L

suggestion : clear bootdef_dev before booting from the OS-CD.

the installation script on CD tries to read some hw_config from the default bootdisk (bootdef_dev)to "optimize" the process.

Pieter
Vladimir Fabecic
Honored Contributor

Re: Tru64 installation fails on DS20L

Just one question:
Did you try to boot with help of NHD5?
As far I can remember, I needed NHD5 to install v5.1A on DS20L.
In vino veritas, in VMS cluster
Rob Leadbeater
Honored Contributor

Re: Tru64 installation fails on DS20L

Looks like you need at least NHD4 according to the user guide (page 3-16).

http://h18002.www1.hp.com/alphaserver/download/ek-ds20l-ug-b01.pdf

Cheers,
Rob
Rob Leadbeater
Honored Contributor

Re: Tru64 installation fails on DS20L

The readme for NHD 4.0 is also quite clear !

ftp://ftp.hp.com.au/pub/patches/unix/v5.1a/nhd/4.0/nhd4.README

Tru64 UNIX New Hardware Delivery-4 for V5.1A CD-ROM contains support for the following hardware:
* DA-81AAA-EA/-FA/-GA and DA-81BAA-EA/-FA/-GA: DS20L Compaq AlphaServer(tm) systems
Steven L Guberman
Occasional Advisor

Re: Tru64 installation fails on DS20L

The suggestions to install an NHD helped to solve the problem. I installed NHD5 (Thanks to Vladimir and Rob)after making an iso file and writing a cd on a pc. The kn600 error messages are now gone. However, the boot (see below) reveals two errors:
< fatal="" error="">
fd internal driver error: FDI PROBE FAIL (A,11).
fdi0 not probed
and
Error:
:
This system appears to have no disks.
These errors appear even though sh dev (see above)shows the presence of a scsi disk:
dka0.0.0.3.0 DKA0 RZ1CC-BA 883F
Any suggestions?

Alpha boot: available memory from 0x1ffc000 to 0x3fb5a000
Compaq Tru64 UNIX V5.1A (Rev. 1885); Wed Aug 1 15:13:05 EDT 2001
physical memory = 1024.00 megabytes.
available memory = 987.36 megabytes.
using 1286 buffers containing 10.04 megabytes of memory
forcing interrupt in tl_do_command
Firmware revision: 6.6-10
PALcode: UNIX version 1.92-71
hp AlphaServer DS20L 833 MHz
pci1 (primary bus:1) at nexus
ee0 at pci1 slot 3
ee0: Intel 82559 (10/100 Mbps) Ethernet Interface
ee0: Driver Rev = V1.0.12, Chip Rev = 8, hardware address: 00-02-56-00-17-79
PCI device at bus 0, slot 3, function 0 could not be configured:
Vendor ID 0x1000, Device ID 0x21, Base class 0x1, Sub class 0x0 Sub-VID 0x14d9 2
has no matching entry in the PCI option table
PCI device at bus 0, slot 17, function 0 could not be configured:
Vendor ID 0x10b9, Device ID 0x7101, Base class 0x0, Sub class 0x0 Sub-VID 0x14d2
has no matching entry in the PCI option table
pci0 (primary bus:0) at nexus
ee1 at pci0 slot 4
ee1: Intel 82559 (10/100 Mbps) Ethernet Interface
ee1: Driver Rev = V1.0.12, Chip Rev = 12, hardware address: 00-02-56-00-17-78
isa0 at pci0
gpc0 at isa0
gpc1 not probed
ace0 at isa0
ace1 at isa0
lp0 at isa0
< fatal="" error="">
fd internal driver error: FDI PROBE FAIL (A,11).

fdi0 not probed
ata0 at pci0 slot 16
ata0: ACER M1543C
scsi0 at ata0 slot 0 rad 0
scsi1 at ata0 slot 1 rad 0
Created FRU table binary error log packet
kernel console: ace0
NetRAIN configured.


Warning: No time set in file system, using the system clock.
This date may not be correct, please check it after booting

ee0: Parallel Detection, 10 Mbps half duplex
vm_swap_init: warning UNSPECIFIED swap device not found
vm_swap_init: swap is re-set to lazy (over commitment) mode

INIT: SINGLE-USER MODE


Initializing system for Tru64 UNIX installation. Please wait...

Assigning a cluster device number to root


Unable to save existing hardware configuration. New configuration will be
used.

*** Performing CDROM Installation

Loading installation process and scanning system hardware.

Welcome to the Tru64 UNIX Installation Procedure

This procedure installs Tru64 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"

Refer to the "Installation Guide" and "Installation Guide -- Advanced
Topics" for more detailed information about installing the operating
system.



** This system is currently running firmware revision: 6.6-10
See the "Installation Guide" for more information about
updating firmware.


Error:
:
This system appears to have no disks. The installation procedure
requires at least one disk. If there is a disk in the system, you
should confirm that it is properly connected, and then start the
installation procedure again from the ">>>" prompt. If you have
already done this, contact a customer service representative.





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




Steven L Guberman
Occasional Advisor

Re: Tru64 installation fails on DS20L

Please note that Fatal Error #174 in the prior message can be ignored according to NHD_Notes.pdf. So this leaves the problem of the lack of recognition of the scsi drive.
Pieter 't Hart
Honored Contributor

Re: Tru64 installation fails on DS20L

check the interfaces in this locations:
PCI device at bus 0, slot 3, function 0 could not be configured:
PCI device at bus 0, slot 17, function 0 could not be configured:
if it's the video card this can be ignored at this moment. some (like powerstorm) needs an extra package in the OS .
if it's the scsi interface you may need another NHD for support of this interface.
does "show config" give any info for these interfaces?

Also check if the scsi-bus is properly terminated. this may be the cause of disk drive being detected at boottime but faulting when used from an "OS" (other scsi commands and other timing).
Vladimir Fabecic
Honored Contributor

Re: Tru64 installation fails on DS20L

Try the following from SRM prompt :
>>>boot -fl fa -fi "GENERIC" dqb0

Then you switch NHD and OS disks several times.
In vino veritas, in VMS cluster
Steven Guberman
Occasional Visitor

Re: Tru64 installation fails on DS20L

I have tried NHD7 with the same results as indicated above. The drive
is still not recognized.
The HP specified cable kit for the SCSI drive is CK-DS20L-AA. However,
this kit is no longer available. The drive is connected to a
Symbios riser card and the cable is for 68 pin UltraSCSI3, LVD160.
Can any one tell me the maximum length of the required cable and the
type of termination needed? Many thanks.
Hein van den Heuvel
Honored Contributor

Re: Tru64 installation fails on DS20L



Scsi cacble ought to terminator at both ends. That DS20 cable kit might provide that, but I doubt it. Does the cable go straight to the drive or with a mini pcb board in between.
Does the drive have a jumber setting for termination?

Do you happen have a generic cable with terminator slot? One of those 1 1/2 inch wide white flat-cable with a couple of black connector blobs?

SE-scsi can go for some (3) meters, so anything that fits in an DS20L should be fine.

That drive is like an RZ29 right? 4GB, wide, Single Ended.
I believe that the Symbios (LSI) 53C100 with auto-detect LVD versus SE... with the right cable.

>> PCI device at bus 0, slot 3, function 0 could not be configured.
And the Console reports the drive to be in that slot. Nasty.

Now the console also seems to report 2 CD-roms. Is that correct? How about keeping dqb for the CD and try using an IDE system disk as DQA, at least to try and maybe for keeps? It will easily be bigger than 4gb :-).


Hein.
Steven L Guberman
Occasional Advisor

Re: Tru64 installation fails on DS20L

Thanks, Hein, for your message.

From the NHD-6 Release Notes:

2.1.9.1 DS20L or DS25 Boot Messages
During a DS20L or DS25 system boot, you may see the following PCI table
error message:
PCI device at bus 0, slot 3, function 0 could not be configured:
Vendor ID 0x1000, Device ID 0x21, Base class 0x1, Sub class 0x0
Sub-VID 0x14d9
Sub-DID 0x8002
has no matching entry in the PCI option table
You also may see the following unrelated driver error message:
< fatal="" error="">
fd internal driver error: FDI PROBE FAIL (A,11).
Both of these messages reflect known errors and can be ignored.

>That drive is like an RZ29 right? 4GB, wide, Single Ended.
>I believe that the Symbios (LSI) 53C100 with auto-detect LVD versus SE... >with the right cable.
Yes, that's the configuration. I'm using a 40" Amphenol cable, AWM 80C LL31941 CSA with 68 pins and active termination. Shouldn't this work? According to SCSI specifications, the cable is not too long and the bus should run in single ended mode with that disk drive.
I will probably try the IDE drive although I don't expect it to work in Tru64.
Steven Guberman
Occasional Visitor

Re: Tru64 installation fails on DS20L

The last sentence in my prior message was:
" I will probably try the IDE drive although I don't expect it to work in Tru64." My expectations were proven wrong upon hooking up an old IDE drive to one of the two IDE connectors on the mother board. It works! I was able to set up a bootable ide drive with Tru64 installed. Thanks Hein for the suggestion--I owe you some points.

Separately, I am having some trouble with licenses but I will start a separate thread for this.
Hein van den Heuvel
Honored Contributor

Re: Tru64 installation fails on DS20L

>> upon hooking up an old IDE drive to one of the two IDE connectors on the mother board. It works! I was able to set up a bootable ide drive with Tru64 installed.

Excellent. That's _so_ much more convenient to use as a base to figure out what is wrong with the SCSI, or you could even just leave it as OS disk.

It worked for me on a DS10, so I had good hope.

Cheers,
Hein.