Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Path_to_inst
- Thread starter ejmilne
- Start date
On a SPARC running Solaris it is ok to remove BOTH /etc/path_to_inst
and /etc/path_to_inst.old
After removing you should have no problem doing a boot -a OR a boot -ar OR
boot -arv
The /etc/path_to_inst will be rebuilt without fail unless some other file
corruption has occurred.
On a x86 architecture running Solaris there might be difficulties if BOTH
the /etc/path_to_inst AND /etc/path_to_inst.olg files are removed.
If there is ever an issue where you can not boot off the boot disk due to
a problem of the boot program not finding /etc/path_to_inst you should
boot off of cdrom (boot -sw cdrom) and copy the /etc/path_to_inst file
contained on the cdrom to the /etc/path_to_inst on the boot disk.
To do this simply boot off the cdrom (boot -sw cdrom) and mount the boot disk
on /a
Then simply copy /etc/path_to_inst to /a/etc/path_to_inst
If this does not allow you to boot then your problems deal more than just with
/etc/path_to_inst
Yass
and /etc/path_to_inst.old
After removing you should have no problem doing a boot -a OR a boot -ar OR
boot -arv
The /etc/path_to_inst will be rebuilt without fail unless some other file
corruption has occurred.
On a x86 architecture running Solaris there might be difficulties if BOTH
the /etc/path_to_inst AND /etc/path_to_inst.olg files are removed.
If there is ever an issue where you can not boot off the boot disk due to
a problem of the boot program not finding /etc/path_to_inst you should
boot off of cdrom (boot -sw cdrom) and copy the /etc/path_to_inst file
contained on the cdrom to the /etc/path_to_inst on the boot disk.
To do this simply boot off the cdrom (boot -sw cdrom) and mount the boot disk
on /a
Then simply copy /etc/path_to_inst to /a/etc/path_to_inst
If this does not allow you to boot then your problems deal more than just with
/etc/path_to_inst
Yass
- Thread starter
- #3
Hi Yass,
Thanks for your reply - I have tried to do a boot -arv and it fails to rebuild the /etc/path_to_inst so I guess this means that there is other file corruption.
The system does come up but all the filesystems are read-only.....
I am new to solaris (my experience is in AIX) do you know of any commands where I can check for disk errors etc etc?
Thanks again,
Emma
Thanks for your reply - I have tried to do a boot -arv and it fails to rebuild the /etc/path_to_inst so I guess this means that there is other file corruption.
The system does come up but all the filesystems are read-only.....
I am new to solaris (my experience is in AIX) do you know of any commands where I can check for disk errors etc etc?
Thanks again,
Emma
Did it ask you if you wanted to recreate the path_to_inst?
Try this
boot from cdrom
mount /dev/dsk/c.t.d.s. /a
locate path_to_inst file under /tmp with find
drvconfig -r /a/devices -p /tmp/path/to/path_to_inst
devlinks -r /a/devices
disks -r /a/devices
touch /a/reconfigure
cp /tmp/path/to/path_to_inst to /a/etc/path_to_inst
Note that devices might move around if you use this method depending on the
order you populated cards in the past (this is exactly what
/etc/path_to_inst tries to preserve).
--
| Mike Nixon
| Unix Admin
|
----------------------------
Try this
boot from cdrom
mount /dev/dsk/c.t.d.s. /a
locate path_to_inst file under /tmp with find
drvconfig -r /a/devices -p /tmp/path/to/path_to_inst
devlinks -r /a/devices
disks -r /a/devices
touch /a/reconfigure
cp /tmp/path/to/path_to_inst to /a/etc/path_to_inst
Note that devices might move around if you use this method depending on the
order you populated cards in the past (this is exactly what
/etc/path_to_inst tries to preserve).
--
| Mike Nixon
| Unix Admin
|
----------------------------
- Thread starter
- #5
Emma, do you use DiskSuite on the System? (are there som /dev/md/... entries in /etc/vfstab?)
Regards
-- Franz
Sorry I'm not a native spaeker, I'm from Munich, Germany - "Home of the Whopper", oh no, "Home of the Oktoberfest" ;-)
Solaris System Manager; I used to work for Sun Microsystems Support (EMEA) for 5 years
Regards
-- Franz
Sorry I'm not a native spaeker, I'm from Munich, Germany - "Home of the Whopper", oh no, "Home of the Oktoberfest" ;-)
Solaris System Manager; I used to work for Sun Microsystems Support (EMEA) for 5 years
- Thread starter
- #8
Hi,
Thanks for your reply(s), yes, I believe we are using DiskSuite, but I dont know how to use it!
The hardware we are using is Sun Sunfire 280R....
Also, can anyone tell me the equivalent of lsdev (AIX) in solaris? I am trying to find out whether the tape device that is connected to the system is configured....
Thanks again,
Emma
Thanks for your reply(s), yes, I believe we are using DiskSuite, but I dont know how to use it!
The hardware we are using is Sun Sunfire 280R....
Also, can anyone tell me the equivalent of lsdev (AIX) in solaris? I am trying to find out whether the tape device that is connected to the system is configured....
Thanks again,
Emma
boot from CDROM and disable SDS by editing /etc/vfstab (replace eg /dev/md/dsk/d1 by /dev/dsk/c0t0d0s0 replace only for / /usr /var Filesystems, uncomment any other filesystems, you do not need them right now), further edit /etc/system, threr is an entry rootdev, comment this out.
rename the following Files from filename to eg _filename to stop Solaris init Process from starting the Scripts
/etc/rc0.d/K34svm.sync
/etc/rc1.d/K34svm.sync
/etc/rc2.d/S95svm.sync
/etc/rcS.d/K34svm.sync
/etc/rcS.d/S35svm.init
shutdown the system to OBP
in OBP type: boot -a
The system should come up again without SDS
There should be a /etc/lvm/md.tab File containing the configuration; you can run "metainit metadevicename" to setup SDS again; do not forget to rename the _filename again to start SDS services!
I you need assistance just write a small post
There is a lot of Documentation in
Your Tapedrive is /dev/rmt/0 if you boot from CD (run ufsdump 0f /dev/rmt/0cn /dev/dsk/c0t0d0s0 to run a Backup of your Filesystem on c0t0d0s0
Regards
-- Franz
Sorry I'm not a native spaeker, I'm from Munich, Germany - "Home of the Whopper", oh no, "Home of the Oktoberfest" ;-)
Solaris System Manager; I used to work for Sun Microsystems Support (EMEA) for 5 years
rename the following Files from filename to eg _filename to stop Solaris init Process from starting the Scripts
/etc/rc0.d/K34svm.sync
/etc/rc1.d/K34svm.sync
/etc/rc2.d/S95svm.sync
/etc/rcS.d/K34svm.sync
/etc/rcS.d/S35svm.init
shutdown the system to OBP
in OBP type: boot -a
The system should come up again without SDS
There should be a /etc/lvm/md.tab File containing the configuration; you can run "metainit metadevicename" to setup SDS again; do not forget to rename the _filename again to start SDS services!
I you need assistance just write a small post
There is a lot of Documentation in
Your Tapedrive is /dev/rmt/0 if you boot from CD (run ufsdump 0f /dev/rmt/0cn /dev/dsk/c0t0d0s0 to run a Backup of your Filesystem on c0t0d0s0
Regards
-- Franz
Sorry I'm not a native spaeker, I'm from Munich, Germany - "Home of the Whopper", oh no, "Home of the Oktoberfest" ;-)
Solaris System Manager; I used to work for Sun Microsystems Support (EMEA) for 5 years
- Status
