Public bug reported: Binary package hint: tar
Ubuntu 6.10/AMD64 on Tyan Thunder K8W with an Adaptec Ultra160 PCI SCSI Card and a Freecom (HP) DAT72 Tape Deck. Hardware ID of the deck is /dev/st0 If I attempt a backup using, for example, the syntax tar cvfz /dev/st0 /home/ytene/data I am rewarded with a spooling tape drive and a scrolling display of files being written to the tape. So far so good. However, if I try and catalog the tape - or restore from it, using the syntax tar tvf /dev/st0 or tar xvf /dev/st0 all that I get for my trouble is the following error message : [EMAIL PROTECTED]:/home/ytene# tar tvf /dev/st0 tar: /dev/st0: Cannot read: Input/output error tar: At beginning of tape, quitting now tar: Error is not recoverable: exiting now [EMAIL PROTECTED]:/home/ytene# I did some basic trawling around and came upon the following reference:- http://lists.freebsd.org/pipermail/f...er/021514.html [forgive the fact that this is a bsd site and not specifically linux related - I think the tools are largely common] and I tried to follow the suggestions given there, but without success. These failures seem to be 100% consistent and repeatable. I have tried to erase the tape back to "new" state, by using mt -f /dev/st0 erase which, for 72Gb tapes, takes an age! However, this makes no difference. I have tried brand new tapes, with the same results. As a final check, I have rebooted this machine into WindowsXP and tried to use NTBackup to prove the tape hardware. This works perfectly. I am therefore pretty confident that my hardware and tape media are all OK. What's really puzzling/frustrating to me is that I am *sure* I've had this working before. Maybe not on 6.10, but almost certainly on 6.04 or 5.10. Obviously slightly concerned as my ubuntu machine is where I do all my serious work... so would like to have a reliably working backup solution. I'd really appreciate any tests or steps I can take to diagnose and preferably fix this problem... If I cat the contents of /dev looking for objects beginning with /dev/st* I get the following list : /dev$ ls -l st* crw-rw---- 1 root tape 9, 0 2007-05-10 17:26 st0 crw-rw---- 1 root tape 9, 96 2007-05-10 17:26 st0a crw-rw---- 1 root tape 9, 32 2007-05-10 17:26 st0l crw-rw---- 1 root tape 9, 64 2007-05-10 17:26 st0m lrwxrwxrwx 1 root root 15 2007-05-10 17:26 stderr -> /proc/self/fd/2 lrwxrwxrwx 1 root root 15 2007-05-10 17:26 stdin -> /proc/self/fd/0 lrwxrwxrwx 1 root root 15 2007-05-10 17:26 stdout -> /proc/self/fd/1 If I use KInfoCenter to describe the hardware that it can see within the "SCSI" environment in the host, I see the following information : Attached devices: Host: scsi0 Chanel: 00 Id: 03 Lun: 00 Vendor: HP Model: C7438A Rev: V303 Type: Sequential-Access ANSI SCSI revision: 03 If I go to /var/log/messages and grep for the word 'scsi', I get some more interesting and potentially useful information : May 10 17:27:10 voyager kernel: [ 68.065873] scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 May 10 17:27:10 voyager kernel: [ 68.477980] scsi1 : sata_sil May 10 17:27:10 voyager kernel: [ 68.691382] scsi2 : sata_sil May 10 17:27:10 voyager kernel: [ 69.073484] scsi3 : sata_sil May 10 17:27:10 voyager kernel: [ 69.453342] scsi4 : sata_sil May 10 17:27:10 voyager kernel: [ 69.453384] scsi: waiting for bus probes to complete ... May 10 17:27:10 voyager kernel: [ 71.751748] sd 1:0:0:0: Attached scsi disk sda May 10 17:27:10 voyager kernel: [ 71.793743] sd 3:0:0:0: Attached scsi disk sdb May 10 17:27:10 voyager kernel: [ 71.838513] sd 4:0:0:0: Attached scsi disk sdc May 10 17:27:10 voyager kernel: [ 79.406284] st 0:0:3:0: Attached scsi tape st0 Please note how the first line shows that the kernel has loaded an Adaptec AIC7XXX SCSI Driver [Rev 7.0] when in fact the card that I have fitted to this machine is quoted as an "Adaptec SCSI Card 19160 Ultra 160 SCSI controller. I am not sure if this problem is being caused by my kernel loading the wrong driver type for this card... ? Please also note, from the last line above, how the kernel appears to be identifying the tape drive as device st0. So I'm confident that at least the OS is seeing the hardware and trying to talk to it. I am as close as I can get to being positive that I have had this working with an earlier release of ubuntu - maybe 5.10. If necessary I will try and re-install to that earlier version and try and prove that I can get the tape deck to work. I hope that the above information is useful and hopefully sufficient to help diagnosis. Please let me know if there is any more information that I can provide to help. Thanks and Regards ** Affects: tar (Ubuntu) Importance: Undecided Status: Unconfirmed -- tar fails with "input/output" error (SCSI Tape Deck) https://bugs.launchpad.net/bugs/114074 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
