Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
02-05-2009, 02:20 AM
|
#1
|
LQ Newbie
Registered: Feb 2009
Posts: 16
Rep:
|
Tar binary data such as mp4 and pdf
I encounter a problem when I'm writing binary data (mp4, pdf, etc) to the Linear Tape Open. The command I'm using to write in the Linear Tape Open is tar -cvf /dev/nst0 videos. Below is the result:
Desktop/Simulation/videos/
Desktop/Simulation/videos/20090202/
Desktop/Simulation/videos/20090202/10/
Desktop/Simulation/videos/20090202/10/05-20090202100401-C.idx
Desktop/Simulation/videos/20090202/10/06-20090202100401-C.g723
tar: /dev/nst0: Cannot write: Input/output error
tar: Error is not recoverable: exiting now
How do you write binary data in the Linear Tape Open? Is there another way to do this? Please help. Thanks!
|
|
|
02-05-2009, 03:43 AM
|
#2
|
LQ Guru
Registered: Sep 2003
Location: Bologna
Distribution: CentOS 6.5 OpenSuSE 12.3
Posts: 10,509
|
I don't think the type of file is relevant. Check the status of the tape using
Code:
mt -f /dev/nst0 status
and see the output of dmesg to check for more verbose error messages about /dev/nst0.
|
|
|
02-05-2009, 04:22 AM
|
#3
|
LQ Newbie
Registered: Feb 2009
Posts: 16
Original Poster
Rep:
|
I'm currently using mtx for this but here's the result of checking the tape's status:
Product Type: Tape Drive
Vendor ID: 'HP '
Product ID: 'Ultrium 3-SCSI '
Revision: 'D22H'
Attached Changer API: No
SerialNumber: 'HU107461U4'
MinBlock: 1
MaxBlock: 16777215
SCSI ID: 1
SCSI LUN: 0
Ready: yes
BufferedMode: yes
Medium Type: Not Loaded
Density Code: 0x44
BlockSize: 0
DataCompEnabled: yes
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0x1
DeCompType: 0x1
Block Position: 22
Partition 0 Remaining Kbytes: 399690
Partition 0 Size in Kbytes: 399690
ActivePartition: 0
EarlyWarningSize: 0
NumPartitions: 0
MaxPartitions: 0
And this is what I got when I used dmesg:
st0: Sense Key : Aborted Command [current]
st0: Add. Sense: Scsi parity error
I'm wondering what's the scsi parity error it displayed... Hope this is the problem that holding me to write on the Linear Tape Open.
Last edited by Berris.Oliver; 02-05-2009 at 04:25 AM.
|
|
|
02-05-2009, 04:40 AM
|
#4
|
LQ Guru
Registered: Sep 2003
Location: Bologna
Distribution: CentOS 6.5 OpenSuSE 12.3
Posts: 10,509
|
Yes, I think that's the problem. The SCSI parity error can be due to different reasons. First of all, I'd check if all the connectors are properly inserted.
|
|
|
02-05-2009, 05:02 AM
|
#5
|
LQ Newbie
Registered: Feb 2009
Posts: 16
Original Poster
Rep:
|
I reattached the connector of the scsi and made sure that it is connected with the pc and tape archive firmly. I tried to write the binary data (mp4s) to the Linear Tape Open and the problem is still there. What are the other reasons causing the scsi parity error?
|
|
|
02-05-2009, 09:36 PM
|
#6
|
LQ Newbie
Registered: Feb 2009
Posts: 16
Original Poster
Rep:
|
By the way, I'm using the Overland Storage ARCvault 12 and ARCvault 24 for the Tape Archive. When I used the ARCvault 24, I had no problem writing the binary data there. But when I got to the ARCvault 12, that's where I started to encounter the scsi parity error problem. I'm using the same connector for both ARCvaults. What else would cause the problem in the ARCvault 12 if taring binary data to the ARCvault 24 has no problem?
Last edited by Berris.Oliver; 02-05-2009 at 09:38 PM.
|
|
|
02-23-2009, 04:54 AM
|
#7
|
LQ Newbie
Registered: Feb 2009
Posts: 16
Original Poster
Rep:
|
OK, I found out weeks ago what the SCSI Parity Error meant. It is a hardware error and it happens to be the SCSI Card installed. I just changed it to a better one and works properly. So the lesson here is to also check the hardware specification of anything you place on your PC. 
|
|
|
All times are GMT -5. The time now is 09:36 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|