Big problem....can't reboot my system anymore - blue screen

[Erwin van der Wiel]

Hi all,
I hope someone can help me. I've got a problem to run the system in single-usermode, so i changed the /etc/inittab. In the etc/inittab there is a line "is:3:initdefault:". I changed it to "is:1:initdefault:"
After chanching the line i reboot the machine. The machine did not start up (so i don't see any prompt. The last line i see in the "blue screen" is:
Init: command is respawning too rapidly. Check for possible errors. Id cons "/usr/sbin/getty console console vt100"

I hope some-one can help me !

[Ravi_8]

Hi,

if this is your default boot disk
then from SMS console
P00>> boot -fl S
which takes you to single user mode
#mount -a
#TERM=vt100
#export TERM
#vi /etc/inittab
replace 1 with 3 in the line which has initdefault, save and quit the file.
#init 3

let me know what happens next.

if this is not the default boot disk then
P00>> boot -fl S
and follow the said procedure

[Erwin van der Wiel]

Thanks you will help me !
But it doesn't work. I will tell you what i've done:
1) Put the CDROM (version unix 5.1b) in cdrom drive
2) reboot the machine
3) system start-up and stoped after the message: Init command ...... console vt100 (see above)
4) The cdrom is not mounted at the moment, and i can't mount the CD-rom, (or do something wrong). I tried to mount the cdrom "mount -t cdfs /dev/disk/cdrom0a /updmnt" but it doesn't work. Maybe it's not "/dev/disk/cdrom0a /updmnt"
5) tried your command's
a) P00 >> boot -fl S
and tried
b) P00 >> boot -fl S cdrom0a

[Roberto Polli]

1) from SRM:
sho dev

for cdrom booting:
boot dskXXX -fl S

where dskXXX is the device id of the cdrom given from
sho dev

Peace, R.

[Ralf Puchner]

1. boot Tru64 cd-rom
2. select "shell" instead of install
3. check harddisk device (hwmgr -show scsi), if not there use hwmgr -scan scsi
4. if advfs filesystem, create /etc/fdmns/ links
5. mount domain
6. copy /etc/.mrg..*inittab template file to original one.
7. sync, halt command
8. boot normal disk from console

If you have a problem, have a look inside the admin guide.

[Erwin van der Wiel]

Thanks,

But i can't even boot the cdrom!

[Michael Schulte zur Sur]

Hi,

how do you try to boot and what happens?

greetings,

Michael

[Erwin van der Wiel]

Pff thank you will help me!

I think (and hope) i'am doing something wrong ....
What did i do:
1) Put the CDROM (version unix 5.1b) in cdrom drive
2) reboot the machine
3) system start-up and stoped after the message: Init command ...... console vt100 (see above)
4) I've got no prompt
5) The CD is not mounted automaticly
6) Whatever i type there is no reaction on the console ore the CD rom. I even din't get back my prompt.
7) The divices are not up, so i can't mount anything.
8) What i tried to mount is (see few reactions above )

Thanks a lot.

[Michael Schulte zur Sur]

Hi,

is your problem, that you have auto_action on boot and now you can't stop it?
You could try the operator halt button or, when initializing press repeatedly ^C before machine starts the boot sequence.

hth,

Michael

[Erwin van der Wiel]

Thanks Michael,
But that doesn't work...

[Michael Schulte zur Sur]

Hi,

have you tried both things?
Do I understand you right that your problem is to get to the console prompt?
There is one more way. Disconnect the system disks.

hth,

Michael

[Ralf Puchner]

Erwin,

what are you talking about? There is no "cdrom" autoboot mechanism. This is not windows or a PC.

Plugin the cd and enter the command on console as written within the admin guide, install guide, machine guide... etc.

If machine is set to autoboot action (as described within the machine guide, install guide, admin guide etc.) press HALT button.

Enter the cdrom and typin the magic boot command for cd-roms as described within the admin guide, install guide, machine guide etc.

After cd-rom bootet enter shell mode and mount the partitioning containing your root filesystem (as described within the admin guide).

Is it so hard to read a manual?

[Eric van Dijken]

I assume that you don't have a VT100 terminal attached to your Alpha Server. But it looks like your SRM console settings are set to "serial"

When the system is halted and you get the "P>>>" prompt. Enter the following command "set console graphics"

Then try the above again.

