not booting "configured vm_swap_init: swap is set to eager"

[Jagadesh]

Dear All,

While booting the Digital machine with Digital 5.1 OS it stops booting after displaying
"configured vm_swap_init: swap is set to eager
allocation mode"

Kindly help me out in how to go about in booting the same.

Thanks
S.Jagadesh

[Alexey Borchev]

1) It may be a problem with disk (or disk partition) containing your swap space.
check it up.

2) the swap device and swap mode are specified in /etc/sysconfigtab:

vm:
swapdevice = /dev/disk/dsk1h
vm_swap_eager = 0

3) Think of setting swap to lazy (deferred) mode - vm_swap_eager = 0. Read
# man swapon

4) probably You'll need to boot into single-user mode to fix sysconfigtab. In SRM prompt:
>>> boot -flag s

Good luck!

[Jagadesh]

thanks for ur reply..

When i boot in to single user mode.. i cannot able to open /etc/sysconfigtab file.. it gives an error like vi not found.

in single user mode i cannot able to find /bin or /usr/bin directory.

now i have booted in the second hard disk ( digital 5.1b). Is it possible to mount the other hard disk which is not booting. If so kindly let mo know how to go about in doing the same.

Thanks
Jagadesh

[Michael Schulte zur Sur]

Hi,

when booted to single user mode,
mount -a #mount the rest of the filesets
TERM=vt100
export TERM
check the swap devices defined in sysconfigtab as said before.
and try swapon -a then.

hth,

Michael

[Mohamed K Ahmed]

Jagadesh,
The message "configured vm_swap_init: swap is set to eagerallocation mode"
means that your system already configured the swap and it should be fine.
The problem maybe lies in the next line after this message.
If you have an output or copy of how the system boots, check the line that comes after this message.
I don't know what are your steps in booting your system, but for mine, it goes like this

b 22 23:50:22 AVENGER vmunix: ATM Subsystem configured with 4 restart threads
Feb 22 23:50:22 AVENGER vmunix: ATMUNI: configured
Feb 22 23:50:22 AVENGER vmunix: ATMSIG: 3.x (module=uni3x) configured
Feb 22 23:50:22 AVENGER vmunix: ILMI: 3.x (module=ilmi) configured
Feb 22 23:50:22 AVENGER vmunix: ATM IP: configured
Feb 22 23:50:22 AVENGER vmunix: ATM LANE: configured.
Feb 22 23:50:22 AVENGER vmunix: ATM IFMP: configured
Feb 22 23:50:22 AVENGER vmunix: vm_swap_init: swap is set to lazy (over commitment) mode
Feb 22 23:50:23 AVENGER vmunix: alt0: 1000 Mbps full duplex Link Up via manual configuration
Feb 22 23:50:24 AVENGER vmunix: Environmental Monitoring Subsystem Configured.

HTH
Mohamed

[Martin Vorlaender]

Hi,

probably too late for the original poster, but for anyone finding this thread, here's my experience:

I had the very same hang when installing 5.1-B onto an ES47. Turned out to be the console variable "ostype" (or was it "os_type"?) being not set to "UNIX".

HTH,
Martin