Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

1. Mount all file systems:
# /sbin/mountall
2. Disable DNS so that /etc/hosts is used:
# mv /etc/resolv.conf /etc/resolv.conf.save
3. Set your client's host name:
# /sbin/rc1.d/S320hostname start
4. Set up loop back networking:
# /sbin/rc2.d/S008net.init start
5. Start the networking daemon:
# swagentd
6. Start the recovery tool you intend to use [make_tape_recovery/make_recovery]:
# [make_tape_recovery/make_recovery]
NOTE: The -s option of make_tape_recovery is not supported in the single user mode.
7. When complete, return the resolv.conf file to its original location:
# mv /etc/resolv.conf.save /etc/resolv.conf
After you have shutdown to single user mode, use this procedure:
1. Mount all file systems:
# /sbin/mountall
2. Start the SD-UX daemon:
# swagentd -r
3. Start the recovery tool you intend to use [make_tape_recovery/make_recovery]:
# [make_tape_recovery/make_recovery]
NOTE: The -s option of make_tape_recovery is not supported in the single
user mode.
Why are there invalid disk device files left behind after some recoveries?
When Ignite-UX performs a recovery operation, it can create device files for disks that are discovered
when the client boots from the installation kernel. During the recovery process, Ignite-UX performs
actions to preserve the original instance numbers of those disks. After the final client boot, the disks
will have the original instance numbers. However, clean up is performed on disk devices which
no longer have hardware devices associated with them.
The existence of these device files presents no problem to HP-UX. This is only known to cause
problems with one third party product as it expects all disk devices to have hardware associated
with them. To remove the device files that no longer have hardware associated with them, the
following commands must be executed:
# lssf /dev/*dsk/* | grep '\?\?\?'
# rmsf "names of files found with the previous command"
Frequently asked questions 49