Unusual error : KEY in LOCKED position ignoring debug enter sequence

UNIX Solaris
1

Hi,

This was very unusual situation I never came across & we have SUN engineers working on this.

We have Sun Fire V240 Server, 2 1.5-GHz UltraSPARC IIIi CPU, Solaris 9 Installed

During the boot-up it gives following message,

<date> <server name> unix : KEY in LOCKED position ignoring debug enter sequence

Has anybody seen this error before.

  • What is the possible cause for the problem
  • & solution you had in the end ?

I really appreciate any feedback on this

!Thanks
Anand

2

I think it means you did a "stop A" or a "Break" or whatever your key sequence is and the key is, well, in the locked position. If you want that to work, move the key to the on position.

3

Perderabo,

Probably I wasnt clear in my details above. Whats happening is, somehow during the bootup process the machine get stuck-up where it says there is a key lock on the server (the server is physically locked). The exact messages is as in my post above (in bold). Where as in reality there is no physical lock on the server. The key is currently in ON position only. SUN engineers are still looking into the issue.

Anand

4

In that case, the only thing I can think of is to go to the ok prompt and check the environment and fix anything that looks wierd. Commands: printenv and setenv). For reference, here is what we have on a V240:

# eeprom
test-args: data not available.
diag-passes=1
local-mac-address?=true
fcode-debug?=false
silent-mode?=false
scsi-initiator-id=7
oem-logo: data not available.
oem-logo?=false
oem-banner: data not available.
oem-banner?=false
ansi-terminal?=true
screen-#columns=80
screen-#rows=34
ttyb-rts-dtr-off=false
ttyb-ignore-cd=true
ttya-rts-dtr-off=false
ttya-ignore-cd=true
ttyb-mode=9600,8,n,1,-
ttya-mode=9600,8,n,1,-
output-device=ttya
input-device=ttya
auto-boot-on-error?=false
load-base=16384
auto-boot?=true
boot-command=boot
diag-file: data not available.
diag-device=disk
boot-file: data not available.
boot-device=disk0 disk1
use-nvramrc?=false
nvramrc: data not available.
security-mode=none
security-password: data not available.
security-#badlogins=0
post-trigger=power-on-reset
diag-script=none
diag-level=min
diag-switch?=false
obdiag-trigger=power-on-reset
error-reset-recovery=boot
#

Stuff like:
fcode-debug
boot-command
security-mode
diag-switch?
might be able to cause this. Also, can you boot from the cdrom? "boot cdrom -s" If so, you may just have a corrupted boot disk.

5

set-default (might have an s) will put everything back to defaults.

Can you boot it to single user?

6

i saw this problem very recently --- the key slot near the DVD drive was set to lock ... the boxes stayed on but I couldn't do a Stop-A on them even through the ALOM prompt ... fixed the problem by grabbing a key from another server and unlocking the settings ... you might want to turn the key fully off and then turn to the right one stop only ... good luck!