Troubleshooting

Creating Missing Device Files

Creating Missing Device Files

When the system boots after installation, the insf command creates the proper device files for the “ctl” interfaces (which are usually adapters) and the SCSI devices attached to the A6828A adapter. Sometimes, though, it does not create all of the needed device files. (One situation where this happens is when you attach SCSI disks to the adapter after the system boots [and the adapter is already installed in the system].) The following is an example of what the output of the ioscan command might look like when you issue it to verify the A6828A installation (see “Verifying Installation” on page 72):

disk

10

0/0/1/0/1.0.0

sdisk

CLAIMED

DEVICE

SEAGATE ST39103LC

 

 

 

/dev/dsk/c1t0d0

/dev/rdsk/c1t0d0

disk

11

0/0/1/0/1.2.0

sdisk

CLAIMED

DEVICE

SEAGATE ST39103LC

 

 

 

/dev/dsk/c1t2d0

/dev/rdsk/c1t2d0

disk

45

0/2/1/0/1.8.0

sdisk

CLAIMED

DEVICE

HP 18.2GST318404LC

 

 

 

/dev/dsk/c9t8d0

/dev/rdsk/c9t8d0

disk

46

0/2/1/0/1.10.0 sdisk

CLAIMED

DEVICE

HP 18.2GST318404LC

 

 

 

/dev/dsk/c9t10d0

/dev/rdsk/c9t10d0

In the ioscan output above, the second line shows the disks’ device files (/dev/... [shown in bold in the example above, for highlighting purposes]). If you see a disk (or other SCSI devices) listed without the second line, that means you are missing that device’s device files. To fix the problem, issue the insf -ecommand, which creates all of the device files.

Chapter 3

67