Sponsored Content
Full Discussion: IBM RAID disks
Operating Systems Linux Red Hat IBM RAID disks Post 302276848 by pdudley on Wednesday 14th of January 2009 08:17:32 PM
Old 01-14-2009
IBM RAID disks

We have a Red Hat linux server running on IBM x445 hardware. There are external disks in an IBM EXP300 disk enclosure. The system is running RAID 5. One of the four IBM disks (73.4 GB 10k FRU 06P5760) has become faulty. The system is still up and running OK because of the RAID. In that same EXP300 disk enclosure we have two other disks - exactly the same specs and FRU number - which are not used and have not been used for a while. They were connected to a system which is no longer being used and have since been disconnected from that system and are sitting in the EXP300 disk enclosure doing nothing. All of these disks are hot swappable.

What I would like to know is - can I use one of these spare disks to replace the faulty one? As they were previously used briefly on another system - if I can use them do they have to be formatted or initialised in some way before use?

Thanks
Paul
 

10 More Discussions You Might Find Interesting

1. AIX

new IBM pseries and new disks

Hello Gurus, i'm quite new person in AIX world, actually i'm SAP consultant. But due to my job faced with AIX. Trying to configure new server for installation SAP. We have 4 disks one of them (hdisk3) has VG rootvg. How i can extend rootvg with another disk? i tried: # extendvg rootvg hdisk0... (2 Replies)
Discussion started by: sapbcer
2 Replies

2. AIX

Horribly old stuff: SMS disks for IBM PC 850?

Hi. I'm trying to reinstall AIX 4.3.3 (ML9) on an IBM PC 850 PowerPC machine but I have trouble getting an SMS diskette that will let me set the CD as bootable. The SMS diskette I have is 1.26 and it either crashes or lists Hard Disk 0 some 20 + times (and nothing else) on the screen you... (2 Replies)
Discussion started by: dlundh
2 Replies

3. AIX

IBM FastT600 SAN - RAID 5 Storage Manager Client v08.33.G5.03 - Recovery?

To summarize the problem: The "IBM FastT Storage Manager Client v8" shows that our Disk Farm is arranged into 6 logical drives each in a RAID 5 configuration. This software also shows that 5 of the 6 logical drives (from Disk Farm) are in a error state: "Failed Logical Drive - Drive Failure".... (1 Reply)
Discussion started by: aix-olympics
1 Replies

4. Solaris

Move disks to different StorEdge, keeping RAID

Hi. I need to move a 5 disk RAID5 array from a SE3310 box to a different SE3310 array. After installing the disks in the "new" StorEdge device, I "would like" ;) to be able have access to the data which is on the RAID. Essentially, the quesion is, how can this be done? :confused: I checked... (5 Replies)
Discussion started by: alexs77
5 Replies

5. Solaris

Solaris not recognizing RAID 5 disks

I've just installed Sol 10 Update 9 on a Sun 4140 server and have a RAID 1 configuration (2 136 Gb drives) for the OS and have created a RAID 5 array (6 136 GB) drives. When i log into the system I am unable to see the RAID 5 disks at all. I've tried using the devfsadm command but no luck and... (9 Replies)
Discussion started by: goose25
9 Replies

6. Linux

If i don't have raid disks can i shut down dmraid device-mapper?

hello my centOS newly installed system loading dmraid modules on startup I did remove all LVM/raid things from system installation menus and after installation too but dmraid is still there and he says: no raid disks found also I did modprobe -r dm_raid45 and it do remove it but only until... (7 Replies)
Discussion started by: tip78
7 Replies

7. AIX

SCSI PCI - X RAID Controller card RAID 5 AIX Disks disappeared

Hello, I have a scsi pci x raid controller card on which I had created a disk array of 3 disks when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk ) suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies

8. Solaris

Solaris 10 Installation - Disks missing, and Raid

Hey everyone. First, let me start by saying I'm primarily focused on linux boxes, and just happened to get pulled into building two T5220's. I'm not super educated on sun boxes. Both T5220's have 8 146GB 15k SAS drives. Inside the service processor, I can run SHOW /SYS/HDD{0-7} and they all come... (2 Replies)
Discussion started by: msarro
2 Replies

9. Red Hat

RAID Configuration for IBM Serveraid-7k SCSI RAID Controller

