Home > Output Error > Bin/tar /dev/st0 Cannot Write Input/output Error

Bin/tar /dev/st0 Cannot Write Input/output Error

Contents

Thanks Sascha #14 tafkaz, Oct 10, 2012 tafkaz Member Joined: Dec 1, 2010 Messages: 65 Likes Received: 0 Hi! But after about some time during the backup process I had again that input/output error!!! But of course some backup software that is able to copy, let's say, three instances then alway remove the oldest....that would be kinda posh... target8:0:3: Domain Validation skipping write tests#lsmodModule Size Used byaf_packet 29064 2iptable_filter 6912 0ip_tables 16324 1 iptable_filterip6_tables 17476 0x_tables 18308 2 ip_tables,ip6_tablesmicrocode 15372 0firmware_class 13568 1 microcodeapparmor 40736 0loop 21636 0osst 54172 http://onlinetvsoftware.net/output-error/bin-ls-input-output-error.php

I chased this up on the 7th of November, and still haven't had any joy. Do not put tapes with valuable data into the drive until you've found a solution - the drive might damage any tape put into it. in syslog i see: Oct 10 10:17:34 proxmox1 kernel: st0: Sense Key : Aborted Command [current] Oct 10 10:17:34 proxmox1 kernel: st0: Add. Thanks again SaschaClick to expand...

Linux Tape Drive Input Output Error

But never get to restore that. Are you new to LinuxQuestions.org? So sayeth the Shepherd more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts

Maybe that's the problem: tar -tvf /dev/nst0 tar: /dev/nst0: Cannot read: Cannot allocate memory tar: At beginning of tape, quitting now tar: Error is not recoverable: exiting now then i tried: bt 0x0, driver bt 0x0, host bt 0x8). will copy the four directory's and do it in a bzip2 copy, to your tape. Dev St0 Input Output Error Adv Reply March 29th, 2010 #5 calyx View Profile View Forum Posts Private Message Visit Homepage First Cup of Ubuntu Join Date Apr 2005 Location Dublin, Ireland Beans 8 DistroUbuntu

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 Tar Cannot Read: Input/output Error I guess you have to check your data size before copying. 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 Yes, my password is: Forgot your password?

Edit bug mail Other bug subscribers Subscribe someone else • Take the tour • Read the guide © 2004-2016 CanonicalLtd. • Terms of use • Contact Launchpad Support • Blog 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 Hi, Code: mt -f /dev/st0 erase should erase the tape (never tried with lto). I use DDS-3 tapes (12/24 GB).

Tar Cannot Read: Input/output Error

none to backup Copying Apache virtual host configuration .. .. Adv Reply Quick Navigation Hardware Top Site Areas Settings Private Messages Subscriptions Who's Online Search Forums Forums Home Forums The Ubuntu Forum Community Ubuntu Official Flavours Support New to Ubuntu Linux Tape Drive Input Output Error By using this site, you accept the Terms of Use and Rules of Participation. End of content United StatesHewlett Packard Enterprise International CorporateCorporateAccessibilityCareersContact UsCorporate ResponsibilityEventsHewlett Packard LabsInvestor RelationsLeadershipNewsroomSitemapPartnersPartnersFind a PartnerPartner Mt Input Output Error What would be the simplest way of me discovering what type of content is on the tape?

Do you happen to have a link to the enterprising soul's fix? More about the author How does Coruscant get food? Thanks SaschaClick to expand... 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. Tar Cannot Close Input Output Error

After some time I had that known well input/output error. TAR failed! I managed to take a backup once, using also multiple volumes mode, but it only finished without errors by specifying file sizes with the -L option and giving file chunks of check my blog Ubuntu Logo, Ubuntu and Canonical Canonical Ltd.

Hi, I guess you are not at the right tape-position. It's been a difficult problem for me to diagnose since I'm accessing the machine remotely Adv Reply April 27th, 2010 #6 calyx View Profile View Forum Posts Private Message Visit I am therefore pretty confident that my hardware and tape media are all OK.

Stay logged in Proxmox Support Forum Forums > Retired and read only forums > Proxmox VE 1.x: Installation and configuration > Toggle Width Home Contact Us Help Terms and Rules Top

Now copying data again...if that doesn't help, i will give full erase a try! It defaults to 10, but you can make that whatever you like. I come up with the error tar: /dev/nst0: Cannot write: Input/output errortar: Error is not recoverable: exiting nowThe command I am using istar cvf /dev/nst0 I have tried varies things from If anyone has any suggestions, I'd appreciate it Adv Reply March 24th, 2010 #2 trundlenut View Profile View Forum Posts Private Message Cookies and cream Join Date Dec 2008 Location

you can define the number of backups via the storage definition. #19 tom, Feb 17, 2013 tafkaz Member Joined: Dec 1, 2010 Messages: 65 Likes Received: 0 Hi! the handling with mt and such on is an reason why many people like backup-software Udo #12 udo, Oct 10, 2012 tafkaz Member Joined: Dec 1, 2010 Messages: 65 Likes Tried also bacula and tapeware with similar failure results. http://onlinetvsoftware.net/output-error/bin-cat-input-output-error.php Thanx again Sascha #5 tafkaz, Oct 10, 2012 udo Well-Known Member Proxmox VE Subscriber Joined: Apr 22, 2009 Messages: 4,576 Likes Received: 27 tafkaz said: ↑ So i tried to

Thanks! Maybe that is the problem? Forum software by XenForo™ ©2010-2016 XenForo Ltd. tar -tvf /dev/st0 will check the tape list it out for you.

Ah, life's just too easy! Closing the bug, as it seems clear that it's not a tar issue. Then I tried backing up a tar file a little bigger than 4GB.