Description of problem:
After setting up a test plan for hts the SAS tape drive does not show up in
the test plan.
Version-Release number of selected component (if applicable): R32
Steps to Reproduce:
1. Install HTS.
2. Power down server.
3. Plug in a SAS tape drive into the server ( I used a HP Ultrium LTO 448 SAS )
4. Turn on the tape drive and insert a tape.
5. Turn the server back on and boot to RHEL 5.
6. Open up a terminal and type:
->hts server start
->hts print --report plan
The tape drive did not show up in the list of devices to test in the test plan.
I expected the tape drive to show up.
I was testing on a DL380 G5 server with RHEL 5 X86_64 installed. I also tried
to use the "lshal | grep info.udi" command to find the udi but could not
determine the correct udi.
please run "hal-device > hal.log", and attach the file "hal.log" here, please
also attach following three files here:
Created attachment 153397 [details]
Created attachment 153398 [details]
Created attachment 153399 [details]
Created attachment 153400 [details]
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
Created attachment 153481 [details]
Created attachment 153482 [details]
Created attachment 153483 [details]
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
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.
Closing this bug now.