5.1b Adding devices and bus id

[Alice Daniel]

ES45 server running 5.1b os. Added a SCSI adapter to support specialized hardware. There are 4 buses on this system. Have had to move the card around several times and each time it is moved to a dift slot, the SCSI bus id increments. It's now up to bus 9. Why is the bus incrementing when there are only 4 scsi buses on this system?

Also, currently getting a msg (after the last relocation of the scsi card): "Failed to initialize the adapter. No associated hardware_id, bus, target, or lun" This error occured after I using setld -d to uninstall the driver associated with the device and reloading it using setld -l

[Steven Schweda]

> Why is the bus incrementing [...]

Because you keep moving the SCSI card? A
SCSI card in a new location is seen as a new
SCSI card. If you put it back into one of
the old locations, then it should be
(re-)recognized with an old identity. I
assume that it's similar to what happened
here (for example):

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1322297

> [...] I using setld -d to uninstall the
> driver associated with the device [...]

Which device is "the device"? (Deleting some
device files might have been a better
approach.) I've never gotten into this kind
of trouble, so I know nothing, but have you
tried building a new kernel?

"man dfsmgr"?

[Steven Schweda · Accepted solution]

> "man dfsmgr"?

Oops. "dsfmgr".

[Alice Daniel]

I did the following (not able to move card, no hardware personnel available today) Very little experience with 5.1b, so specifics would be appreciated:

(1) "hwmgr -view devices" The output was
hwid=119 /dev/disk/dsk11c ... location=bus-7-targ-2-lun-0
(2) "hwmgr delete component -id 119" - successful
(3) "dsfmgr -R hwid 119" - no output

(3a) "dsfmgr -m dsk11 nx0" (my special char device) - got error msgs

(4) setld -d
(5) rebooted the system
(6) setld -l output (to re-install the driver)
(7) doconfig -c
(8) copied vmunix and rebooted

(9) "hwmgr -view devices" - 120:/dev/disk/dsk11c ... bus-7-targ-2-lun-0


Output of /usr/var/messages file:
InitAdapter
cam_logger: SCSI event packet
cam_logger: No associated hardware_id, bus, target, or lun
InitDriver
Failed to initialize Adapter
scsi8 at aha)chim5 slot 0 rad 0

[Pieter 't Hart]

4) setld -d
(5) rebooted the system
(6) setld -l output (to re-install the driver)
(7) doconfig -c
(8) copied vmunix and rebooted

is not the way to add support for the controller in the kernel.
it should be
1) b -fi genvmunix
2) sizer -n
3) compare with
4) modify with lines from in respect to driver
(probably something like "config_driver itpsa")
5) doconfig -c
6) copy vmunix and reboot

Pieter

[Alice Daniel]

for the sizer -n command, what would be an example for the filename?

[Pieter 't Hart]

you're free to choose any name and location
like "/tmp/sizerconfig" or "/sys/conf/"
or "$HOME/myconfig"
as long as you can find it to compare with "/sys/conf/"

(you can use "diff" to do that)

[Alice Daniel]

Thanks to All! Problem resolved...

ISSUE: scsi card supporting a custom device was moved several times in the es45 server. As a result, "unused" scsi ids created. The custom device was limited to using scsi device < 4 (scsi0, for example).

SOLUTION:
(1) "hwmgr -view devices" to get hw_id of custom device
(2) Used "sysman - hardware view" graphic
(3) used "hwmgr -show name" and noticed that the unused scsi ids were listed, but not on the graphics.
(4) "hwmgr delete component -id (5) since scsi card to support the custom device was still installed, could not delete it.
(6) shutdown the system, removed the scsi card for custom hardware, rebooted the system the used "hwmgr delete component -id to remove scsi7
(7) re-installed the card and rebooted. The system selected the unused scsi id (0).
(8) Successfully accessed the custom device!

[Alice Daniel]

The forum was extremely helpful in getting me on the right track. The timeliness of your responses is exceptional. Hopefully, my solutions notes will assist others.