Sponsored Content
Operating Systems AIX Replaced pdisk not showing up in SAS Disk Array Configuration Post 303036290 by hicksd8 on Friday 21st of June 2019 01:31:30 PM
Old 06-21-2019
I'll start by stating that I'm not an AIX person and I'm not familiar with the RAID controller you have there. I am a storage person.

However, with a part number of ST3300656SS that is not a disk manufactured by IBM; it is OEM'd from Seagate.

I'm well aware that Seagate disks of the exact same part number can have a slightly different LBA count and when the LBA count is less than the existing RAID members, the RAID controller refuses to configure it. So just be aware and don't fall for that one.

Check that the LBA's on the disk you replaced is at least equal, or more than, the existing RAID members.

EDIT: The total LBA's (Logical blocks) are usually written on the disk label.

Last edited by hicksd8; 06-21-2019 at 02:38 PM..
These 2 Users Gave Thanks to hicksd8 For This Post:
 

10 More Discussions You Might Find Interesting

1. Solaris

T5240 and Internal SAS RAID Configuration help

Dear Friends, I need to configure T5240 with Internal SAS RAID HBA(SG-XPCIESAS-R-INT-Z).. T5240 uses 8 hard disks... From the documents of RAID card I have found that I need to create a jump start server to include three packages SUNWaac, StorMan, SUNWgccruntime if Im using solaris10 5/08... ... (5 Replies)
Discussion started by: nicktrix
5 Replies

2. Solaris

3320 Disk Array Configuration for Oracle 10

We have a dual-controller StorEdge 3320 disk array with 5 disks (each 320 MB). Four disks have been set up in a RAID-5 configuration with the remaining disk acting as a hot spare. There is a single logical drive which has been partitioned into 3 slices. The disk array is to be simultaneously... (14 Replies)
Discussion started by: StarSol
14 Replies

3. AIX

add SSA pdisk to array to become hdisk

May I know how can I add a new SSA pdisk into array and become usable hdisk? I have inserted a 36GB SSA disk into enclosure and done the "cfgmgr" and I can see it already been regconized as pdisk47. I would like to make it a system disk in order for me to add to my volume group. Please let me... (3 Replies)
Discussion started by: kwliew999
3 Replies

4. Solaris

Veritas not attaching replaced disk

