07-27-2012
Thanks for your opinion. The 'dd' results were returned although I didn't record the number of bytes copied, but it was vast. Today I have re-read 'usr1 kill recommendation and have made a definite note to use it next time. Thanks again. However, the process was clearly marked as 'sleeping' and I took that to mean that it was complete.
By the way - this not a GNU version so far as I can tell. It is
Ubuntu 11.10.
'man dd_rescue' produces 'no manual entry'.
I really am very grateful for the trouble that you have taken. Roy
Last edited by methyl; 08-03-2012 at 09:39 PM..
9 More Discussions You Might Find Interesting
1. SCO
Hello everybody,
:confused:
I have to change the system disk on an old PC running SCO 5.0.5.
The disk is up and running, this is a preventive action.
My experience on UNIX is very limited and I look for the easyest solution to clone this unit.
Is it possible with commands or through a clone... (2 Replies)
Discussion started by: mhachez
2 Replies
2. HP-UX
hello,
Anybody that has already running script or command that can disk clone the hpux machine
thanks (2 Replies)
Discussion started by: eykyn17
2 Replies
3. Solaris
I am using ufsdump and ufsrestore to clone the root disk on one of my servers. I would like to automate this as much as possible, but have run into a problem where it prompts for changing the owner/mode when it is complete.
Any ideas for running this in the background and not being prompted?
... (4 Replies)
Discussion started by: patricko0317
4 Replies
4. Red Hat
I wish to clone a RedHat EL5 server. What's the easiest way to do this?
Thanks :) (4 Replies)
Discussion started by: wazzu62
4 Replies
5. Solaris
Hello guys!
I use the Solaris 10 x86 machine.
I need to clone the boot disk.
Why, when I copy slice 1 - there is a following:
# ufsdump 0f - /dev/rdsk/c0d0s1 | (cd /mnt && ufsrestore rf - )
DUMP: Warning - super-block on device `/dev/rdsk/c0d01` is corrupt - run fsck
Dump: The Entire... (6 Replies)
Discussion started by: wolfgang
6 Replies
6. Filesystems, Disks and Memory
Hi,
I'm running Ubuntu on my laptop. To keep my data safe and easy disaster recovery as well I bought similar HDD to one installed in my laptop with higher capacity and using USB box I'm doing disk clone to it. So at any time I can replace disk and carry on with my work as before.
I'm trying... (2 Replies)
Discussion started by: uvaio
2 Replies
7. Shell Programming and Scripting
Hi,
Is there disadvantages if we do AIX Serevr cloning to the new AIX server.
Thanks in advance (0 Replies)
Discussion started by: kmsekhar
0 Replies
8. HP-UX
Hello Friends,
Am in requirement to clone a Live HP-UX server here's details
OS: HpUX B-11.11 with mirrored LVM disks .
S/ws: Remedy, XML engine, Annoysystem, Oracle
All Oracle, XMl and Remedy data is on SAM LUN which is used for clustering .
My requirement to create a clone server and... (10 Replies)
Discussion started by: Shirishlnx
10 Replies
9. Linux
Dear All
I needed to clone my disk to another hard drive . I did it as the following :
#dd if=/dev/sdb of=/dev/sdc
But after a while, the procedure ended with the "writing to /dev/sdc
input/output error" message.
Can you please let me know how can I overcome this as the fdisk now returns as "... (1 Reply)
Discussion started by: hadimotamedi
1 Replies
mtx(8) System Manager's Manual mtx(8)
Name
mtx - generic magtape exerciser
Syntax
/usr/field/mtx [ options ] -adev
/usr/field/mtx [ options ] -sdev
/usr/field/mtx [ options ] -ldev
/usr/field/mtx [ options ] -vdev
Description
The exerciser will write, read, and validate random data on the specified magnetic tape device from beginning of tape (BOT) to end of tape
(EOT). There are four record length modes in which to run the exerciser. The modes are short (512 bytes), long (10240 bytes), variable
(512-20480 bytes), and all of these three in sequence.
The exerciser will run until or a kill -15 pid is sent to the process.
A logfile is made in for you to examine and then remove. If there are errors in the logfile, check the file, where the driver and kernel
error messages are saved.
An enhanced tape exerciser called provides more comprehensive tape testing than this exerciser. Refer to for a complete description.
Options
The mtx options are:
-h Print help message for the command.
-ofile Save diagnostic output in file.
-ti Run time in minutes (i). The default is to run until the process receives a or kill -15 pid.
-rj Record length for long-record test. May range from 1 - 20480; the default is 10240 bytes.
-fk Size of file in records. The default is -1, go to end-of-tape.
Arguments
You must specify one of the following function flags and its argument to the exerciser.
-adev Perform short, long, and variable-length record tests on the dev, a raw device name and unit number. For example, -armt0h.
-sdev Perform short (512-byte) record length test. The dev argument is a raw device name and unit number. For example, -srmt0h.
-ldev Perform long (10240-byte) record length test. The dev argument is a raw device name and unit number. For example -lrmt0h.
-vdev Perform variable record length test (records vary from 512 bytes to 20480 bytes). The dev argument is a raw device name and unit
number. For example, -vrmt0h.
Restrictions
If there is a need to run a system exerciser over an NFS link or on a diskless system there are some restrictions. For exercisers that
need to write into a file system, such as the target file system must be writable by root. Also the directory, in which any of the exer-
cisers are executed, must be writable by root because temporary files are written into the current directory. These latter restrictions
are sometimes difficult to overcome because often NFS file systems are mounted in a way that prevents root from writing into them. Some of
the restrictions may be overcome by copying the exerciser to another directory and then executing it.
The following restrictions apply to the SCSI tape drives. The Magnetic Tape Exerciser (MTX) runs the tape in start/stop mode; that is, the
tape does not stream. Therefore, MTX should not run for extended periods of time (two hours maximum run time). In addition, MTX does not
handle the end of tape properly.
Examples
This example runs short, long, and variable-length tests on rmt0h until the process receives a or kill -15 pid:
% /usr/field/mtx -armt0h
The following example runs a long-record length test on rmt0h for 240 minutes in the background:
% /usr/field/mtx -lrmt0h -t240 &
See Also
tapex(8)
Guide to System Exercisers
mtx(8)