Cannot load kernel drivers for IBM tape drives

[jerrym]

I am getting these error messages on bootup for loading IBM ULTRIUM TAPE devices. 

HP-UX 11.23  9000/800/rp8420

Configure GES driver for IBM Tape and Library Devices
Output from "/sbin/rc2.d/S999atdd_cfg start":
----------------------------
Unable to update DPF_KEY! 9
unknown      6  0/0/2/1/0/4/0.1.0.0.0.0.2        atdd      UNCLAIMED   UNKNOWN      IBM     ULTRIUM-TD4
unknown      7  0/0/2/1/0/4/0.1.0.0.0.0.3        atdd      UNCLAIMED   UNKNOWN      IBM     ULTRIUM-TD4
unknown      8  0/0/4/1/0/4/1.1.2.0.0.0.1        atdd      UNCLAIMED   UNKNOWN      IBM     ULTRIUM-TD4
unknown      9  0/0/4/1/0/4/1.1.2.0.0.0.2        atdd      UNCLAIMED   UNKNOWN      IBM     ULTRIUM-TD4
unknown     10  0/0/6/1/0/4/1.1.8.0.0.0.1        atdd      UNCLAIMED   UNKNOWN      IBM     ULTRIUM-TD4
unknown     11  0/0/6/1/0/4/1.1.8.0.0.0.2        atdd      UNCLAIMED   UNKNOWN      IBM     ULTRIUM-TD4
unable to determine maj number
mknod: illegal number
usage: mknod name b|c major minor
       mknod name p
unable to determine maj number
mknod: illegal number
usage: mknod name b|c major minor
       mknod name p
unable to determine maj number
mknod: illegal number
usage: mknod name b|c major minor
       mknod name p
unable to determine maj number
mknod: illegal number
usage: mknod name b|c major minor
       mknod name p
unable to determine maj number
mknod: illegal number
usage: mknod name b|c major minor
       mknod name p
unable to determine maj number
mknod: illegal number
usage: mknod name b|c major minor
       mknod name p
Unable to update DPF_KEY! 9

[jerrym · Accepted solution]

Upgrading the atdd driver from 5.6.0.43 to 5.6.2.20, from IBM webpage, fixed the problem.

ioscan was showing:

unknown   2  0/0/4/1/0/4/1.1.2.0.0.0.1    atdd     UNCLAIMED   UNKNOWN      IBM     ULTRIUM-TD4

Which uses the atdd driver.

swlist showed we were running :

atdd                          5.6.0.43       GES IBM tape and changer device driver for TotalStorage

Storage group had upgraded the drives in the storage library which had newer firmware that was not compatible

with our attd driver on HP server. Once we rebooted the server and it trided to communicate with the remote

drives this problem started.