12-23-2004
You could try to reinitialize your Drive(s) with
devfsadm
Also have a look at your /etc/path_to_inst and
prtconf -v
If it donīt work you could make a reconfigure boot with
reboot -- -r
You could make a reconfigure boot where all devices entries are new written with
reboot -- -pr
If that donīt work try a other drive
![Smilie Smilie](https://www.unix.com/images/smilies/smile.gif)
8 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I'm trying to moun my external USB Mass Storage Drive (80GB) in my Solaris 9 box, I am new to Solaris, and kind of new to linux / unix variants. The external HD contains windows files, but I will be using it as a central storage area for my windows/ linux clients.
Thanks
--
N:confused:C (1 Reply)
Discussion started by: N0C717
1 Replies
2. Solaris
While mounting nfs file system I get the following error .
# mount -F nfs jewelex:/back2 /oback2
nfs mount: jewelex:/back2: Permission denied
Following is the permission for oback2
drwxr-xr-x 2 root other 512 Apr 9 18:39 oback2
Directory permission on jewelex server is ... (4 Replies)
Discussion started by: Hitesh Shah
4 Replies
3. Solaris
Hi,
I have x86 machine with P4, 512 MB with 17" ViewSonic TFT screen. I installed Solaris 10 and i am geeting the error messages like "Notice: failed to initialize inband hot plug controllers." while booting. Later am getting the shrinked window in single line.
I thought itd because of video... (4 Replies)
Discussion started by: paventhan
4 Replies
4. Solaris
On my Solaris 10 server, I want to share out the directory /export/home/data, so in the /etc/dfs/dfstab file, I have this line:
share -F nfs -o rw /export/home/data
In the /etc/hosts.equiv file, I have this:
+
When I do a "ps -ef" command, I see that the "nfsd' daemon is started.
... (2 Replies)
Discussion started by: serendipity1276
2 Replies
5. UNIX for Dummies Questions & Answers
How can I install Solaris 10 x86 on a machine without a DVD drive? Is there a way to boot from a flash stick or install it through a network? Any help will be appreciated. (1 Reply)
Discussion started by: Bradj47
1 Replies
6. Solaris
Is there a way to install Solaris 10 x86 with an external DVD drive that connects through the USB port? I would think I would run GRUB off of a floppy disk and somehow use that to make it look to the USB port to boot from but I don't know how to do that. Can anyone help me out? (1 Reply)
Discussion started by: Bradj47
1 Replies
7. Solaris
Is it possible to boot an existing Solaris 10 update 1 from boot dvd that I run on p3(1 ghz -512 mb ram).
I have got a dual boot sys - the other os is win xp that I need to reinstall but that removes the mbr so, is there any way to recover mbr after the installation of xp?
Thanks. (3 Replies)
Discussion started by: vectrum
3 Replies
8. Solaris
Hi All,
Has anyone else come across a network interface issue after installing Solaris x86 11.3 from the 'live' DVD?
I have had issues myself and also found others have similar issues.
On my systems, installing Solaris 11.3 works fine but after rebooting (from the hard disk root... (4 Replies)
Discussion started by: hicksd8
4 Replies
LEARN ABOUT MOJAVE
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)