Operating System - HP-UX
1832451 Members
3132 Online
110042 Solutions
New Discussion

system crash when booting in multi user mode

 
sahar
New Member

system crash when booting in multi user mode

Hi all,

we have a rp3440 with HPUX 11i (dec-03) with internal mirrored system HDDs (36GB). WE shutdown the server and disconnected the alternate internal system disk the we rebooted from primary internal system disk in multi user mode (hpux -lq). The system crashed (panic) without booting. We tried to boot from the alternate system disk (same problem).
So, we rebooted from primary disk in maintenance mode (hpux -lm), we got the following error before getting the shell prompt :

" /sbin/ioinitrc :
fsck /dev/vg00/lvol1 : possible swap device ( cannot determine )
fsck SUSPENDED BY USER
/dev/vg00/lvol1 : no such device or address
unable to mount /satnd - please check entries in /etc/fstab
Skipping KRS database initialization
/stand can't be mounted "

Then , i activated vg00 (vgchange -a y vg00)
and check lvol1 logical volume using
fsck /dev/vg00/lvol1 which returned the following " fsck /dev/vg00/lvol1 : possible swap device ( cannot determine ) "

So , i executed bcheckrc command and switched to run level 3 through 1 and 2.
All L.V. / F.S. were mounted.
I noticed the following :
1- the root file system was mounted under / using /dev/root device file not /dev/vg00/lvol3
2- swapinfo -tm showed that the NAME of the primary swap area as 31,0x020002 not /dev/vgg00/lvol2
3- when selecting swap from sam ( Disks anf file systems ) , the swap area was marked as unused

NB : - i checked /etc/fstab : ok
- tried to reboot many times , same problem in multi user mode and in maintenance mode

please if any one can help and respond urgently

BR

Sahar
3 REPLIES 3
Steven E. Protter
Exalted Contributor

Re: system crash when booting in multi user mode

Shalomom Sahar,

If possible, put the sytem back together the way it was before you started.

Boot multi or sinle and check the lvm boot structure.

lvlnboot -v

I would think the system has not been configured correctly for mirroring and perhaps swap's mirror mirror set may not be on different disks.

Full procedure:

pvcreate -B /dev/rdsk/c1t0d0 #use real disk

mkboot -l /dev/rdsk/c1t0d0
mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c1t0d0 # use real disk


# mkboot -b /usr/sbin/diag/lif/updatediaglif -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?

If you are running 64-bit OS:

# mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?


vgextend /dev/vg00 /dev/dsk/c1t0d0 # same thing
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c1t0d0

# real disk. repeat for other lvols

lvlnboot -r /dev/vg00/lvol3 # root fs /
lvlnboot -s /dev/vg00/lvol2 #swap
lvlnboot -d /dev/vg00/lvol2 #swap/dump
lvlnboot -b /dev/vg00/lvol1
lvlnboot -R
lvlnboot -v
setboot
setboot -a 52.1.0 # second disk

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
sahar
New Member

Re: system crash when booting in multi user mode

Hi Steven,

Thank you for your concern.

I have some questions :

1- pvcreate should be run on primary disk or second disk
1- /dev/disk/c1t0d0 means the first or second disk
3- what do you mean by real disk , /dev/dsk/c?t?d? , same thing
4- concerning vgextend , the second disk is already in vg00
5- is there any risk on HPUX booting

BR

Sahar

Mridul Shrivastava
Honored Contributor

Re: system crash when booting in multi user mode

If u boot in lvm maintenance mode then its not recommended to change the run level from there always reboot then come to multi user mode or there may be incorrectable errors.
It's advisable to execute only LVM related commands in lvm maintenace mode so better u try lvlnboot -v (after booting in lvm maintenace mode) and then check for the device configured for dump/swap.
I think they r not configured so pls configure primary swap and then reboot, PLs don't try to come to multi user mode from there or it will corrupt the vg info.
Time has a wonderful way of weeding out the trivial