IBM Ultrium LTO2 driver lost during reboot

[Smucker]

We recently installed the atape driver for out LTO2 drives to utlize compression. All was working fine until I applied some patches over the weekend and rebooted. The atdd/atdc modules are still in the kernel but the drives are not using these drivers ....any idea why or how to correct?

[Denver Osborn]

compare your /stand/system file to /stand/system.prev, there may have been an etry specific to the atdd/atdc driver that was lost w/ your patch installation's kernel build.

If the driver's in the kernel but not bound, you can bind it using ioscan -M -H (man ioscan). I'm assuming ioscan shows the deviace as UNCLAIMED / UNKNOWN...

hope this helps,
-denver

[Smucker]

The modules are in the kernel and loaded the devices did not get claimed......

[Geoff Wild]

Sounds like you may need to re-install driver - did you follow instructions in:

ftp://ftp.software.ibm.com/storage/devdrvr/Doc/IBM_ultrium_tape_IUG.pdf

Check chapter 17 or 18...

Rgds...Geoff

[Smucker]

Found the problem. The install script places a member into /var/tmp called atdd_response. The atdd member in /sbin/init.d executed this member wich set a variable for autoch....

Well the driver initialization failed because the member was not there (cleaned up after 3 days via our cleanup scripts). Therefore we ran the commands by hand to allow the driver to claim the drives then changed the atdd in /sbin/init.d to not look for this member.

Why IBM placed a member to be permanant in a tmp file directory I'll never know......

[Geoff Wild]

Interesting - we use LT02 drives as well - and we don't have atdd_response on our backup servers - nor anything for atdd in /var/tmp

Which version do you have?

swlist |grep -i atdd
atdd 3.1.0.3 GES IBM Magstar and Ultrium tape device driver



Rgds...Geoff

[Smucker]

version


atdd 3.5.0.20

the file is there for the autoch product. I would imagine if you just installed the atdd then you would not get it..