Bug 234661

please run "hal-device > hal.log", and attach the file "hal.log" here, please
also attach following three files here:
  1) "/etc/sysconfig/hwconf"
  2) "/var/log/dmesg"
  3) "/var/hts/plan.xml"

Thanks

Created attachment 153397 [details]
dmesg

Created attachment 153398 [details]
hal.log

Created attachment 153399 [details]
hwconf

Created attachment 153400 [details]
plan.xml

Hi Keith,

I checked the attached 4 files. Both kudzu and HAL can not find any TAPE device.
And I can not find it in dmesg neither. This is strange.

Could you please provide more info as following:
  1) make sure the SAS tape drive is well connected before the system boots;
  2) boot the system, after the system booted, run following commands as root:
      a) # echo ^M | sysreport
      b) # tree /proc/ > /root/proc-tree.log
      c) # tree /sys/ > /root/sys-tree.log
  3) attach three files: "/root/*.tar.bz2" and "/root/proc-tree.log" and
"/root/sys-tree.log" here.

Thanks

Created attachment 153481 [details]
sysreport

Created attachment 153482 [details]
proc-tree.log

Created attachment 153483 [details]
sys-tree.log

Hi Keith,

I didn't see any tape-related device driver been loaded into kernel.

Can you confirm if this SAS tape drive(HP Ultrium LTO 448 SAS) works well under
RHEL5 ?  Is there a proper device name for this tape drive under "/dev/"
directory ? If yes, could you manually run following command to verify if it works:
    #  mt -f /dev/DEVICE_NAME rewind

Thanks

The HBA I used to plug the tape drive into the server did not have a driver 
installed.  I used a Sputnik SAS card instead and it worked fine.

-Keith

That's great. 

Closing this bug now.