Software ProblemsNew devices may require that the appropriate
/devicesfiles be created. This can be done through use of the
diskscommands, but it is usually done by performing a
boot -rfrom the
Once the system is back, the root user should be able to run
format and see the disk listed as available. The disk can then
be partitioned and labelled with
format and have filesystems
mkfs, as appropriate.
The presence of the appropriate
/devices files can be verified by running the commands
ls -lL /dev/dsk and
ls -lL /dev/rdsk and making
sure that they are block and character special files respectively, with
major numbers depending on the driver used. (See the
man page if you are not sure what this means.)
Files that can cause problems with hard drive connectivity include:
Problems with the
/devices files can be corrected directly by removing the
offending files and recreating them, either directly with
ln -s or indirectly with
boot -r (as appropriate).
Hardware ProblemsThe most common sources of hard drive connectivity problems (once the device files are built) are loose cables and terminators. Check these first before proceeding.
The system SCSI buses can be probed at the
To set this up, perform the following:
ok> setenv auto-boot? false
ok> setenv auto-boot? true
This will give a hardware mapping of all SCSI devices on the system.
If the hard drive in question does not appear, you have either a hardware
problem or a PROM search path problem. To check for the PROM search
path problem, run the following:
Look for the
parameters and make sure that they are set to the default for