Sponsored Content
Full Discussion: /etc/path_to_inst
Special Forums Hardware Filesystems, Disks and Memory /etc/path_to_inst Post 302108425 by rhfrommn on Monday 26th of February 2007 11:49:03 AM
Old 02-26-2007
/etc/path_to_inst stores vital information about the devices on your system. If it is damaged or missing the machine will not be able to boot.

To recover you will need to boot off of a CD-Rom or the network, then mount your root partition by hand to copy /etc/path_to_inst back on there. Hopefully you will have a copy on a backup somewhere. I don't think just grabbing /etc/path_to_inst from another server or the CD will work. If you end up having to try that make sure at least you use another V490, hopefully one with exactly the same hardware inside it.

If that doesn't work you may have no choice but to re-install Solaris.

Good luck,
Ralph
 

4 More Discussions You Might Find Interesting

1. Solaris

cannot open /etc/path_to_inst file

In trouble... booted system and error on prom is "cannot open /etc/path_to_inst file" Any suggestions? (4 Replies)
Discussion started by: frustrated1
4 Replies

2. UNIX for Dummies Questions & Answers

path_to_inst output for usb storage device

Hello, I have a sun blade 100 with solaris 10 and am perplexed by the instances of devices that I see when I attach a usb flash stick to one of the ports in the back of the chassis. Here is what I see for USB storage in /etc/path_to_inst: "/pci@1f,0/usb@c,3/storage@3" 0 "scsa2usb"... (0 Replies)
Discussion started by: montana77
0 Replies

3. Solaris

path_to_inst file question

When path_to_inst file get created? Can we manually edit it? Thanks (2 Replies)
Discussion started by: mokkan
2 Replies

4. Solaris

Incorrect fabric WWN and path_to_inst Solaris 9

Hi, Over a period of time we gradually migrated all LUN's from our HP EVA array over to our EMC array. From the server it would appear some files require a tidy up and was wondering what the impact it would have if changes were to be made to the fabric_WWN_map and path_to_inst files and if... (0 Replies)
Discussion started by: jamba1
0 Replies
path_to_inst(4)                                                    File Formats                                                    path_to_inst(4)

NAME
path_to_inst - device instance number file SYNOPSIS
/etc/path_to_inst DESCRIPTION
/etc/path_to_inst records mappings of physical device names to instance numbers. The instance number of a device is encoded in its minor number, and is the way that a device driver determines which of the possible devices that it may drive is referred to by a given special file. In order to keep instance numbers persistent across reboots, the system records them in /etc/path_to_inst. This file is read only at boot time, and is updated by add_drv(1M) and drvconfig(1M). Note that it is generally not necessary for the system administrator to change this file, as the system will maintain it. The system administrator can change the assignment of instance numbers by editing this file and doing a reconfiguration reboot. However, any changes made in this file will be lost if add_drv(1M) or drvconfig(1M) is run before the system is rebooted. Each instance entry is a single line of the form: "physical name" instance number "driver binding name" where physical name is the absolute physical pathname of a device. This pathname must be enclosed in double quotes. instance number is a decimal or hexadecimal number. driver binding name is the name used to determine the driver for the device. This name may be a driver alias or a driver name. The driver binding name must be enclosed in double quotes. EXAMPLES
Example 1: Sample path_to_inst Entries Here are some sample path_to_inst entries: "/iommu@f,e0000000" 0 "iommu" "/iommu@f,e0000000/sbus@f,e0001000" 0 "sbus" "/iommu@f,e0000000/sbus@f,e0001000/sbusmem@e,0" 14 "sbusmem" "/iommu@f,e0000000/sbus@f,e0001000/sbusmem@f,0" 15 "sbusmem" "/iommu@f,e0000000/sbus@f,e0001000/ledma@f,400010" 0 "ledma" "/obio/serial@0,100000" 0 "zs" "/SUNW,sx@f,80000000" 0 "SUNW,sx" FILES
/etc/path_to_inst SEE ALSO
add_drv(1M), boot(1M), drvconfig(1M), mknod(1M) WARNINGS
If the file is removed the system may not be bootable (as it may rely on information found in this file to find the root, usr or swap device). If it does successfully boot, it will regenerate the file, but after rebooting devices may end up having different minor numbers than they did before, and special files created via mknod(1M) may refer to different devices than expected. For the same reasons, changes should not be made to this file without careful consideration. NOTES
This document does not constitute an API. path_to_inst may not exist or may have a different content or interpretation in a future release. The existence of this notice does not imply that any other documentation that lacks this notice constitutes an API. SunOS 5.10 2 Nov 1995 path_to_inst(4)
All times are GMT -4. The time now is 02:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy