Sponsored Content
Full Discussion: Power machine 720 SAS disk
Operating Systems AIX Power machine 720 SAS disk Post 303042785 by Phat on Tuesday 7th of January 2020 12:13:39 AM
Old 01-07-2020
Quote:
Originally Posted by rbatte1
It depends quite what you are looking for. Do any of these help (sorry but I no longer have access to AIX so I'm a bit rusty!)
Code:
lspv
lspv -v
lspv -l
lsvpcfg                    # (possibly with a -l flag?)
lsdev -Cc disk             # Bit of a long shot perhaps
lscfg -v|grep -i disk      # Again, a bit of a guess

What are the metrics you are looking for? Is it the LPAR view of the assigned disk to the size of the disk that is owned by the hardware as a whole? The LPAR will not see that.




I hope that these suggestions give you something.
Robin
Thank Robin, I would like to check at the physical hardware console, not from LPAR, have not LPAR right now.

--- Post updated at 06:13 AM ---

Quote:
Originally Posted by zxmaus
from the hardware itself, you cannot see the disks - you can only see the controllers, not what is attached to them.

As part of the SMS menu you can see the disks and sizes if you query the controllers - or when you install AIX as you have to select a suitable disks for the installation - with location code.

If you have AIX already installed, run these commands.

to find your SAS disks, run
Code:
lsdev -Cc disk | grep -i sas

to figure out the disk size of said disks use
Code:
getconf DISK_SIZE /dev/<hdisk>

Hi Zxmaus,

I understand now that from physical hardware Power Machine we cannot check the disk and size.

Still have 1 thing to ask, for SAS disk, I see it is part of raid controller. The disk is called pdisk. After configuring raid, it becomes hdisk which AIX can see. The question is, if in the first time, we assign the controller and its disks to LPAR to install AIX. How can we configure the raid before AIX OS can see these disks?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

mount disk on other machine

I have two Unix machines on the network and now one of them are running out of disk but i have alot on the other so i like to mount the disk (or a folder) from the one that has disk and mount it on the other that does not. How do i do that? Is it possible i read the "man mount" but didn't really... (5 Replies)
Discussion started by: sajjan2
5 Replies

2. UNIX for Dummies Questions & Answers

command to know disk controllers in a machine

Hi!! I am these days working on a project, where I need to know about the disk controllers available in a machine (e.g., 3ware,IBM,etc). Please, let me know the command by which I can get the information. thnx, priyanka (3 Replies)
Discussion started by: reply2priyanka
3 Replies

3. AIX

Maximum Limit of HMC to handle Physical Power Virtualization Physical Machine

Hello All, Can anybody please tell me what is the maximum limit of Physical IBM Power Machine which can be handled by single HMC at a single point of time? Thanks, Jenish (1 Reply)
Discussion started by: jenish_shah
1 Replies

4. AIX

POWER HA 5.5 & Service IP / disk heart beat

Hello, I have a quick question regarding POWER HA ( HACMP ) 5.5 ; I have four ethernet adapters en0 en1 en2 en3 en0 is configured as BOOT_IP with IP address all other ethernet adapters are empty en1 / en2 / en3 so when I configure the service IP and start HACMP , the service IP... (2 Replies)
Discussion started by: filosophizer
2 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. AIX

Power HA 7 repository disk unmirrored?

hi guys, I don't like the new concept of the power ha 7 cluster with the repository disk and the internal solidb, I really would like to mirror this disk, but the "IBM PowerHA SystemMirror 7.1 for AIX" redbook says, normal lvm operations should not be performed on this disk. even mirroring the... (0 Replies)
Discussion started by: funksen
0 Replies

7. UNIX for Dummies Questions & Answers

How to get current power consumption of a machine

Hi Is there any native commands or somewhere in the /proc files to get the machine's power consumption? I googled for a while and cannot really find this information Thanks for your help. (6 Replies)
Discussion started by: flagman5
6 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. AIX

Power Machine password

Hi, I have installed the HMC on the VMWare VM. I try to add the power machine (managed system) and asking for a password? So this is the IBM predefined password of Power Machine? In the VMWare perspective, we can login to ESX host to do some management tasks. But how about the Power machine?... (6 Replies)
Discussion started by: Phat
6 Replies

10. AIX

Replaced pdisk not showing up in SAS Disk Array Configuration

OSLevel: 5300-10-02-0943 System Model: IBM,8203-E4A Power 6 == Hi! I replaced a failed pdisk in the raid enclosure as follows, - rmdev -l 'pdisk18' '-d' - Replaced it. - cfgmgr (detected) - I can see the new drive, with the correct serial # lscfg -v -l pdisk18 pdisk18... (2 Replies)
Discussion started by: estrar
2 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 05:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy