Dev Nst0 Input Output Error Debian
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn tar /dev/st0 cannot write input/output error more about hiring developers or posting ads with us Unix & Linux Questions Tags Users
Linux Tape Drive Input Output Error
Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like tar cannot read: input/output error operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top tar: /dev/nst0: Cannot write: Input/output tar: cannot write: input/output error error when taking backup up vote 2 down vote favorite When I try to take backup of data more than 1MB in a tape (LTO3) using tar command it showing me the following error. xyz@localhost# tar -cvf /dev/nst0 file1.tar file1.tar tar: /dev/nst0: Cannot write: Input/output error tar: Error is not recoverable: exiting now Output of mt -f /dev/st0 status: SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 0 bytes. Density code 0x44 (LTO-3). Soft error count since last status=0 General status bits on (41010000): BOT ONLINE IM_REP_EN Output of dmesg: st0: Sense Key : Aborted Command [current] st0: Add. Sense: Information unit iuCRC error detected and st0: <
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; http://unix.stackexchange.com/questions/126497/tar-dev-nst0-cannot-write-input-output-error-when-taking-backup it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top HP Storageworks 448 tape drive input/output error with Ubuntu up vote 0 down vote favorite I'm trying to set a backup to tape of a machine http://serverfault.com/questions/125807/hp-storageworks-448-tape-drive-input-output-error-with-ubuntu using flexbackup. However any attempt to write to the tape drive (via either flexbackup or just tar) results in "/dev/st0: Input/output error" The machine seems to recognise the drive (HP Storageworks Ultrium 448) and that there's a tape in it and "mt status" seems to work... "mt -f /dev/st0 rewind" or "erase" throw no errors... root@stor001:/# mt status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 0 bytes. Density code 0x42 (LTO-2). Soft error count since last status=0 General status bits on (41010000): BOT ONLINE IM_REP_EN root@stor001:/# cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: HL-DT-ST Model: DVDRAM GSA-4084N Rev: KS02 Type: CD-ROM ANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 03 Lun: 00 Vendor: HP Model: Ultrium 2-SCSI Rev: S65D Type: Sequential-Access ANSI SCSI revision: 03 "tell" does however root@stor001:/# mt -f /dev/st0 tell /dev/st0: Input/output error Based on a forum post I found, I tried: root@stor001:/# dd if=/dev/zero of=/dev/nst0 bs=1024 count=10 10+0 r
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Hardware & Laptops Tape input/output error FedoraForum Search User http://forums.fedoraforum.org/showthread.php?t=262434 Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Hardware & Laptops Help with your hardware, including laptop issues Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads https://bugs.launchpad.net/bugs/114074 Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 3rd May 2011, 02:46 AM AlwaysLearning Offline Registered User Join Date: Dec 2004 Posts: 40 output error Tape input/output error Hi all, I'm either missing the obvious or have four identically defective tape drives. Each is a Seagate or IBM Travan drive (yes, I know they're old and I need to access the data; they were in Win boxes) using QIC-80/DC-2120 media. I've been trying to solve this using three Fedora boxes (different versions) and one Debian machine. The OS's recognize the drives and they show up as /dev/st0. more /proc/scsi/scsi Attached input output error devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: WDC WD1600JB-00D Rev: 65.1 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: HL-DT-ST Model: DVDRAM GSA-4163B Rev: A103 Type: CD-ROM ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 01 Lun: 00 Vendor: Seagate Model: STT20000A Rev: 8A51 Type: Sequential-Access ANSI SCSI revision: 02 dmesg | grep scsi scsi0 : pata_amd scsi1 : pata_amd scsi 0:0:0:0: Direct-Access ATA WDC WD1600JB-00D 65.1 PQ: 0 ANSI: 5 scsi 1:0:0:0: CD-ROM HL-DT-ST DVDRAM GSA-4163B A103 PQ: 0 ANSI: 5 scsi 1:0:1:0: Sequential-Access Seagate STT20000A 8A51 PQ: 0 ANSI: 2 sd 0:0:0:0: Attached scsi generic sg0 type 0 scsi 1:0:0:0: Attached scsi generic sg1 type 5 scsi 1:0:1:0: Attached scsi generic sg2 type 1 sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray sr 1:0:0:0: Attached scsi CD-ROM sr0 scsi2 : sata_nv scsi3 : sata_nv st 1:0:1:0: Attached scsi tape st0 scsi4 : sata_nv scsi5 : sata_nv dmesg | grep tape st 1:0:1:0: Attached scsi tape st0 With no media in the drives, I get a status report; with media inserted, I get the same input/output errors. Examples (all as root): With tape inserted: # mt -f /dev/st0 status /dev/st0: Input/output error With no tape in drive: # mt -f /dev/st0 status SCSI 2 tape drive: File number=-1,
tar (Ubuntu) Edit Invalid Undecided Unassigned Edit You need to log in to change this bug's status. Affecting: tar (Ubuntu) Filed here by: ytene When: 2007-05-11 Completed: 2007-05-19 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Undecided Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description 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 : root@voyager:/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 root@voyager:/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