LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 02-11-2008, 12:02 PM   #1
sjpiv44
Member
 
Registered: Jan 2008
Location: Little Rock
Distribution: SUSE 10.3
Posts: 38

Rep: Reputation: 15
Question Having a problem with DAT /dev/st0 SCO/SUSI


Using a DAT tap drive, I did a, tar cvf /dev/st0 filename.tar /filepro/*, to pick up the data from the SCO system. I can do a tar tvf /dev/st0 and see the data.

When I move the tapedeck to the SUSE system, it seemed to see it as we booted up. When I tar tvf /dev/st0, the light on the tape drive indicates it is being accessed but It gives me a read error. If you need more info, I will be to site and replicate.

I the device st0 have parameters that can be set or changesed?

This worked at one time. We can figure out, one, why the SCO dev /rct0, which worked using the filePro backup to rct0. Now the SCO system is seeing the DAT as st0.

On the SUSE system, we get the following:
tar: Can not read input/output error
tar: at the begining fo tape, quitting now
tar: error is not recoverable.

Need some help ! ! !

Thanks in advance for your help.

Jack Privitt, IT
Up & Running Arkansas

Last edited by sjpiv44; 02-12-2008 at 03:41 AM. Reason: Try to clarify my DAT I/O Error problem.
 
Old 02-21-2008, 04:45 AM   #2
ravibhure
Member
 
Registered: May 2007
Posts: 75

Rep: Reputation: 15
Hello sjpiv44,
It's to complicated & such hard situation to find out and recover your Input/Output error, but there are some command that getting you some results.
first off all you have to go using following steps

$ mt -f /dev/st0 status
$ mt -f /dev/st0 setblk 0
$ tar tvf /dev/st0
Now you will see table of content of your data. setting your block size to zero.
 
Old 04-08-2008, 05:31 PM   #3
sjpiv44
Member
 
Registered: Jan 2008
Location: Little Rock
Distribution: SUSE 10.3
Posts: 38

Original Poster
Rep: Reputation: 15
Below is a show if each command.

Below is a copy if the results of, 1st, status and the view of tape inventory.
After the first of 1st of 4 tapes, the flowwing is the only difference I saw. BOT ONLINE IM_REP_EN when I did a status. All the tapes displayed the same on status.
Jack


FORDONE:~ # mt -f /dev/st0 status
drive type = Generic SCSI-2 tape
drive status = 318767104
sense key error = 0
residue count = 0
file number = 0
block number = 0
Tape block size 0 bytes. Density code 0x13 (DDS (61000 bpi)).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN

FORDONE:~ # 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
 
Old 04-09-2008, 01:59 AM   #4
ravibhure
Member
 
Registered: May 2007
Posts: 75

Rep: Reputation: 15
Hi sjpiv44,
To late to check reply,
when you put the
$ mt -f /dev/st0 status
It shows the block on which it has.
that time put command
$ mt -f /dev/st0 fsf
and again try
$ tar tvf /dev/st0
 
Old 04-09-2008, 02:15 AM   #5
blacky_5251
Member
 
Registered: Oct 2004
Location: Adelaide Hills, South Australia
Distribution: RHEL 4&5, Fedora 10, CentOS 5.4, IPCop
Posts: 569

Rep: Reputation: 55
Try adding '--blocking-factor=128' to the tar command on the SUSE system.

Older *NIX systems often use blocking factors that don't correspond well with Linux. We often strike this problem with tapes created on AIX and DG-UX systems.
 
Old 04-11-2008, 06:30 PM   #6
sjpiv44
Member
 
Registered: Jan 2008
Location: Little Rock
Distribution: SUSE 10.3
Posts: 38

Original Poster
Rep: Reputation: 15
I am having a problem addressing the 'Blocking-factor=128' The man tar states
-b, --blocking-factor=BLOCKS BLOCKS x 512 bytes per record

I need to understand what we are saying, referring to 'Blocking-Factor'. For some reason when our old HP, C1533 DAT died, the 'HP replacement was not, possiblely, fully compatable with the HP C1599A. I am starting to question.

When we had the HP C1533, I was successful in getting a copy of the files that I needed. I am having a learning experance.
 
  


Reply

Tags
can, dat, error, input, output, read


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Rescue Disk w/ /dev/st0 kromberg Linux - General 3 07-16-2007 01:48 PM
difference between /dev/st0 and /dev/nst0 mayankh Linux - Hardware 1 10-19-2006 04:42 AM
quicker than mt -f /dev/st0 erase? mattl Linux - Hardware 3 05-20-2006 11:38 AM
various /dev/(n)st0? devices coreyw Linux - Hardware 1 11-03-2003 06:53 PM
alias /dev/st0? utabintarbo Linux - Newbie 1 04-19-2002 02:17 PM


All times are GMT -5. The time now is 06:58 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration