10 More Discussions You Might Find Interesting
1. AIX
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (3 Replies)
Discussion started by: terrya
3 Replies
2. Filesystems, Disks and Memory
Hello,
On 4/20/2018, we performed a disk replacement on our IBM 8202 P7 server. After the disk was rebuilt, the SAS Disk Array sissas0 showed a status of degraded. However, the pdisks in the array all show a status of active.
We did see a message in errpt. DISK ARRAY PROTECTION SUSPENDED.
... (1 Reply)
Discussion started by: terrya
1 Replies
3. AIX
Hi,
One of my disk is in 'disk missing state'. It is a sharedVG and cluster nodes.
The errpt keeps reporting stale partition error.
lvs are in open/stale state.
In this sceanario is replacing the disk the best practice?
When i do a lsdev the disk is labelled as below.
hdisk3 Available ... (2 Replies)
Discussion started by: ElizabethPJ
2 Replies
4. HP-UX
Hello,
I'm new to this forum and as you will see from my question I'm new to UNIX as well.
One of our costumers has HP rx4640 running on UNIX with two 300GB hot-swappable disks that are mirrored. They reported to us that one of the disks is faulty and they want us to take care of it. Below is... (16 Replies)
Discussion started by: gjk
16 Replies
5. Solaris
Hello,
I have a Sparc system with encapsulated disks.
Because of disk errors I had to replace rootdisk,
I did it with
vxdiskadm 4)
replacement, vxdctl disable/enable,
vxdiskadm 5)
After it it the system boot failed, dropped back to the ok> prompt, message was:
The file... (0 Replies)
Discussion started by: ggi
0 Replies
6. Linux
Hi all,
I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies
7. Shell Programming and Scripting
Hello,
I have the following perl array:
@longname = (Fasthernet0/0 Fasthernet0/1 Serial0/1/0 Serial0/2/1 Tunnel55 Tunnel77)
with the followinh array:
@shortname = (Fa0/0 Fa0/1 Se0/1/0 Se0/2/1 Tu55 Tu77)
in other words, I need to remove the following from each element in the array... (4 Replies)
Discussion started by: ahmed_zaher
4 Replies
8. Solaris
Hello,
Can someone advise the proper procedure for replacing a mirrored disk in SVM. I have checked the docs and various websites but the procedure seems to vary. This is what I would do...
1. Remove the db replicas from the bad disk.
2. Detach it from the mirror
3. Clear it with... (4 Replies)
Discussion started by: Actuator
4 Replies
9. Red Hat
Hi all,
I need some help with a RHEL 4 on a Sun Fire v65x machine.
Some of the disks is damaged or has a hardware issue. This disk is connected to a hardware raid.
The problem is that I don't know what is the brand, model and capacity of the disk.
I've read the raid manual, but says... (3 Replies)
Discussion started by: adelgadom
3 Replies
10. Solaris
I dont even know what raid level this is, but its raid 5 mirrored from the looks of it.
I have a failed disk (t12) within this mirror. What is the best way to replace this disk? 2 things concern me, isn't there a command to prepare the disk for a hot swap? and what should i do with the... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
voldiskadm(8) System Manager's Manual voldiskadm(8)
NAME
voldiskadm - Menu interface for LSM disk administration
SYNOPSIS
/usr/sbin/voldiskadm
DESCRIPTION
The voldiskadm script is an interactive tool that presents a menu of possible operations to the user. When an operation is selected, the
script guides the user through the necessary steps, and prompts for data needed to complete the operation.
The voldiskadm interface is intended mainly for beginning users and for those who prefer a simple method for doing common operations. The
interface uses query-based prompts to gather input, with defaults supplied when possible. 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.
For operations that require a device name, one or more names can be specified using a space-separated list. Names in the list can have the
form dskn or rdskn (for an entire disk) or dsknp or rdsknp (for a specific disk partition). Disk names relate directly to device names in
the /dev/disk and /dev/rdisk directories.
The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadm. Each line of the file specifies the name of a disk
to exclude (for example, dsk5).
The voldiskadm menu includes the following options: Add or initialize one or more disks
This option prompts for one or more disk device addresses. The specified disks can be added to an existing disk group, added to a
new disk group, added to a disk group as spares, or initialized but not added to a disk group (reserved for use as replacement
disks).
After specifying the disks, the user is prompted for a disk group (rootdg by default) and a disk name. If no name is specified, a
default disk name is assigned (diskn for disks in the rootdg disk group and diskgroupn for disks in other disk groups).
The disks are then checked to ensure that there is no information already on them. If there is, the user is given the option of
encapsulating the disks. Encapsulate one or more disks
This option prompts for one or more disk addresses. It then calls volencap to encapsulate the specified partitions. Remove a disk
This option prompts for a disk, by disk media name. The disk is checked to ensure that no subdisks reside on the disk. If the disk
is in use, the operation fails with a recommendation to first move all volumes off the disk. If this disk is the last disk in a
disk group, the user is prompted for whether the disk group should be removed from the system, as well.
The operation proceeds by calling voldg rmdisk to remove the disk from its disk group. If this is the last disk in its disk group,
voldg deport is used, instead, to remove the disk group from use. Remove a disk for replacement
This option prompts for a disk, by disk media name. The disk is checked for volumes that would lose all mirrors as a result of the
operation. If such volumes exist, they are listed and the user is prompted to ensure that the operation should proceed.
The operation proceeds by calling voldg -k rmdisk to dissociate the media record from the physical disk. If some formatted disks
are under LSM control but not assigned to a disk group, the user is prompted for whether one of these disks should be used as a
replacement. Replace a failed or removed disk
This option prompts for a disk media name. The named media record must be dissociated from a disk. If the media record is not in
the removed state, unused disks are scanned for matching disk IDs. If a disk with a matching disk ID is found, the user is prompted
for whether that disk should be reattached.
If a matching disk is not used, the user is prompted for a new disk, by device name. If the named replacement disk has a valid disk
header, but is not allocated to a disk group, the user is prompted for whether the disk should be reinitialized. If the named
replacement disk is listed as allocated to a disk group or to another host, the user is prompted to ensure that the operation should
proceed.
If the device is to be initialized, a new disk label is written to the disk to reflect its private and public regions.
Given an initialized disk, the operation proceeds by replacing the disk in a disk group with voldg -k adddisk. Mirror volumes on a
disk
This option prompts for a disk, by disk media name. It then prompts for a destination disk within the same disk group, also by disk
media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volmirror to
mirror the volumes.
Mirroring volumes from the boot disk will produce a disk that can be used as an alternate boot disk. This is done by calling the
volrootmir command. Move volumes from a disk
This option prompts for a disk, by disk media name. It then prompts for a possible list of destination disks, also by disk media
name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volevac to move sub-
disks off the disk. Enable access to (import) a disk group
This option prompts for a disk, by device address. The operation proceeds by calling voldg import to import the disk group stored
on that disk. Disable access to (deport) a disk group
This option prompts for a disk group name. The prompt display lists alternate disk groups and the disks (media name and access
name) that they contain. The operation proceeds by calling voldg deport. Enable (online) a disk device
This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func-
tions for disks currently in an offline state. It then proceeds to make the disk accessible. Disable (offline) a disk device
This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func-
tions for disks currently in an online state but not part of any disk group. It then proceeds to mark the disk as offline such that
the Logical Storage Manager makes no further attempt at accessing the disk. Mark a disk as a spare for a disk group
This option sets up a disk to be used as a spare device for its disk group. A spare disk can be used to automatically replace a disk
that has failed. No space can be used on a disk that is marked as a spare. Turn off the spare flag for a disk
This option removes a disk from those that can be used as a spare and returns its space to the general pool of available space.
Recover plexes and volumes after replacement
This operation performs plex attachment, RAID-5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes
residing on the named disks (media name). If no media name or volume operands are specified, the operation applies to all volumes
(or to all volumes in the specified disk group).
ERRORS
See the voldiskadd(8) reference page for a description of errors related to the initialization operation.
FILES
A list of disks to exclude from use by voldiskadm.
SEE ALSO
disklabel(8), volintro(8), voldg(8), voldisk(8), voldiskadd(8), voldisksetup(8), volrootmir(8)
voldiskadm(8)