![]() |
|
|
|||||||
| Home | Forums | Register | Rules & FAQ | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| Filesystems, Disks and Memory Questions involving NAS, SAN, RAID, Robotic Libraries, backups, etc go here. |
Other UNIX.COM Threads You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| path_to_inst file question | mokkan | SUN Solaris | 2 | 05-16-2008 08:59 PM |
| path_to_inst output for usb storage device | montana77 | UNIX for Dummies Questions & Answers | 0 | 04-05-2008 04:04 AM |
| cannot open /etc/path_to_inst file | frustrated1 | SUN Solaris | 4 | 03-05-2004 08:24 AM |
![]() |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|||
|
/etc/path_to_inst
Hello Friends
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 01:26 PM. |
| Forum Sponsor | ||
|
|
|
|||
|
Quote:
i am suspecting that path_to_inst is missing. what can i do now? is there any way to restore it? |
|
|||
|
/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 |
|||
| Google UNIX.COM |