06-11-2008
SCO newbie here also:
I am receiving the message:
cpio: cannot open </dev/rStp0> for input
Should the tape be mounted using a mount command first?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi. I have been having problems with restoring from a tape backup. I use the following cpio command:
find / -print | cpio -ouvB > /dev/rStp0
After running this cpio command, the screen will display all files, but when I try to read or restore the tape I get the following error:
Tape input... (1 Reply)
Discussion started by: cstovall
1 Replies
2. Filesystems, Disks and Memory
I have been restoring from tape some old data. I have done quite a few tapes and have had no problems until now.
The command I am running is "dd if=/dev/rmt/1hbn bs=1024 | tar -pBxF - ".
This is the second tape have have come up with the error "Not enough space". This tape has a couple of... (1 Reply)
Discussion started by: mtoombs
1 Replies
3. HP-UX
I am trying to do a restore on a backup tape (DDS2) and am having a little trouble. For one, I dont know how the tape was made, whether is was tar, cpio, dump..etc. Anyone know how to restore a tape without knowing the format of the backup? (5 Replies)
Discussion started by: bake255
5 Replies
4. AIX
Hello everyone
I have a tape with some information that I got
to restore, the tape was made with the fbackup
command in a hp box.
My question is that I have to restore in a Ibm
box, how can I do this ?
Thanks in advance (1 Reply)
Discussion started by: lo-lp-kl
1 Replies
5. SCO
Here is the scenario. We have an billing system that ran on SCO 5.0.6. The HP Netserver went dwon, along with SCSI disks. They are unretrievable. I installed an IDE HDD, and reinstalled SCO. I am not too familiar w/ SCO or UNIX, and need to know how to install Tape drive, and how to restore from... (11 Replies)
Discussion started by: jlewis808
11 Replies
6. Solaris
I have a T2000 server that is JumpStarted with Solaris 10 from the JumpStart server. Host name and IP address is changed after that. Then we backup the server using FLAR to tape:
root.damas# date; flarcreate -c -t -n "Sol10_cairo_image" -a "engineering@starsolutions.com" -R / /dev/rmt/0n ;... (2 Replies)
Discussion started by: StarSol
2 Replies
7. SCO
Looking for specifically naming convention for a tape device for SCO Unix
What full system backup command should I use for SCO UNIX (1 Reply)
Discussion started by: jedimaster
1 Replies
8. Solaris
Hope someone can help me here...
I've got to restore an E450 with 300MHz cpus which was running Solaris 2.6 from tape. Regrettably the boot drive has failed.
I've access to the first release of Solaris 2.6 CD's and to a set of Solaris 9 CD's.
I remember that different E450 CPUs needed different... (1 Reply)
Discussion started by: pamplemousse
1 Replies
9. SCO
Hello folks. I have the following problem:
I'm trying to create a tape backup of a list of files on a 10 year old server, running SCO Openserver 5.0.5 (the tape drive is a Seagate STD224000N, connected as a SCSI drive).
I then want to restore the contents of this tape onto a new server... (6 Replies)
Discussion started by: klabelkholosh
6 Replies
10. Emergency UNIX and Linux Support
Hi
I recently deleted my /etc but I had a backup on tape. I was able to boot the server with a cd-rom and mounted the /c1t0d0s0 which is where the root directory resides. However when I tried to restore the backup with tar xvf /dev/rmt/0n I wasn't successful even though I was able to use the tar... (2 Replies)
Discussion started by: rahmantanko
2 Replies
LEARN ABOUT ULTRIX
umount
mount(8) System Manager's Manual mount(8)
Name
mount, umount - mount or unmount file systems
Syntax
/etc/mount [ options ] [ device ] [ directory ]
/etc/umount [ options ] [ device ] [ directory ]
Description
This is a general description of the command. Additional descriptions are provided to define the syntax and options for the NFS and UFS
file systems.
Each invocation of the command announces to the system that a file system is present on the device device. The file system may be local or
remote. File directory must exist as a directory file. It becomes the name of the newly mounted file system root.
If invoked without arguments, prints the list of mounted file systems.
Physically write-protected disks and magnetic tape file systems must be mounted read-only or an error will occur at mount time.
General users can only mount file systems with certain restrictions. For example, the user, other than the superuser, performing the mount
must own the directory directory. Furthermore, no users other than the superuser can execute or programs on the mounted file systems. In
addition, users other than the superuser cannot access block or special character devices such as on the mounted file systems.
The command announces to the system that the removable file system previously mounted on the specified directory is to be removed. Only
the person who mounted a particular file system or the superuser can unmount the file system again.
Options
-a Reads the file and mounts, or unmounts, all file systems listed there.
-f Fast unmount. The option has no meaning for local file systems and directories. However, for remote file system types (such
as NFS), the option causes the client to unmount the remotely mounted file systems and directories without notifying the
server. This can avoid the delay of waiting for acknowledgment from a server that is down.
-o options Specifies a string that is passed to the kernel and used by the specific file system's mount routine in the kernel. For spe-
cific options, refer to the file system-specific description, such as
-r Indicates that the file system is to be mounted read only. To share a disk, each host must mount the file system with the -r
option.
-t type Specifies the type of file system is being mounted. When used with the option, the option mounts all file systems of the given
type found in the file. For specific file system types, refer to the file system-specific description, such as
-v Tells what did or did not happen. (Verbose flag)
The options for are:
-a Unmounts all mounted file systems. It may be necessary to execute twice to accomplish unmounting of all mounted file systems.
-v Tells what did or did not happen. (Verbose flag)
Restrictions
Mounting corrupted file systems will crash the system.
Files
File systems information table
See Also
getmnt(2), mount(2), fstab(5), fsck(8), mount(8nfs), mount(8ufs)
mount(8)