[root@hpux02:/root]
# /opt/ignite/bin/make_net_recovery -s hpux03 -x inc_entire=vg00
* Creating NFS mount directories for configuration files.
======= 04/11/08 10:56:30 SST Started /opt/ignite/bin/make_net_recovery. (Fri
Apr 11 10:56:30 SST 2008)
@(#) Ignite-UX Revision B.5.4.50
@(#) net_recovery (opt) $Revision: 10.637 $
* Testing pax for needed patch
* Passed pax tests.
* Checking Versions of Recovery Tools
ERROR: Cannot stat device file: /dev/old_vg_apps/lv_mom: No such file or
directory (errno = 2). Check /etc/fstab for a bad entry.
ERROR: The list_expander command failed. This could be due to a problem with
the -x options specified - see messages above.
======= 04/11/08 10:57:11 SST make_net_recovery completed unsuccessfully
[root@hpux02:/root]
#
AND/OR
# /opt/ignite/lbin/list_expander
ERROR: Cannot stat device file: /dev/old_vg_hr03/lv_u01: No such file or
directory (errno = 2). Check /etc/fstab for a bad entry.
[root@hpux02:/root]
#
This occurs when certain FS is no longer in use and was not removed in /etc/fstab. I check it using:
# bdf <block_device_name>
# bdf /dev/old_vg_apps/lv_mom
OR
# mount -v grep -i <pattern>
AND/OR
# lvdisplay <block_device_name>
# lvdisplay /dev/old_vg_apps/lv_mom
If it does NOT return any of your expected result, then it is safe to say that the FS is NOT is use. From here, we can proceed by commenting [deleting] this but, make sure to have a backup just in case. Systems admins know this by heart. "He who laughs last, made a backup!". Proceeding..
# cp -p /etc/fstab /etc/fstab.backup1.20080411
# vi /etc/fstab
....
/dev/old_vg_hr03/lv_u01 /old/var/opt/vghr03/u01 vxfs delaylog,mincache=direct 0 2
/dev/old_vg_hr04/lv_u01 /old/var/opt/vghr04/u01 vxfs delaylog,mincache=direct 0 2
/dev/old_vg_hr05/lv_u01 /old/var/opt/vghr05/u01 vxfs delaylog,mincache=direct 0 2
/dev/old_vg_hr06/lv_u01 /old/var/opt/vghr06/u01 vxfs delaylog,mincache=direct 0 2
/dev/old_vg_hr07/lv_u01 /old/var/opt/vghr07/u01 vxfs delaylog,mincache=direct 0 2
....
So, our target here is to comment these lines so that it will not be read by ignite. For this case, we can comment it one by one. But for cases where we want to comment hundreds of lines, it'll take a lot of time. So I searched for some vi commands that will do this task for me. And I found it here: http://sparky.rice.edu/~hartigan/vi.html.
I executed this in command mode: :218,$s/^/\#
This means that, I'd like to insert a "#" character at the beginning of each line from line 218 to the last. Save and exit. Then re-ran ignite. As of this writing, it's running smoothly.
Interesting topic: http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1207883792669+28353475&threadId=996179
Hello friend, on yesterday i am going to do myjob onsite and can not make ignite complete.
ReplyDeletei get the message error in this bellow, how i can solve this problem.
# make_tape_recovery -a /dev/rmt/2mn
* Creating local directories for configuration files and archive.
======= 07/13/09 15:05:47 TST Started make_tape_recovery. (Mon Jul 13
15:05:47 TST 2009)
@(#)Ignite-UX Revision C.7.2.94
@(#)ignite/net_recovery (opt) $Revision: 10.882 $ $Date: 2007/02/28
17:10:48 $
* Testing for necessary pax patch.
* Checking Versions of Ignite-UX filesets
lifls(open): No such device or address
lifls: Can't list /dev/dsk/c26t0d0s2; file not opened
WARNING: /dev/dsk/c26t0d0s2 is not a LIF volume.
No LIF files on the boot disk will be archived.
Check /stand/bootconf, man bootconf(4), and /dev/dsk to
ensure that the bootconf file is set up correctly.
WARNING: The make_sys_image failed to save the LIF volume.
ERROR: The list_expander command failed. This could be due to a problem with
parsing /etc/fstab or /etc/mnttab file - see messages above.
======= 07/13/09 15:06:12 TST make_tape_recovery completed unsuccessfully
# bdf
Filesystem kbytes used avail %used Mounted on
/dev/root 753664 465776 285704 62% /
/dev/vg00/lvol1 576595 225760 293175 44% /stand
/dev/vg01/lvol2 26214400 23506 24553971 0% /work
/dev/vg01/lvol6 31457280 24791 29467966 0% /version
/dev/vg00/lvol7 5996544 3765592 2213600 63% /var
/dev/vg01/lvol4 31457280 24791 29467966 0% /utilloc
/dev/vg00/lvol6 6422528 2633192 3759840 41% /usr
/dev/vg01/lvol5 31457280 24791 29467966 0% /user
/dev/vg00/lvol5 1048576 378744 665656 36% /tmp
/dev/vg01/lvol3 15728640 20945 14725971 0% /temp
/dev/vg00/lvol9 41943040 2894139 36608404 7% /sas
/dev/vg00/lvol10 41943040 403149 38949628 1% /sas/install
/dev/vg00/lvol4 7766016 6148536 1604864 79% /opt
/dev/vg01/lvol7 31457280 24791 29467966 0% /logs
/dev/vg00/lvol8 229376 10208 217504 4% /home
/dev/vg01/lvol1 104857600 28274328 71796884 28% /data
/dev/vg01/lvol8 31457280 61862 29433245 0% /config
# lvlnboot -v
lvlnboot: Couldn't retrieve the names of the logical volumes
belonging to volume group "/dev/vg00".
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c16t0d0s2 (2/0/0/1/0.0.0) -- Boot Disk
/dev/dsk/c18t0d0s2 (2/0/1/1/0.0.0) -- Boot Disk
No Boot Logical Volume configured
Root: ??? on: /dev/dsk/c16t0d0s2
/dev/dsk/c18t0d0s2
Swap: ??? on: /dev/dsk/c16t0d0s2
/dev/dsk/c18t0d0s2
Dump: ??? on: /dev/dsk/c16t0d0s2, 0
Current path "/dev/dsk/c32t0d0" is an alternate link, skip.
Current path "/dev/dsk/c32t0d1" is an alternate link, skip.
#