checking boot area

[himacs]

Hi Admins,

I am going to reboot my hpux B..11.23 server as part of patch deployment.I dont have ignite backup for the same.Please suggest me with steps to check the boot area,kernel etc.. before rebooting,to ensure there are no error in root disk and server will come up with no issues.

My root disk is mirrored

regards
himacs

[Michal Kapalka (mikap)]

hi,

at first patching without DRD or minimum Ignite it is not good idea.

1, backup OS ( DRD / Ignite (tape/net)

2, reboot the server before patching

3, check if your system don't have any problem after commeing up

4, before patching of the system use -p switch

5, apply patches, and check the system again.

mikap

[Torsten.]

To be real safe, you must have a backup before patching.

[Michal Kapalka (mikap)]

hi,

i forgot to say :

check /stand/bootconf

lvnboot -v

mikap

[himacs]

Hi,

Thanks for the response..i dont have taper drive connected to the server and no scsi card attached.

I want to check the reliablity of root disk.
Please provide the steps to ensure there are no errors in boot area.

Regards
himacs

[R.K. #]

Hello Himacs..

As said it is important to reboot the server once before patching and see if it comes up fine..so you will know that everything is fine with the server as of now.

Also do:
# swverify \*
to ensure all filesets are installed properly before patching.

If something goes wrong you can boot the server with the backup kernel (thats why you should boot the server before patching also).

Since you do not have any tape drive, you can go with DRD. Install it and then patch one the disk using DRD, then see if system boots up fine with that disk. (so you will have two disks, one with OS before patching and one with OS after patching).

[himacs]

Hi Team,

I m thinking to do below steps before restarting(before patching).

1.Check in syslog for any errors related to root disk.
2.Take kernel backup using kconfig


This server was restarted long back.So i am worried.

Regards
himacs

[rariasn]

Hi,

- Verify "syslog" file.
- Verify "rc.log" file.
- Verify consistence for vg00
- Verify "lvlnboot -v" output
- Verify integrity of patches:

# check_patches
or
# /usr/sbin/swlist â l fileset â a state | /usr/bin/grep â v â e â #â â e â configuredâ


- Install "bundle" of patches with option "-p".
# swinstall -x mount_all_filesystems=false -x autoreboot=true -x \
patch_match_target=true -s /path_depot_file archivo depot>/
Verify /var/adm/sw/swinstall.log file


- Verify "kenel"

# cd /stand/
# kconfig -e - /stand/system.test
# kconfig â i hpux_test /stand/system.test
# ll /stand/hpux_test

- Execute "dmesg" command
- Execute "ioscan -fn" command

Rgs,

[himacs]

Hi RK,

Thanks for th reply..

>>As said it is important to reboot the server once before patching and see if it comes up fine>>

this is my main concern.. if it comes up fine before patching..

so iwant to check for any errors in root VG.

Regards\
himacs

[Johnson Punniyalingam]

>>I want to check the reliablity of root disk.<<

reliability of root disk in what ways?

software & hardware error are different.

no such thing or command to check "reliability of root disk" by hardware level you check with commands like "vgdisplay" "lvlnboot" "dd" commands, but if software error ??? you can't
you have no choice to repair the software you need to boot the server into single usermode and revert back to "old kernal"

so options are

verify the patches properly prior to Installation of patches

perfrom reboot of the server and make sure you boot from secondary mirror disk .prior to installation of patches

than break mirror and boot the server using your secondary disk and proceed to install the patches