[dutch]
Mocht dit niet helpen, stuur dan even je telefoon nummer naar eric.dijken@isc.politie.nl
Praat ik je er wel doorheen :)
[/dutch]

[Ralf Puchner]

Eric,

it seems this could be the root cause of the original problem (first problem was the seen message, second he was not able to boot a cd-rom as suggested from Michael).

Another approach is to use a rs232 cable and plug a PC to the serial port using hyperterm as terminal emulation.

[Michael Schulte zur Sur]

Hi,

it is still not clear, whether the machine is on autoboot.
But even if console is set to serial, you should be able to get a prompt by hitting the Enter key.

hth,

Michael

[Eric van Dijken]

Aye, but with a getty respawning too fast.... The VT100 (if one is attached) is defective or wrongly configured, otherwise getty wouldn't respawn so fast.

Maybe he used an laptop to get access to his console port, then forget to switch back to graphics. Or plugged the cable again in, but into the wrong serial port.

So many things that can go wrong, the possibilities are end-less. I'am afraid this is gonna be a very long thread. (Thats why i asked for his phonenumber. Don't think we can solve this one the web. But we can try ofcourse)

[Michael Schulte zur Sur]

Eric,

you get it also, when the os can't mount /usr

Michael

[Ralf Puchner]

the message "respawn too rapidly" is typical if no terminal is connected and machine is configured for terminal use, because the signal on the serial port leads to a restart of the process...

[Erwin van der Wiel]

Some more information. Maybe this information can resolve my problem ?!

1)
"P00>>>init 1" or
"P00>>>init S" reboots my system

2)
When i type:
P000>>> boot (or boot -fl S)
Message of system:
HALT is or has been asserted, BOOT NOT POSIIBLE

3)
A VGA monitor is configured

4)
When i activated HALT before rebooting the system and reboot the system, i get the next message:
Halt assortion detected
NVRAM power-up script not executed
AUTO_ACTION=BOOT/RESTART and OS_TYPE=NT ignored, iff applicalble

I hope those are the answers you to come further!
Thanks a lot for all the reactions !

[Eric van Dijken]

With AUTO_ACTION set, when you UN-HALT the system, it will boot using the configured settings. You will first have to change the AUTO_ACTION SRM setting at the P>>> prompt.
type "set auto_action halt"

Then try to boot into Single User mode using the "boot -fl S" command.

Fix yer inittab, halt again, reset the "AUTO_ACTION" to "boot"

And you should be were you started, again.

[Erwin van der Wiel]

Okee, but this doensâ t work.
After typing

P00>>>
1) â set auto_action haltâ
2) â boot â fl Sâ
I will still get the message

Halt is or has been asserted,

[Michael Schulte zur Sur]

Hi,

please do the following on console prompt
set auto_action halt
post as attachment
show dev
show *

thanks,

Michael

[Erwin van der Wiel]

show dev:
-polling ncr0 (NCR 53C810) slot 1, but 0 PCI, hose 1 SCSI BUS ID 7
-dka400.4.0.1.1 DKA400 RRD 46 0557
-mka500.5.0.1.1 MKA500 TLZ09 03a5
- polling ISP0 (qlogic ISP10x0) slot 2, bus 0 PCI, hose 1 SCSI BUS ID 7
-polling floppy 0 (FLOPPY) PCEB-XBUS hose 0
-deva0.0.0.1000.0 DVA RX23
polling dac0 (mylex DAC960) slot4, bus 0 PCI hos 0
-dra0.0.0.4.0 DRA0 5 member RAID 5
-dra1.0.0.4.0 DRA1 5 member raid 5
-Polling tullip 0 (DEC chip 21140-AA) slot 3 bus 0 PCI, hose 1
-ewa0.0.0.3.1 00-00-F8-1A-13-D9 FAST FD (FULL DUPLEX)

sho *:
i can't scroll to above ... so which variables do you wan't to know ?

Thanks a lot

[Michael Schulte zur Sur]

Hi,

it seems, that you have managed to get to the console prompt. Was that with auto_action set to halt or by virtue of the halt button? ;-)

Well now you should be able to boot from dka400. Please make sure, halt button is switched off and then
boot dka400

hope, that works now!

Michael

[Ralf Puchner]

maybe the halt button is activated? On some machine it is a switch not a button. All the problems reported are "machine specific".

Please have a look into the manual of your machine learning how to use the SRM console, what variables must be set for what OS and what their meaning is.

The documentation will also learn you how to handle the buttons in front of the machine!