Hello, I want to delete a RAID configuration an old server has. Since i haven't the chance to work with the specific raid controller in the past can you please help me how to perform the configuraiton? I downloaded IBM ServeRAID Support CD but i wasn't able to configure the video card so i... (0 Replies)
Discussion started by: @dagio
0 Replies

10. Solaris

Hardware RAID using three disks

Dear All , Pl find the below command , # raidctl -l Controller: 1 Volume:c1t0d0 Disk: 0.0.0 Disk: 0.1.0 Disk: 0.3.0 # raidctl -l c1t0d0 Volume Size Stripe Status Cache RAID Sub Size ... (10 Replies)
Discussion started by: jegaraman
10 Replies
vxdiskadm(1M)															     vxdiskadm(1M)

NAME
vxdiskadm - menu-driven Veritas Volume Manager disk administrator SYNOPSIS
vxdiskadm DESCRIPTION
vxdiskadm provides a menu-driven interface to perform common Veritas Volume Manager (VxVM) disk administration tasks. The vxdiskadm script is interactive and prompts you for responses, supplying defaults where appropriate. Help is available at every prompt by entering a question mark (?) to display a context-sensitive help message. To add disks, specify one or more disks with a disk-address-pattern-list. The basic format for disk addresses is c#t#d# or enclosure-based names such as enc1_0. You can specify just the controller and target to add all the disks at that SCSI address. For example, use c2t0 to specify all disks on controller two, target zero. You can specify more than one disk address or address pattern on the command line. The word all specifies all disks on the system. Disk address names relate directly to device node names in the /dev/dsk and /dev/rdsk directo- ries. You can use the files /etc/vx/disks.exclude, /etc/vx/cntrls.exclude and /etc/vx/enclr.exclude to exclude disks, controllers and enclosures from use by vxdiskadm. Each line of disks.exclude specifies a disk to exclude, for example, c0t3d0. Each line of cntrls.exclude specifies the address of a controller to exclude, for example, c2. Each line of enclr.exclude specifies an enclosure to be excluded, for example, enc1. OPERATIONS
Add or initialize one or more disks Prompts for one or more disk device addresses, and a disk group to which these are to be added. When initializing disks into a new disk group, you are prompted to choose whether this disk group should be compatible with the Cross-platform Data Sharing (CDS) feature. You are also given the alternative of initializing the disk but leaving it unallocated to a disk group. A default disk name is assigned with the format, diskgroup##, such that the names are unique within all imported disk groups. You are prompted to specify whether to designate the disks as spares for the disk group. Remove a disk 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 group, you are also prompted whether to remove the disk group from the system. The operation then calls vxdg rmdisk to remove the disk from its disk group. If this is the last disk in its disk group, vxdg deport is used instead. Remove a disk for replacement 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, those volumes are listed and you are prompted whether to continue the operation. The operation calls vxdg -k rmdisk to dissociate the media record from the physical disk. If there are formatted disks available that have disk headers but no disk group, you are prompted whether to use one of these disks as a replacement. Replace a failed or removed disk 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, you are prompted whether to reattach that disk. If a matching disk is not used, you are prompted for a new disk, by device address. If the named replacement disk has a valid disk header, but is not allocated to a disk group, you are prompted whether to reinitialize the disk. If the named replacement disk is listed as allocated to a disk group or to another host, you are prompted whether to continue the operation. If the device is initialized, vxdisksetup is called to set up public and private regions and to create the disk header. Given an initialized disk, the operation replaces the disk in a disk group with vxdg -k adddisk. Mirror volumes on a disk Prompts for a disk, by media name. It then prompts for a destination disk within the same disk group, also by media name. Spec- ifying no destination disks indicates that any disk can be the destination. The operation calls vxmirror to mirror the volumes. Move volumes from a disk Prompts for a disk, by media name. It then prompts for a possible list of destination disks, also by disk media name. Specify- ing no destination disks indicates that any disk is suitable. The operation calls vxevac to move subdisks off the disk. Enable access to (import) a disk group Prompts for a disk group name. The operation calls vxdg import to import the disk group stored on that disk. Remove access to (deport) a disk group Prompts for a disk group name. The prompt lists alternate disk groups and the disks (media name and access name) that they con- tain. The operation calls vxdg deport. Enable (online) a disk device Prompts for a disk device. The prompt lets you display the disks on the system. The operation functions only for disks cur- rently offline. It then makes the disk accessible. Disable (offline) a disk device Prompts for a disk device. The prompt lets you display the disks on the system. The operation functions only for disks cur- rently online, but not part of any disk group. It then marks the disk as offline such that VxVM no longer tries to access the disk. Mark a disk as a spare for a disk group Sets up a disk 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 Removes a disk from the list of spare disks, and returns its space to the general pool of available space. Remove (deport) and destroy a disk group Removes access to and destroys a disk group that is currently enabled (imported). A disk group may be destroyed if the disks are needed for some other purpose. Unrelocate subdisks back to a disk Moves subdisks which were hot-relocated following a disk failure back to the original disk, or to a disk with a different name, possibly with a different offset. Exclude a disk from hot-relocation use Sets up a disk to be excluded from use by hot-relocation. The disk is marked as nohotuse and it cannot be used by hot-relocation to replace a disk that has failed. However, it remains available to be used as free space for its disk group. Make a disk available for hot-relocation use Turns off the nohotuse flag on a disk. Use this option to make a disk available for hot-relocation use. This only applies to disks that were previously excluded from hot-relocation use. Prevent multipathing/Suppress devices from VxVM's view Excludes devices from VxVM's view, or prevents them from being multipathed by the dynamic multipathing (DMP) driver, vxdmp. There are three ways of specifying the devices on which these operations are to be performed: o As a controller for all devices connected through the controller. o As a physical pathname for all devices under that path. o As a combination of the Vendor ID and Product ID (VID:PID) for all devices of that type. This option also provides a method to define pathgroups in case of disks which are not multipathed by VxVM. Only one path from a pathgroup will be made visible to VxVM. This is useful to avoid duplicate entries for devices that are not multipathed by vxdmp. Allow multipathing/Unsuppress devices from VxVM's view Makes devices visible to VxVM again or makes vxdmp multipath these devices again. This can be performed only on devices that have already been specified using the "Prevent multipathing/Suppress devices from VxVM's view" option. List currently suppressed/non-multipathed devices Lists all devices suppressed from VxVM's view and all devices prevented from being multipathed by vxdmp. Change the disk naming scheme Changes the disk naming scheme from the c#t#d# format to enclosure-based. Alternatively, if the existing naming scheme is enclo- sure-based, it is changed to c#t#d# format. Note: Changing to enclosure-based naming may cause the failure of persistent disk access records for simple or nopriv disks. You can use the vxdarestore utility to repair these records. See the vxdarestore(1M) manual page for more information. This option is equivalent to using the vxddladm set namingscheme={ebn|osn} command. Note: Devices with very long device names (for example, Fibre Channel devices that include worldwide name (WWN) identifiers) are always represented by enclosure-based names. This operation has no effect on such devices. Change/Display the default disk layouts Allows you to change or display the default disk format and private region length that are used when initializing disks. Mark a disk as allocator-reserved for a disk group Reserves a disk for use with the Intelligent Storage Provisioning (ISP) feature when allocating storage space. Turn off the allocator-reserved flag on a disk Allows space on a disk to be allocated by VxVM commands other those provided with the Intelligent Storage Provisioning feature. List disk information Displays a list of disks. You can also choose to list detailed information about the disk at a specific disk device address. Hardware-Specific Note Some environments provide guidelines to optimize VxVM's interaction with intelligent storage systems. If these guidelines are present, VxVM follows the guidelines when adding disks to disk groups and when mirroring the volumes on a disk. If the operation fails due to these guideline(s), you are prompted to use the force option. The force option ignores any such storage-specific guidelines. FILES
/etc/vx/cntrls.exclude Specifies the address of controllers to exclude from vxdiskadm operations. /etc/vx/disks.exclude Specifies the address of disks to exclude from vxdiskadm operations. /etc/vx/enclr.exclude Specifies the names of enclosures to exclude from vxdiskadm operations. NOTES
EFI disks cannot be added to a disk group that is compatible with the Cross-platform Data Sharing (CDS) feature, nor can they be formatted as CDS disks. See the vxddladm(1M) manual page for information on using the vxddladm command to include or exclude specific array libraries from device discovery. SEE ALSO
vxdarestore(1M), vxddladm(1M), vxdg(1M), vxdisk(1M), vxdiskadd(1M), vxdisksetup(1M), vxevac(1M), vxintro(1M) VxVM 5.0.31.1 24 Mar 2008 vxdiskadm(1M)
All times are GMT -4. The time now is 06:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy