Hello, Thank you for the reply. Alan Stern wrote: > It helps, but not very much. The log shows that the drive failed to carry > out a WRITE request, and from that point on it returned error status for > every command, even after it was reset. This suggests there is a nasty > bug in the tape drive. I see that the 'point' you said was below, but I don't have enough knowledge to see the reason why it suggests a nasty bug in the tape drive: > usb-storage: Command WRITE_6 (6 bytes) > usb-storage: 0a 01 00 00 40 00 00 00 00 00 00 00 > usb-storage: Bulk command S 0x43425355 T 0x6e738 Trg 0 LUN 0 L 32768 F 0 > CL 6 > usb-storage: Bulk command transfer result=0 > usb-storage: usb_stor_transfer_partial(): xfer 32768 bytes > usb-storage: command_abort() called > usb-storage: usb_stor_bulk_msg() returned -104 xferred 0/32768 > usb-storage: usb_stor_transfer_partial(): transfer aborted > usb-storage: Bulk data transfer result 0x3 > usb-storage: -- transport indicates command was aborted In order to see the reason, I think I need to look deeper into the modules, drivers or kernel (also the hardware is, certainly). Is it useful to enable the debug options for them? (At first, though, I will learn how to enable it, and which lower level part of Linux software have the debug options!) I would like to narrow down the cause as much as I can. Any advise or idea is much appreciated. Takashi Yoshida ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
