I was using V490 server with StoreEdge 3500 on Solaris 5.8 platform.
It got crashed when the optical link between 3500 and V490 got failed.
After a long effort it is now getting messege like below,
Rebooting with command: boot
Boot device: /pci@9,600000/SUNW,qlc@2/fp@0.0/disk@w500000e011d37831,0:a File and args:
SunOS Release 5.8 Version Generic_117350-20 64-bit
Cannot open '/etc/path_to_inst'
Program terminated
{3}ok
Now the optical link is up.
It fails all boot commands and returns back with these kind of messege.
Nebody having any idea bout the /etc/path_to_inst file please reply.
With Heartiest Greetings
Nil.
Last edited by ailnilanjan; 02-25-2007 at 05:26 PM..
boot -ar might work, but I believe that the user will be prompted for some stuff. I'm not sure if taking the defaults will work with path_to_inst missing.
boot -ar might work, but I believe that the user will be prompted for some stuff. I'm not sure if taking the defaults will work with path_to_inst missing.
/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.
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
Glad it worked. And thanks much for putting in the entire procedure. That will come in handy if somebody searches on /etc/path_to_inst and finds this thread in the future.
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)
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)
