06-30-2008
Ah but thinking of it...
You used mediainit to initialize the media but did you use lifinit after? to create a lif volume
About dd:
dd if=/dev/dsk/cEd0s0 of=/dev/dsk/cEd1s0 bs=1024k
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a SCO Openserver 5.0.6 running Raid 5. and want to make a bootable disk but the boot image is 5MB ie unix file on root is around 5M and the size is obviously too large for a floppy diskette. Please help on how I can make any bootable device. The aim is to change the filesystem size.
... (6 Replies)
Discussion started by: sshokunbi
6 Replies
2. UNIX for Dummies Questions & Answers
Hello all,
I'm trying to recover from backup file to a new system with a new disk. I'm able to partition my new hard drive the same way as my old drive, but I'm unable to boot off of it. I have set the fdisk to toogle as a boot flag. But it does not seem to be working. Does anyone know how to... (4 Replies)
Discussion started by: larryase
4 Replies
3. HP-UX
hi,
i have a query regarding the size of the LVM header. Since the LVM header of a bootable disk is always 2912KB. The header size of a non bootable disk is not fixed. In Bootable disk after the LVM header (2912 KB=5824 sectors)the user data starts or we can say LV extents starts.
If i extend any... (0 Replies)
Discussion started by: gorayen
0 Replies
4. BSD
Hi to all,
Iam using FreeBSD 5.4. I want to write a kernel file with an option "CD9660_ROOT" in it. When i start to compile this kernel, it gives a message "unknown option CD9660_ROOT". Could anyone hellp with this as soon as possible.
Bye,
tadakamalla (3 Replies)
Discussion started by: tadakamalla
3 Replies
5. Solaris
The second disk that I'm trying to make bootable is to hold another version of Solaris (9).
I've created the partitions with format and labeled the disk - created the filesystems with newfs - created and mounted the directories.
...but I think I've missed something out like using fdisk to... (16 Replies)
Discussion started by: pondlife
16 Replies
6. Filesystems, Disks and Memory
In our HP/Unix system, our master scsi drive was bootable and our mirrored drive was non-bootable. Are any of these alternatives possible:
1) Make the non-bootable scsi drive bootable? How?
2) Create a bootable scsi drive, then copy the mirrored data to the newly created scsi drive?
I seek... (1 Reply)
Discussion started by: bfisk
1 Replies
7. Red Hat
I am currently trying to create a bootable USB key that I can use to boot a couple different X86 single slot processors. Creating a basic key is as easy as can be but I am looking to customize this boot image to meet two important criteria:
1. The system must boot in text only mode as my only... (4 Replies)
Discussion started by: kingfish1760
4 Replies
8. Linux
Hi all,
thanks for so many helps in many problems!
Can anyone guide, how to create a bootable cd/dvd from downloaded iso images of CentOS 5? I have collected all the iso in a dvd but it is not booting the system. Any response will be appreciable... (2 Replies)
Discussion started by: naw_deepak
2 Replies
9. Red Hat
Hi everyone,
I have a custom kickstart file from a software vendor and I'm trying to package that with a RHEL 6.5 and then attach it to a VM and install RHEL with the settings in the kickstarter file. I'm doing this from a windows PC using an app called InfraRecorder.
I've extracted the... (0 Replies)
Discussion started by: 911Eric
0 Replies
LEARN ABOUT HPUX
vxsplitlines
vxsplitlines(1M) vxsplitlines(1M)
NAME
vxsplitlines - show disks with conflicting configuration copies in a cluster
SYNOPSIS
vxsplitlines [-g diskgroup] [-c daname]
DESCRIPTION
If you import portions of a disk group on different systems, this can lead to conflicting configuration copies on the disks of the disk
group.
If the configuration information in a disk group is ambiguous, it may not be possible for Veritas Volume Manager to determine which config-
uration copy is most up-to-date. (This is usually termed a serial split brain (SSB) condition when it occurs in a cluster.) You cannot
import a disk group in this state unless you specify which disk's configuration copy to use.
You can use the vxsplitlines command to see which disks in a disk group have conflicting configuration copies, and use this information
together with your knowledge of the history of the disk groups' usage to determine which configuration copy is most valid.
The output from vxsplitlines displays the vxdg commands that you can run to import the disk group using the available configuration copies.
The -o selectcp option of the vxdg import command is used to select the configuration copy to use for the import.
OPTIONS
-c daname Display the SSB IDs for each disk that are stored in the configuration copy on the disk specified by its disk access name.
Note: Although the SSB IDs for some disks may match, this does not necessarily mean that those disks' configuration copies have
recorded all the configuration changes. When viewed from some other configuration copies, the SSB IDs of the same disks may not
match.
-g diskgroup
Specifies the disk group. If a disk group is not specified, the default disk group is used as determined from the rules on the
vxdg(1M) manual page.
EXAMPLES
Display the disks on each side of the split in the disk group newdg:
vxsplitlines -g newdg
Display the SSB IDs stored in the configuration copy on disk c2t4d0:
vxsplitlines -g newdg -c c2t4d0
NOTES
The vxsplitlines is primarily intended to be used with private disk groups, but it also works with shared disk groups.
The version number of the disk group must be 110 or greater.
SEE ALSO
vxdg(1M)
Veritas Volume Manager Administrator's Guide
VxVM 5.0.31.1 24 Mar 2008 vxsplitlines(1M)