How to rebuild the /etc/path_to_inst without un-encapsulating the root disk
Article ID: 100010412
Updated On:
Description
Error Message
cannot open /etc/path_to_instResolution
Note : This will only work if the rootdisk is encapsulated. You don't have to break the root mirror.
Under VERITAS Volume Manager (tm) rootdisk encapsulation, the administrator must take an extra step to ensure the path_to_inst file is created and populated. The difference lies in the root device. This value is not the same as the default offered during the boot; use the value specified for rootdev in the /etc/system file.
At the OK prompt, do the following:
1.
2. At the following prompts, just hit:
Enter default directory for modules [/platform/SUNW,Ultra-5_10/kernel/platform/sun4u/kernel /kernel /usr/kernel]:
3. When the system asks about rebuilding the path_to_inst, type
4. When you get to the following prompt, enter/
System will now boot OK.
Under VERITAS Volume Manager (tm) rootdisk encapsulation, the administrator must take an extra step to ensure the path_to_inst file is created and populated. The difference lies in the root device. This value is not the same as the default offered during the boot; use the value specified for rootdev in the /etc/system file.
At the OK prompt, do the following:
1.
boot-ar Rebooting with command: boot-ar Boot device: /pci@1f,0/pci@1,1/ide@3/disk@0,0 File and args:-ar 2. At the following prompts, just hit
Enter filename[kernel/sparcv9/unix]: << --------Hit Enter default directory for modules [/platform/SUNW,Ultra-5_10/kernel/platform/sun4u/kernel /kernel /usr/kernel]:
Name of system file[etc/system]: <<< Hit SunOS Release 5.8 Version Generic_108528-15 64-bit Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved. 3. When the system asks about rebuilding the path_to_inst, type
yes The/etc/path_to_inst on your system does not exist or is empty. Do you want to rebuild this file [n]? yes <<<<--------------type yesroot filesystem type[ufs]: <<<<------------ Hit 4. When you get to the following prompt, enter/
pseudo/vxio@0:0 Enter physical name of root device [/pci@1f,0/pci@1,1/ide@3/disk@0,0:a]:/pseudo/vxio@0:0 <<<<---- Enter this(this comes from /etc/system).System will now boot OK.
Warning: forceload of drv/ide failed Warning: forceload of drv/ide failed Warning: forceload of drv/pci failed Starting VxVM restoredaemon... VxVM starting in bootmode... configuring IPv4 interfaces:hme0. Hostname:sunhost VxVM starting special volumes( swapvol )... Configuring /dev and/devices Configuring the /devdirectory (compatibility devices) VxVM general startup... The system is coming up. Please wait. starting rpcservices: rpcbind done. Setting netmask of hme0 to255.255.248.0 starting internet domain name server. Setting default IPv4 interface for multicast: add net 224.0/4: gatewaysunhost syslog service starting. Print services started. volume management starting. checking :/usr/sbin/luxadm checking :/usr/lib/liba5k.so.2 checking :/usr/lib/libg_fc.so.2 checking :/usr/lib/sparcv9/liba5k.so.2 checking: /usr/lib/sparcv9/libg_fc.so.2 The system is ready.
Issue/Introduction
How to rebuild the /etc/path_to_inst without un-encapsulating the root disk
Was this article helpful?
Yes
No
Powered by
