Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Having problems with reading tape in SCO 5.0.7

Status
Not open for further replies.

rcaddy

Technical User
Jul 2, 2003
6
US
I have installed SCO 5.0.7 on a Pentium 4-2.4GHZ with 1GB mem, Raid 5 Adaptec 2100S controller with 4-18GB hard drives, Adaptec 2940AU controller for the tape drive, Dell OEM (Seagate STD224000N) tape drive. When I read a tape using (tar -tv8) it will get part of the way through the read and fail. After trying this several times the failure is at different places on the tape. The tape has been verified good on another machine and tape drive. I have tried two different 2940 controllers with the same results. Has anyone had a problem with the Adaptec 2940 controllers and Pentium 4 processors? I have not ruled out that it is the tape drive that I am using. Any thoughts or suggestions would be appreciated.
 
I get partially through the file lising and the error I get is:

tar: tape read error
read: No such device or address

I can read this tape on the original system without failure. On the new system it fails at a different place every time.
 
Do you have it terminated properly?
Is it the only device on the chain?
can you do:

tape load
tape status

properly?
 
>stanhubble (MIS) Jul 2, 2003 :
>Do you have it terminated properly?
yes
>Is it the only device on the chain?
yes
>can you do:
>tape load
no response - i just go back to root prompt
>tape status
status: ready beginning-of-tape write-protected
soft errors: 0
hard errors: 0
underruns: 0

tape xstatus
status: ready beginning-of-tape write-protected
Total read error: 166
Total read error corrected: 174
Total read ECC erros: 8
Total unrecovered read error: 0
Total write errors: 0
Total write errors corrected: 0
 
Have you tried this:
Code:
tar -tvf /dev/rStp0
this will let tar find himself the blocking factor

Hope This Help
PH.
 
Yes, I have tried modifying compression, blocking factor, size of tape device, even used special devices. I have also removed the tape device and set it up as both DAT and generic SCSI. I am pretty much at a loss. I am trying a few other things to make it work. Any other suggestions are always appreciated.
 
Will it read back a tape it has written? Question related to data interchange problems. And will the other machine read a tape produced on this machine?

Ed Fair
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
 
As a followup to the previous posts let me elaborate on what has been done since these were posted. The system is a Pentium 4 2.0Ghz w/ Adaptec 2100S Raid controller, 1GB memory, Archive Python 4106 12/24GB DAT tape drive, and 4-18GB hard drives. For the tape drive we have tried four SCSI controllers: Adaptec's AHA-2940AU & AHA-2940U, Symbios 53C8XX, and Tekram's DC-3051E PCI SCSI controllers. I have been able to install SCO Openserver 5.0.7 and 5.0.6 on the system. It is currently configured with 5.0.6. For the Symbios and Tekram controllers, once I install the drivers and the tape drive, Lone Tar will fail a read and the tar command will return a blocksize = 0. The Adaptec controllers will partially read the tape and will fail at various places on the tape giving me the following error:

tar: tape read error
read: No such device or address

I have taken the tape drive to the system this one is replacing (AMD K3) and it reads the tape fine on an Adaptec 2940 Ultra/Ultra Wide. I have checked the scsi block size and they are 512 in both systems. Also the archive 8 matches in both systems. It is terminated properly and it is the only device on the chain. It will allow me to read a DDS-1 tape that it has written.

My plan was to set up the system remotely, restore the backup using the Lone Tar software, upgrade the O/S from 5.0.5 to 5.0.7 and setup any new hardware in the system and remove all the old hardware and drivers. It appears that with these problems my only solution is to connect the system to the network and move data across to the new system after all the programs are reinstalled. Could this problem be resolved by replacing the controllers with something new? Does anyone have any suggestions for a controller to replace these with, so that I can get this system finished?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top