06-06-2006
10 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. UNIX for Dummies Questions & Answers
I am new to UNIX and need help in cloning a HPUX 10.2 Ace 5, can anybody please guide me in making a full system backup.
Real Chess (0 Replies)
Discussion started by: real-chess
0 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. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 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. HP-UX
First of all, forgive me if I come off as naive. Normally I'm doing day-to-day management of a Server 2008 network, so HP-UX isn't exactly my forte.
We have several HP 715/100 machines running UX 9.x, and recently one of them stopped being able to boot. In the boot menu the disk shows up with... (3 Replies)
Discussion started by: GoldnPantaloons
3 Replies
8. Ubuntu
I am using 'dd' to clone an entire hard drive which only has Ubuntu 11.10 and some data with no special options. The disks are both 1Tb, However, I did re-partition the target disk with gparted successfully. The new partions are not the same size as the source disk. When starting 'dd' no partitions... (24 Replies)
Discussion started by: Royalist
24 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
10. HP-UX
This has got to be the system from hell. Once again, on the RP4440 (after the supplier replaced the entire box due to the bad RTC battery), finally have it all reloaded with the packages the developers need. The last thing is to add the secondary disk to the OS.
BCH sees both OS and secondary... (2 Replies)
Discussion started by: mrmurdock
2 Replies
LEARN ABOUT HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)
NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)