02-06-2006
SCO 5.0.5 Tape Drive errors
hi guys,
I.m trying to remove and add a new tape drive by using the mkdev tape command and when i try to update the Kernel this is what i'm getting,
i386ld: Symbol Sdsk_no_tag in /var/opt/K/SCO/link/1.1.1Eb/etc/conf/pack.d/blad/s
pace.o is multiply defined. First defined in /var/opt/K/SCO/link/1.1.1Eb/etc/con
f/pack.d/alad/space.o
i386ld: Symbol Sdsk_no_sg in /var/opt/K/SCO/link/1.1.1Eb/etc/conf/pack.d/blad/sp
ace.o is multiply defined. First defined in /var/opt/K/SCO/link/1.1.1Eb/etc/conf
/pack.d/alad/space.o
i386ld: Symbol Sdsk_no_tag in /var/opt/K/SCO/link/1.1.1Eb/etc/conf/pack.d/ad160/
space.o is multiply defined. First defined in /var/opt/K/SCO/link/1.1.1Eb/etc/co
nf/pack.d/blad/space.o
i386ld: Symbol Sdsk_no_sg in /var/opt/K/SCO/link/1.1.1Eb/etc/conf/pack.d/ad160/s
pace.o is multiply defined. First defined in /var/opt/K/SCO/link/1.1.1Eb/etc/con
f/pack.d/blad/space.o
ERROR: Can not link-edit unix
idbuild: idmkunix had errors.
System build failed.
Please any help i will apreciate it.
thanks a lot
Error: Kernel link failed.
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi guys
I had a system running 5.0.6 , we upgraded it to 5.0.7 everything was fine till i try to do a test backup.
The error was cannot open (cannot open /dev/xct0 no such file or directory)what i did was, removed the tape , reboot the system and the try to install it again, but its... (2 Replies)
Discussion started by: josramon
2 Replies
2. UNIX for Dummies Questions & Answers
I need to run a back up that will take more than one tape. What is the command that will continue the back up on to a second tape drive. the first is /dev/rStp0 second is /dev/rStp1. Anyone? (1 Reply)
Discussion started by: franruiz
1 Replies
3. SCO
Hi
Don't know if anyone will be able to help, but we're currently having problems with our external tape drive on our SCO server. If I try the following command for instance, "tar cvf /dev/rStp0", the tape drive jumps into action for a while, then comes back with the error "tar: cannot open:... (3 Replies)
Discussion started by: mattingg
3 Replies
4. SCO
Situation - i have an IDE hard drive from server apparently running SCO last used in 2003. No access to computer it was formerly in. I need to access the drive to pull off data files from a billing/scheduling program. I have no SCO machine or access to one atm. Have some limited Linux... (3 Replies)
Discussion started by: lordlars1
3 Replies
5. SCO
when I do a tape status /dev/rStp0 I get the following on a new tape and I have tried several:
Status : ready beginning-of-tape
soft errors : 0
hard errors: 2
underruns: 5
My BackupEdge has stopped backing up my system because it asks for a new volume yet my total system data is under 20... (5 Replies)
Discussion started by: psytropic
5 Replies
6. SCO
Hi,
Does anyone know if a HP VS160 Tape drive will work with SCO Openserver Release 5?
If so what driver would it use? alad, cha?
Thanks
John (3 Replies)
Discussion started by: jfd7000
3 Replies
7. SCO
Our tape drive died and I installed a newer Quantum DAT72 drive in it's place with the same SCSI ID. It still works, but with one major flaw, the system will lock up if I try to upgrade BackupEDGE or view NFS settings in scoadmin.
I get a Transition to ready failure on ha=0* message when the... (4 Replies)
Discussion started by: psytropic
4 Replies
8. Shell Programming and Scripting
AIX 7.1
Here's the script
#!/bin/ksh
find . -print > filelist.txt
backup -ivqf/dev/rmt0 < filelist.txt > backup.log
if ; then
echo "Backup to tape failed!" >> backup.log
else
echo "Backup to tape successfull!" >> backup.log
fi
mail -v -s "Backup report" maillist < backup.log
... (4 Replies)
Discussion started by: landog
4 Replies
link(1) General Commands Manual link(1)
NAME
link, unlink - Creates an additional directory entry for an existing file
SYNOPSIS
link file1 file2
unlink file
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
link: XCU5.0
unlink: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
DESCRIPTION
The link command performs the link() system call to create an additional directory entry for an existing file, file1. In effect, the
underlying file then has two names, file1 and file2 (either of these arguments can be a pathname). The old and new entries share equal
access rights to the underlying file.
The unlink command performs the unlink() system call to remove a link to file created by link. The unlink command removes the directory
entry specified by the file parameter and, if the entry is a hard link, decrements the link count of the file referenced by the link.
You should be familiar with the link() and unlink() system calls before you use these commands.
The link and unlink commands do not issue error messages when the associated system call is unsuccessful.
NOTES
The link and unlink commands cannot be used to link and unlink directories.
EXIT STATUS
The link and unlink commands both exit with the following: The link() or unlink() system call succeeded. Too few or too many arguments
specified. The link() or unlink() system call failed.
SEE ALSO
Commands: fsck(8), ln(1)
Functions: link(2), unlink(2)
link(1)