Sponsored Content
Full Discussion: Ignite
Operating Systems HP-UX Ignite Post 302983670 by vbe on Friday 14th of October 2016 03:48:05 PM
Old 10-14-2016
Either your D class had the FWSCSI controller option giving you hot swap disks but only 2 disk internal allowed or you had standard on hot swap but could have up to 5 disks in it... Trying to find Ignite-UX to reinstall WILL NOT solve you issue as so far I see no proof Ignite isnt working but as I said above you have a system issue, I have been helping CERN to maintain the running D classes they had so I know what kind of message you get when things go wrong, you dont want to answer what you have been asked, I think its time to close the thread so others dont loose their time too
 

10 More Discussions You Might Find Interesting

1. HP-UX

ignite tapes

can any1 tell me how to make ignite tapes for the HP-ux. this company said it was: "make_tape_recovery_A", but that don't work. (4 Replies)
Discussion started by: JBX
4 Replies

2. UNIX for Advanced & Expert Users

without an ignite server ??

system: HP-UX 10.20 with HFS mounted. How can I convert the HFS to VxFS without an ignite server ? Is this possible ? thanks simon2000 (4 Replies)
Discussion started by: simon2000
4 Replies

3. HP-UX

make_sys_image + Ignite problem

could any one help me I have a HP UX 11.0 with a lot of VG and disks connected to SAN. I need to create a Golden Image having only the vg00 of this system. How do i do this using make_sys_image? In case any have some docs, I would appreciate if You could share it. Thanks Dhanish (5 Replies)
Discussion started by: i2admin
5 Replies

4. HP-UX

HP-UX Ignite server

Sorry if this has been asked and answered, but I can't find this particual problem. I've had an Ignite server running for years on a small internal network with images we load on daily basis. Tried to load two servers, L2000 and C3600 , both with same problem. # boot lan.192.168.2.2 install ... (0 Replies)
Discussion started by: ddeblance
0 Replies

5. HP-UX

Need Ignite for HP-UX 10.20

Hello All, I need to bring down our old 9000 series d350, but my supervisor wants an ignite backup created. I cannot find ignite in the usual places (/opt/ignite) nor can I find it in swlist. As far as I can tell the cd's are long gone. Is there anywhere else I could look for ignite being... (6 Replies)
Discussion started by: stay0ut
6 Replies

6. HP-UX

vpar ignite

Hi Can I use a vpar as an ignite server? (1 Reply)
Discussion started by: mahlathini
1 Replies

7. AIX

ignite equivalent in AIX

Hi All, Does AIX has utility like ignite server to make remote os installation using image (2 Replies)
Discussion started by: jayannair
2 Replies

8. HP-UX

Ignite and HP-UX 09.XX

I am looking to make bootable tape backups of four machines running HP-UX 09.02, 09.05 and 09.07. I successfully located Ignite 10.20 and installed it and made a backup on the one machine running HP-UX 10.20. I am having trouble locating information about Ignite for HP-UX 9. Does it exist? Is... (3 Replies)
Discussion started by: whack_job
3 Replies

9. HP-UX

Ignite - make_net_recovery

I've read the Ignite User/Admin Guide but I'm having trouble figuring out if I can do a make_net_recovery if the ignite server and client server are on completely different networks? If this can be done is there any special configuration? If I initiate the command from the server it looks like it... (3 Replies)
Discussion started by: gonzotonka
3 Replies

10. HP-UX

Error with ignite

Works all. Depot shared via nfs dhcp working setting file system,network,root password,etc But when i start "go!" with installation,give me this error. How to fix,debug? Thanks http://s24.postimg.org/5hzbgk551/unixbell3.png (3 Replies)
Discussion started by: Linusolaradm1
3 Replies
voldiskadd(8)						      System Manager's Manual						     voldiskadd(8)

NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager SYNOPSIS
/usr/sbin/voldiskadd disk-address-list DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility. One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp (for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names in the /dev/disk directory. For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified, that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the disk group. If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated. Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage Manager. For new disks, all space on the disk becomes free space in the disk's disk group. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions. Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group. This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot spare device. Creating new disk groups in which to import new disks. If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist- ing contents. This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a disk label. Encapsulation is performed by calling volencap. Reconnecting a drive that was temporarily inaccessible. This situation is detected automatically, by noting that the specified drive has a disk ID that matches a disk media record with no currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes referring the disk are restarted. This reattach action is performed by calling the volrecover script. ERRORS
You may receive the following messages when using the voldiskadd command: Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open. This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device. special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data. Would you like to continue?? [y,n,q,?] (default: n) This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints this message to warn that a disk partition may have valid data which could be destroyed. If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM. FILES
A list of disks to exclude from use by voldiskadd. SEE ALSO
disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8) voldiskadd(8)
All times are GMT -4. The time now is 04:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy