Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to boot DS10 from internal (disk failed to open dqa0.0.0.13.0)

 
Alessandro de Oliveira
Occasional Visitor

Failed to boot DS10 from internal (disk failed to open dqa0.0.0.13.0)

Hi All,

I have a DS10 and the following messages are showed during normal boot:

512 Meg of system memory
probing hose 0, PCI
probing PCI-to-ISA bridge, bus 1
probing PCI-to-PCI bridge, bus 2
bus 0, slot 9 -- ewa -- DE500-BA Network Controller
bus 0, slot 11 -- ewb -- DE500-BA Network Controller
bus 0, slot 13 -- dqa -- Acer Labs M1543C IDE
bus 0, slot 13 -- dqb -- Acer Labs M1543C IDE
bus 2, slot 4 -- eia -- DE602-B*
bus 2, slot 5 -- eib -- DE602-B*
bus 0, slot 15 -- pka -- QLogic ISP10x0
bus 0, slot 16 -- pkb -- QLogic ISP10x0
initializing GCT/FRU at 1e0000
System Temperature is 41 degrees C

COMPAQ AlphaServer DS10 617 MHz Console V6.1-2, Oct 15 2001 14:11:29

CPU 0 booting

(boot dqa0.0.0.13.0 -flags A)
failed to open dqa0.0.0.13.0

Retrying, type ^C to abort...


I can't find the dqa0 entry on the result of "show device"

>>>show device
dka0.0.0.15.0 DKA0 COMPAQ BD00965333 B911
dkb0.0.0.16.0 DKB0 COMPAQ BD00965333 B911
dqb0.0.1.13.0 DQB0 Compaq CRD-8402B 1.03
dva0.0.0.0.0 DVA0
mka400.4.0.15.0 MKA400 TLZ10 04a8
eia0.0.0.2004.0 EIA0 00-0B-CD-F4-EF-62
eib0.0.0.2005.0 EIB0 00-0B-CD-F4-EF-63
ewa0.0.0.9.0 EWA0 00-10-64-31-12-1A
ewb0.0.0.11.0 EWB0 00-10-64-31-12-19
pka0.5.0.15.0 PKA0 SCSI Bus ID 5 5.57
pkb0.5.0.16.0 PKB0 SCSI Bus ID 5 5.57

The disk is there, and I'm not sure if it is a disk or a configuration problem.

Can somebody help me?
Is there some way to configure dqa0 via console?
Or do you believe it is a disk problem indeed?

Thanks a lot,

Alessandro
7 REPLIES
Richard Brodie_1
Honored Contributor

Re: Failed to boot DS10 from internal (disk failed to open dqa0.0.0.13.0)

When you say 'the disk is there', does that mean you are sure the boot disk is an IDE drive, and not one of the two SCSI drives that the console sees?
Hoff
Honored Contributor

Re: Failed to boot DS10 from internal (disk failed to open dqa0.0.0.13.0)

DQA0: is not electrically present, whether or not it is visually present. If there really is a DQA0: device here, then there's a hardware-level error or hardware failure of some sort.

This could also be the case that the BOOTDEF_DEF default boot device is simply set wrong. I'd expect to see this SRM console environment variable set to DKA0: or DKB0:, and not to DQB0: (the IDE ATAPI CD device) regardless.

If one or more of the following work, then you've found a bootable device:

>>> BOOT DQB0:
>>> BOOT DKA0:
>>> BOOT DKB0:

if so, flip over BOOTDEF_DEV with the the ddci: device name replaced in the following:

>>> SET BOOTDEF_DEV ddcu:

It may also be the case that somebody has been working inside the box reconfiguring the I/IO widgets, and has simply reconnected the CD drive to the wrong IDE connection on the main board. (I don't have an AlphaServer DS10 handy to check to see how the IDE and SCSI connectors are organized on the motherboard.)


Alessandro de Oliveira
Occasional Visitor

Re: Failed to boot DS10 from internal (disk failed to open dqa0.0.0.13.0)

Yes, the disk is an IDE and it's connected to the workstation.

I have another workstation with exactly in the same configuration working fine, and its boot device is also dqa0.0.0.13.0.

The disks dka0 and dkb0 are connected on two StorageWorks shelfes, and are not the boot devices of the system.

Sorry, but if somebody could help me to understand how the system is supposed to work it would be great!!

When I execute a "ls" on the >>> prompt I see all devices but the dqa0... This entry should be there does not mean the disk is connected or not, or these devices entries are created during boot??? (see below)

>>>ls
add_de205 alloc alphabios arc assign_hw
b bar boot bootp bpt
break buildfru c cat check
chmod clear clear_error cmp continue
crash d debug1 decode deposit
dka0.0.0.15.0 dkb0.0.0.16.0 dqb0.0.1.13.0 dva0.0.0.0.0 dynamic
e echo edit eerom eia0.0.0.2004.0
eib0.0.0.2005.0 el element eval ewa0.0.0.9.0
ewb0.0.0.11.0 examine examine_render exer exit
false fat find_field flash fpr
free fsrom fwupdate galaxy gct
gctverify gpr grep h halt
hd help hwrpbtta0 iic_mst iic_rcm_nvram0
iic_rcm_nvram1 iic_rcm_nvram2 iic_rcm_nvram3 iic_rcm_nvram4 iic_rcm_nvram5
iic_rcm_nvram6 iic_rcm_nvram7 iic_rcm_temp iic_smb0 iic_system0
iic_system1 info init ipr isacfg
iso9660 iso9660_raw isp1020_edit jtopal kill
kill_diags lfu line login lpinit
ls man mc_cable mc_diag memexer
memtest mfgtest migrate mka400.4.0.15.0 mopdl
more ndbr net nettest ni_db_eia0
ni_db_eib0 ni_db_ewa0 ni_db_ewb0 nl nt
ntrom nvram para pcicfg pciio
pcimem pmem prcache ps psr
psr_render pwrup rca0 rcb0 rcu
readme restore_nvram rm run sa
save_nvram se semaphore set set_flag
sh shell sho show show_status
showit sleep sort sound sp
srmrom srom srom21143_edit start stop
sym sys_exer tee test testmem
tftp toy tr true tt
tta0 tta1 uptime vmem vmem_render
wc wwidmgr




Alessandro de Oliveira
Occasional Visitor

Re: Failed to boot DS10 from internal (disk failed to open dqa0.0.0.13.0)

Yes, the disk is an IDE and it's connected to the workstation.

I have another workstation with exactly in the same configuration working fine, and its boot device is also dqa0.0.0.13.0.

The disks dka0 and dkb0 are connected on two StorageWorks shelves, and are not the boot devices of the system.

Sorry, but if somebody could help me to understand how the system is supposed to work it would be great!!

When I execute a "ls" on the >>> prompt I see all devices but the dqa0... This entry should be there does not mean the disk is connected or not, or these devices entries are created during boot??? (see below)

Thanks!!

>>>ls
add_de205 alloc alphabios arc assign_hw
b bar boot bootp bpt
break buildfru c cat check
chmod clear clear_error cmp continue
crash d debug1 decode deposit
dka0.0.0.15.0 dkb0.0.0.16.0 dqb0.0.1.13.0 dva0.0.0.0.0 dynamic
e echo edit eerom eia0.0.0.2004.0
eib0.0.0.2005.0 el element eval ewa0.0.0.9.0
ewb0.0.0.11.0 examine examine_render exer exit
false fat find_field flash fpr
free fsrom fwupdate galaxy gct
gctverify gpr grep h halt
hd help hwrpbtta0 iic_mst iic_rcm_nvram0
iic_rcm_nvram1 iic_rcm_nvram2 iic_rcm_nvram3 iic_rcm_nvram4 iic_rcm_nvram5
iic_rcm_nvram6 iic_rcm_nvram7 iic_rcm_temp iic_smb0 iic_system0
iic_system1 info init ipr isacfg
iso9660 iso9660_raw isp1020_edit jtopal kill
kill_diags lfu line login lpinit
ls man mc_cable mc_diag memexer
memtest mfgtest migrate mka400.4.0.15.0 mopdl
more ndbr net nettest ni_db_eia0
ni_db_eib0 ni_db_ewa0 ni_db_ewb0 nl nt
ntrom nvram para pcicfg pciio
pcimem pmem prcache ps psr
psr_render pwrup rca0 rcb0 rcu
readme restore_nvram rm run sa
save_nvram se semaphore set set_flag
sh shell sho show show_status
showit sleep sort sound sp
srmrom srom srom21143_edit start stop
sym sys_exer tee test testmem
tftp toy tr true tt
tta0 tta1 uptime vmem vmem_render
wc wwidmgr
Jon Pinkley
Honored Contributor

Re: Failed to boot DS10 from internal (disk failed to open dqa0.0.0.13.0)

Alessandro,

>"I have another workstation with exactly in the same configuration working fine, and its boot device is also dqa0.0.0.13.0."
...
>"Sorry, but if somebody could help me to understand how the system is supposed to work it would be great!!"

Is this a trick question? It is supposed to work like your other workstation.

You have told us nothing about the history of the non working system. When was the last time it did work? What has happened to the system in the mean time?

Hoff gave you the answer. There is something that is preventing the system from seeing the drive. So that leaves a few possible reasons.

A loose or bad cable.
Dead drive. (Are there any LEDs that light up, can you hear the drive spin up?)
Something on the motherboard (less likely in my opinion).

If this system has never worked since you have had it, then it is possible that some cable is installed wrong, a jumper on the drive may be wrong, etc. It really is impossible to troubleshoot hardware remotely with a forum as the only means of communication.

Since you have a working example, look there and see if you can see any differences in cables, drives, etc.

Jon
it depends
The Brit
Honored Contributor

Re: Failed to boot DS10 from internal (disk failed to open dqa0.0.0.13.0)

Alessandro,
It seems to me that Hoff has it correct. (Unless there are two CD drives attached to this system).

From the information that you provide, the system clearly sees a CD drive on DQB0, and nothing on DQA0.

I would try booting DQB0.

>>> boot DQB0 -fl A

What do you have to lose??

Dave.
Hoff
Honored Contributor

Re: Failed to boot DS10 from internal (disk failed to open dqa0.0.0.13.0)

I'm presuming this box is supposed to have an IDE ATA disk and an IDE ATAPI CD-ROM device.

The CD-ROM (CRD-8402B) is visible in various diagnostic displays.

If there is an ATA hard disk drive present on the first IDE bus in the primary position (a position which would be known as DQA0: to the console and to OpenVMS), then that IDE ATA disk is disconnected or dead or unpowered or otherwise unknown to the console.

There could be a bad cable here, a dead ATA disk, a loose connection on the power or bus, or (less likely but still possible) a problem with the main board or with the power supply.

SRM reads the configuration directly off the bus. There's no configuration here, SRM looks for and finds the devices it recognizes automatically. Which means that if there was an IDE ATA disk, it's not responding any more.

Call in your preferred hardware support organization for a look.

Given that SCSI is faster than IDE ATA on most (all?) Alpha boxes, I'd look to ignore IDE entirely and switch to an external SCSI disk here regardless. (Yes, IDE ATA can be fast, but the particular implementation found in most Alpha systems is simply not fast. The particular IDE ATA I/O implementation on OpenVMS Alpha is generally rather slower and more compute-intensive than SCSI.) Which means I'd look to restore or re-install on a scratch SCSI disk, and boot and run from that.