/etc/path_to_inst Post: 302108434

Sponsored Content

Special Forums Hardware Filesystems, Disks and Memory /etc/path_to_inst Post 302108434 by ailnilanjan on Monday 26th of February 2007 01:08:23 PM

02-26-2007

Registered User

Quote:

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

Quote:

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.

Thanks Ralph

It works as i have the V490 with the same hardware, you may say it a xerox copy. It worked when i was setting up the root device.

The system is now fine.

I can give the entire procedure by recalling the entire activites what i performed during recovery.

Code:

1- # boot cdrom -s (inserting the Solaris OS CD in the cdrom).
2- #fsck -y /dev/rdsk/c0t0d0s0 
3- #mkdir /a
4- #mount /dev/dsk/c0t0d0s0 /a
5- #grep rootdev /a/etc/system

The result will be something like this :
*       rootdev:        Set the root device.  This should be a fully
*               rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
rootdev:/pseudo/md@0:0,0,blk       (for example)
The line that needs to be noted is the line beginning with rootdev. In the above example, the line "rootdev:/pseudo/md@0:0,0,blk" should 
be the line noted.

6- #mv /a/etc/path_to_inst /a/etc/orig.path_to_inst
7- #init 0
8- ok>boot -ar
Resetting... 
Software Power ON
Clock board TOD does not match TOD on any IO board.
Clock board TOD does not match TOD on any IO board.

slot Sun Enterprise 4000/5000, No Keyboard
OpenBoot 3.2.27, 320 MB memory installed, Serial #7923805.
Copyright 2000 Sun Microsystems, Inc.  All rights reserved
Ethernet address 8:0:20:78:e8:5d, Host ID: 8078e85d.

Rebooting with command: boot -ar
Boot device: /sbus@3,0/QLGC,isp@0,10000/sd@8,0:a  File and args: -ar
|
NOTICE: 64-bit OS installed, but the 32-bit OS is the default
 for the processor(s) on this system.
 See boot(1M) for more information.

Booting the 32-bit OS ...

9- Enter filename [kernel/unix]: (press enter)
Enter default directory for modules [/platform/SUNW,Ultra-Enterprise/kernel /platform/sun4u/kernel /kernel /usr/kernel]: 

10- Name of system file [etc/system]: (press enter)  
SunOS Release 5.8 Version Generic_117350-02 32-bit
Copyright 1983-2003 Sun Microsystems, Inc.  All rights reserved.
/
11- The /etc/path_to_inst on your system does not exist or is empty.
 Do you want to rebuild this file [n]? y
root filesystem type [ufs]: 

12- Enter physical name of root device
[/sbus@3,0/QLGC,isp@0,10000/sd@8,0:a]: <ENTER ROOTDEV noted  ABOVE in BOLD HERE >

13- After the system boots check for the presence of the file
cd /etc/
ls -l

Love
Nil

ailnilanjan

View Public Profile for ailnilanjan

Find all posts by ailnilanjan

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?

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"...

3. Solaris

path_to_inst file question

When path_to_inst file get created? Can we manually edit it? Thanks

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...

LEARN ABOUT MINIX

path_to_inst

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)