Some more details recorded in the ddrescue logfile, but not sure how to interpret it:
(My apologies that this may not be the right forum on this...) # Rescue Logfile. Created by GNU ddrescue version 1.16 # Command line: ddrescue /dev/st0 /tmp/lto/tar logfile # current_pos current_status 0x11E6E9E8000 / # pos size status 0x00000000 0x0416D600 - 0x0416D600 0x007E4600 / 0x04951C00 0x0381BC00 - 0x0816D800 0x027E4600 / 0x0A951E00 0x0181C000 - 0x0C16DE00 0x007E4400 / 0x0C952200 0x0381B800 - 0x1016DA00 0x067E4600 / 0x16952000 0x0181C000 - 0x1816E000 0x027E4400 / 0x1A952400 0x0181C000 - 0x1C16E400 0x007E4200 / 0x1C952600 0x0381B600 - 0x2016DC00 0x0E7E4600 / 0x2E952200 0x0181C000 - 0x3016E200 0x067E4400 / 0x36952600 0x0181C000 - ... Peter -----Original Message----- From: Chiu, Peter (STFC,RAL,RALSP) Sent: 15 June 2012 17:45 To: Antonio Diaz Diaz; [email protected] Cc: Chiu, Peter (STFC,RAL,RALSP) Subject: RE: [Bug-tar] tar: unable to read LTO4 tapes on a LTO5 drive using tar thanks, Antonio, I have downloaded ddrescue, and invoked this command: ddrescue /dev/st0 /tmp/lto/tar logfile The command is still running, and so far the logfile is showing: frost:/tmp/lto # cat logfile # Rescue Logfile. Created by GNU ddrescue version 1.16 # Command line: ddrescue /dev/st0 /tmp/lto/tar logfile # current_pos current_status 0x00000000 ? # pos size status 0x00000000 0x7FFFFFFFFFFFFFFF ? Not sure what it means. Peter ________________________________________ From: Antonio Diaz Diaz [[email protected]] Sent: 15 June 2012 16:05 To: [email protected] Cc: Chiu, Peter (STFC,RAL,RALSP) Subject: Re: [Bug-tar] tar: unable to read LTO4 tapes on a LTO5 drive using tar Paul Eggert wrote: >>we are getting io errors. > > Possibly that's because the tape is bad. If this is the case and the cause are media errors, you can try reading the tape with ddrescue[1]. [1] http://www.gnu.org/software/ddrescue/ddrescue.html Regards, Antonio. -- Scanned by iCritical.