Hi, I`m on SunFire480R with Solaris 10. Disk in rootdg group failed, so it was replaced. However, I cannot make Veritas initalise the replaced disk: # vxdctl enable # vxdisk list c1t0d0s2 Device: c1t0d0s2 devicetag: c1t0d0 type: auto flags: online error private autoconfig... (1 Reply)
Discussion started by: masloff
1 Replies

5. UNIX for Dummies Questions & Answers

find physical disk type : SAS / SATA

Hi, Is there an easy way to find the disk-type from the command line or with another api ? sdparm works for SAS but not for SATA, hdparm works for SATA but not SAS. Thanks (1 Reply)
Discussion started by: coderd
1 Replies

6. Ubuntu

Linux LVM.. Grub not loading from replaced disk

Hi, a little while ago, one of the GPT Partitioned hard disk had gone faulty in a Mirror RAID and is now successfully replaced. here is how I did that. 1) created identical partition table on the new disk. 2) attached the mirrors using md commands. The whole procedure is given... (5 Replies)
Discussion started by: busyboy
5 Replies

7. Linux

Grub not loading from replaced disk

Hi, a little while ago, one of the GPT Partitioned hard disk had gone faulty in a Mirror RAID and is now successfully replaced. here is how I did that. 1) created identical partition table on the new disk. 2) attached the mirrors using md commands. The whole procedure is given below:... (2 Replies)
Discussion started by: busyboy
2 Replies

8. Red Hat

Udev Rule TAG for identifying a local sas disk, non-scsi, non-fiber, non-iscsi

I need to add a VMware virtual disk to the 99-oracle-asmdevices.rules file but the OS is not assigning a WWID to the disk. It has been fdisk'd and a single partition created. What TAG inside the file needs to be added? the Program scsi-id does not work for some reason. latest patches... (0 Replies)
Discussion started by: mrmurdock
0 Replies

9. Filesystems, Disks and Memory

DISK ARRAY PROTECTION SUSPENDED message displayed following disk replacement

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

10. AIX

Power machine 720 SAS disk

Hello, I would like to check how many SAS disks and its size per disk for the whole power system. As per my understanding, if we assign the SAS controller to LPAR, then we can see the disk in lpar smitty command. How can we check from the Power machine(physical ones) as well? I think the... (5 Replies)
Discussion started by: Phat
5 Replies
re(7)							 Miscellaneous Information Manual						     re(7)

NAME
re - SWXCR RAID interface SYNOPSIS
2100 Server Model A500MP DEC SWXCR controller xcrn at * vector xcintr device disk renn at xcrn drive nn DESCRIPTION
The re driver is for the SWXCR RAID Array controller. The following rules are used to determine the major and minor numbers that are associated with an re type disk. There are two major num- bers used to represent re disks. The major numbers are 11 for block devices and 44 for character (raw) devices. The minor number is used to represent both the unit number and partition. A disk partition refers to a designated portion of the physical disk. To accomplish this reference, the 20-bit minor number is divided into three parts. The lowest six bits of the minor number specify a disk partition. The partitions use a letter, a through h, for their name. The next three bits of the minor number specify the RE unit number for a unit attached to an SWXCR controller. The final 11 bits specify the controller number. The device special file names associated with re disks are based on conventions that are closely associated with the minor number assigned to the disk. The standard device names begin with re for block special files and rre for character (raw) special files. Following the re is the unit number and then a letter, a through h, that represents the partition. Throughout this reference page, the question mark (?) character represents the unit number in the name of the device special file. For example, re?b could represent re0b, re1b, and so on. The unit number can be calculated if the major and minor numbers of an re disk are provided. For example, suppose you have a device spe- cial file rre6a, with a major number of 44 and a minor number of 384. The partition is represented by the lower six bits of the number 384. These lower six bits of the number 384 are 0, which specifies the a partition. The next three bits of the minor number 384 specify the unit number, which is 6. The next eleven bits specify the controller number, which is zero. Putting these three pieces together reveals that the major/minor number pair 44/384 refers to the a partition of unit 6 attached to controller number 0. A disk can be accessed through either the block special file or the character special file. The block special file accesses the disk using the file system's normal buffering mechanism. Reads and writes to the block special file can specify any size. This capability avoids the need to limit data transfers to the size of physical disk records and to calculate offsets within disk records. The file system can break up large read and write requests into smaller fixed size transfers to the disk. The character special file provides a raw interface that allows for direct transmission between the disk and the user's read or write buf- fer. A single read or write to the raw interface results in exactly one I/O operation. Consequently, raw I/O may be considerably more efficient for large transfers. For systems with RE disks, the first software boot after the system is powered on may take longer than expected. This delay is normal and is caused by the software spinning up the RE disks. Disk Support The RE driver handles all disk drives that can be connected to the SWXCR controller. To determine which drives are supported for specific CPU types and hardware configurations, see the Installation and Configuration Guide for the StorageWorks RAID Array 200 Subsystem Family. SWXCR RAID Controllers are viewed in all cases as RE type disks. There are some notable differences that should be taken into considera- tion when configuring a RAID device: Currently only sector sizes of 512 bytes are supported. Logical Volume sizes are not fixed sizes as compared to other disk devices. The size of the Logical Volume is configurable based on needs. The dynamic nature of Logical Volume sizes is dealt with by defining RAID devices as DYNAMIC. Only partitions a, b, c, and g are defined. If necessary, the disklabel(8) command can be run to change and define partitions for RAID devices. Usually, the re?a partition is used for the root file system and the re?b partition as a paging area. The re?c partition can be used for disk-to-disk copying because it maps the entire disk. The starting location and length (in 512 byte sectors) of the disk partitions of each drive are shown in the following table. Partition sizes can be changed by using the disklabel(8) command. SWXCR (RAID) partitions for systems based on the Alpha AXP architecture disk start length re?a 0 131072 re?b 131072 262144 re?c 0 end of media re?d 0 0 re?e 0 0 re?f 0 0 re?g 393216 end of media re?h 0 0 FILES
/dev/re??? /dev/rre??? /etc/disktab RELATED INFORMATION
disklabel(8), MAKEDEV(8), uerf(8) delim off re(7)
All times are GMT -4. The time now is 10:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy