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

boot problem - failed to open dka0.0.0.6.1

SOLVED
Go to solution
Dan Borell
Occasional Contributor

boot problem - failed to open dka0.0.0.6.1

I'm running a Compaq XP1000 with Tru64unix 5.1.
The machine won't boot. Message is "failed to open dka0.0.0.0.6.1. Any help would be greatly appreciated.
Note: Prior to the boot problem the machine would go into a coma after being up for a few minutes. The keyboard, mouse and monitor would be off/not working. I could not access the machine from other computers on the network. However, I could ping it.
9 REPLIES
Mark Poeschl_2
Honored Contributor

Re: boot problem - failed to open dka0.0.0.6.1

Can you see the dka0 device from the ">>>" console prompt? What does "show device" at the ">>>" prompt give you?

It's possible your disk might be toast. Hopefully you've got a good backup!
Ivan Ferreira
Honored Contributor

Re: boot problem - failed to open dka0.0.0.6.1

Can you see the disk led? Is anything amber there?

In this case, is likely that the disk is failed. You could start with the installation CD and try to access the disk and the data on it.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Dan Borell
Occasional Contributor

Re: boot problem - failed to open dka0.0.0.6.1

No, I'm not seeing the device at the >>> prompt. However,my critical data is on 2 external disks (raid array) connect to this machine. Is there any way I can boot up and move this data to another server?
Solution

Re: boot problem - failed to open dka0.0.0.6.1

Well, the disk might be dead. What kind of disk is it? Where is it physically located (can you visually locate it and is there an illuminated LED) ? If you have an installation CD, depending upon what your external disks are and what kind of array controller you have, you *might* be able shell out of the installer, mount your external data disk then copy what you need to a tape or something. I say *might* because if you need some kind of special driver that isn't on the CD, this won't work. Now, it's a different story if the disks were simply under LSM control and not hardware raid.

It would be very unusual for SRM to rename your devices without you doing something intentionally, but that's also a possibility. Do you see any disks with e "show dev" that weren't there before? Maybe you'll get lucky and just be able to specify another boot device from the SRM prompt and get it back up.

The long and short of your situation is that if your boot disk is on a local bus and SRM doesn't see it at all, you probably have a dead device. Just for grins, what SRM firmware revision are you running?

Jack
Dan Borell
Occasional Contributor

Re: boot problem - failed to open dka0.0.0.6.1

It is a internal SCSI drive. I'm not seeing the light on front panel turn on.

I'm not seeing any new devices shown during "show dev".

The firmware is vers 5.8.
Steven Schweda
Honored Contributor

Re: boot problem - failed to open dka0.0.0.6.1

> I'm not seeing the device at the >>> prompt.

_That's_ not a disk. [...]

> Is there any way I can boot up and move
> this data to another server?

Move how? Tape? Network? ESP?

I just do OS installations from the OS
CD-ROM. I don't know how much device and/or
network functionality you get when booted
from the OS CD-ROM. You may be able to
configure IP and NFS that way, but it might
be easier to attach a good disk, do a quick
OS installation, and proceed from there.

Depending on what's inside, it may be easy to
add a SCSI disk without removing the
paperweight, but it should be pretty easy to
swap out the dead one in any case.

Just curious:
> I could not access the machine from other
> computers on the network. However, I could
> ping it.

I'd call a successful "ping" accessing the
machine. What did _you_ mean by "could not
access the machine"?
Steven Schweda
Honored Contributor

Re: boot problem - failed to open dka0.0.0.6.1

> I'm not seeing the light on front panel
> turn on.

Which light on whose front panel? I believe
that the inquiry was referring to an LED on
the suspect disk drive itself, not the
pretty green LED by the power switch (the
one with the anachronistic drum-storage
icon), which would indicate activity on
_any_ SCSI or IDE device. (Of course, no
light anywhere does not bode well.)

If the internal (suspect) disk is on the
internal SCSI interface, and the external
disks are on a different (PCI card?) SCSI
interface, you _could_ have an internal SCSI
problem rather than an internal SCSI _disk_
problem, but a dead disk is far more likely.

> The firmware is vers 5.8.

On the bright side, while it's highly
unlikely to help you here, at least you have
V5.9-1 to look forward to.

Re: boot problem - failed to open dka0.0.0.6.1

What's about >>>show conf
Do You have pka controller or it dead ?
What's about SCSI terminator and/or other device on SCSI bus ?
Dan Borell
Occasional Contributor

Re: boot problem - failed to open dka0.0.0.6.1

This morning I turned on the machince and to my surprise I heard the disk come to life and it booted up! I was able to copy the files I needed. I suppose now I'll reload the OS on one of the external SCSI drives, because I expect the bad drive to lapse into a coma any minute, which is what has been happened before. It's almost certainly a bad disk right? Thanks for all the help!!!!