AIX physical DVD/CD drive

UNIX AIX
1

Hello,
I have some doubts about the dvd/cd physical on power machine and AIX.
I see on my AIX lpar and see there is 1 DVD drive and its physical location

bash-4.4#  lsdev | grep cd0
cd0        Available 03-00-00    SATA DVD-RAM Drive
bash-4.4# lscfg -vpl cd0
  cd0              U78CB.001.WZS0GY4-P2-D15  SATA DVD-RAM Drive

        Manufacturer................IBM.
        Machine Type and Model......RMBO0140532
        ROS Level and ID............RA64
        Device Specific.(Z0)........058002028F000030
        Part Number.................00RW610
        EC Level....................N99020
        FRU Number..................00RW611
        Hardware Location Code......U78CB.001.WZS0GY4-P2-D15

  PLATFORM SPECIFIC
  Name:  disk
    Node:  disk
    Device Type:  block

I check on the managed system IO tab. See the screenshot.

I didn't find the location code of DVD drive above in the list (screenshot attached)

U78CB.001.WZS0GY4-P2-D15

I'm surprised that on power machine did not have any optical device. Please correct if I'm wrong for this case.

Try to mount the DVD to see its content but not success. But the status of DVD drive is available, it should mean that DVD media is loaded. I'm not sure.

bash-4.4# mount -v cdrfs -o ro /dev/cd0  /cd
mount: 0506-324 Cannot mount /dev/cd0 on /cd: The device is not ready for operation.
2

OK, first: WHERE do you see the DVD drive? From the below output i cannot see which system the output is from. The LPAR? The VIOS? Something else?

Second:

Note that the "-P2-" in the location code means "Planar 2". Your screenshot below only shows items from Planar 1. It is either wrong or incomplete.

No. The status "Available" means that a device which was configured once is indeed connected and working - the "device", not a media in it. To understand how this works, here is an example: attach a harddisk to a system. Run cfgmgr and the harddisk device will be created. It will be "available". Now disconnect the harddisk again. It will become "defined", because its definition in the ODM (you remember from the other thread?) is still there but the disk is not. If you now use rmdev on it the ODM definitions will be removed and the device will vanish, but if you don't it will stay there. If you would reattach the disk it will go from "defined" to "available" again.

Usually you create a CD-device with a certain SMITty-panel, smitty mkdvd (or maybe smitty mkcd , i am not entirely sure) or something such. Then you attach the physical DVD drive via a DLPAR-operation and remove it the same way again. Once the drive is available you can mount/umount media until you remove the drive via another DLPAR-operation again.

I hope this helps.

bakunin

3

Hi Bakunin,

--> I see the DVD drive on the AIX lpar, not VIOS

--> sorry my fault. Please see full screenshots attached zip.

We don't have VIOS here. So any I/O devices have to be physical ones and assigned directly to the LPAR.

The strange here is I cannot find the location of DVD drive on hardware list of managed system.

4

Sorry, but still: no. Your first output showed a location code of:

U78CB.001.WZS0GY4-P2-D15

"U78CB.001.WZS0GY4" is a certain enclosure (probably the main one), "P2" means "Planar 2" and "D15" is the slot where the hardware is attached. The drive should be in this enclosure, but attached to the other planar.

The screen shots in the zip-file show the enclosures:

U5877.001.9K8J244
U5877.001.9K8G410
U5877.001.9K8G349
U5877.001.9K8G801
U5802.001.9K83626
U5802.001.9K83627
U5802.001.9K83628
...

At first: which hardware is this? It looks like a very big (and old) 570 with a lot of additional RIOs (I/O drawer?) added over time. Still, the second planar of the (main?) unit doesn't show up, neither as unassigned slots nor as adapter cards in the list. So, the list is still incomplete or wrong.

It would be interesting if you could tell us a bit more about your hardware, though: what nightmare of system is this and why in Hell don't you have any VIOS on it? It would make life so much easier!

Regarding the CD-drive directly: start by trying to mount it with:

mount /cd

which should work if the drive and everything else is defined correctly. Chances are your (Linux-inspired?) command did not work because several automatisms stood on their respective toes.

If this doesn't work, proceed:

OK, maybe you (or whoever?) created the DVD device wrong. I remember that often being a problem.

First, make sure the /cd directory over which you want to mount later is really there (yes, i know, but i have seen stranger things).

Second, remove the DVD drive entirely ( rmdev -Rdl , then run cfgmgr . Next, you open smitty storage and allocate the drive.

Here is a page describing the process. Notice that things can go wrong if you don't follow this procedure. This way it has always worked for me.

I hope this helps.

bakunin

5

Hi Bakunin,

apology for my mistake. I take screenshot of the wrong system mentioned. The first screenshot is the correct one, I uploaded here again.

That is the complete list of hardware I have now.

The info of managed system

bash-4.4# prtconf
System Model: IBM,8284-22A
Machine Serial Number: 846F8BW
Processor Type: PowerPC_POWER8
Processor Implementation Mode: POWER 8
Processor Version: PV_8_Compat
Number Of Processors: 2
Processor Clock Speed: 3891 MHz
CPU Type: 64-bit
Kernel Type: 64-bit
LPAR Info: 3 abcxxxxx
Memory Size: 6144 MB
Good Memory Size: 6144 MB
Platform Firmware level: SV840_087
Firmware Version: IBM,FW840.11 (SV840_087)
Console Login: enable
Auto Restart: true
Full Core: false
NX Crypto Acceleration: Capable and Enabled

Hardware list seen on AIX lpar

INSTALLED RESOURCE LIST

The following resources are installed on the machine.
+/- = Added or deleted from Resource List.
*   = Diagnostic support not available.

  Model Architecture: chrp
  Model Implementation: Multiple Processor, PCI bus

+ sys0                                                         System Object
+ sysplanar0                                                   System Planar
* vio0                                                         Virtual I/O Bus
* vsa0             U8284.22A.846F8BW-V2-C0                     LPAR Virtual Serial Adapter
* vty0             U8284.22A.846F8BW-V2-C0-L0                  Asynchronous Terminal
* pci3             U78CB.001.WZS0GY4-P1                        PCI Express Bus
+ usbhc0           U78CB.001.WZS0GY4-P1                        Integrated USB 3.0 xHCI Adapter (4c1041821410b204)
* pci2             U78CB.001.WZS0GY4-P1                        PCI Express Bus
+ sissas1          U78CB.001.WZS0GY4-P1-C6-T1                  PCI Express x8 Ext Dual-x4 3Gb SAS Adapter
* sas1             U78CB.001.WZS0GY4-P1-C6-T1                  Controller SAS Protocol
* sfwcomm1                                                     SAS Storage Framework Comm
* sata1            U78CB.001.WZS0GY4-P1-C6-T1                  Controller SATA Protocol
* pci1             U78CB.001.WZS0GY4-P1                        PCI Express Bus
+ sissas0          U78CB.001.WZS0GY4-P1-C14-T1                 PCIe3 x8 SAS RAID Internal Adapter 6Gb
* sas0             U78CB.001.WZS0GY4-P1-C14-T1                 Controller SAS Protocol
* sfwcomm0                                                     SAS Storage Framework Comm
+ ses0             U78CB.001.WZS0GY4-P2-Y1                     SAS Enclosure Services Device
+ pdisk0           U78CB.001.WZS0GY4-P2-D7                     Physical SAS 4K Disk Drive
+ pdisk1           U78CB.001.WZS0GY4-P2-D8                     Physical SAS 4K Disk Drive
+ pdisk2           U78CB.001.WZS0GY4-P2-D9                     Physical SAS 4K Disk Drive
* hdisk0           U78CB.001.WZS0GY4-P1-C14-T1-L206DF9A300-L0  SAS 4K RAID 0 Disk Array
* hdisk1           U78CB.001.WZS0GY4-P1-C14-T1-L606DF9A300-L0  SAS 4K RAID 0 Disk Array
* hdisk2           U78CB.001.WZS0GY4-P1-C14-T1-L406DF9A300-L0  SAS 4K RAID 0 Disk Array
* sata0            U78CB.001.WZS0GY4-P1-C14-T1                 Controller SATA Protocol
+ cd0              U78CB.001.WZS0GY4-P2-D15                    SATA DVD-RAM Drive
* pci0             U78CB.001.WZS0GY4-P1                        PCI Express Bus
+ ent0             U78CB.001.WZS0GY4-P1-C11-T1                 4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
+ ent1             U78CB.001.WZS0GY4-P1-C11-T2                 4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
+ ent2             U78CB.001.WZS0GY4-P1-C11-T3                 4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
+ ent3             U78CB.001.WZS0GY4-P1-C11-T4                 4-Port Gigabit Ethernet PCI-Express Adapter (e414571614102004)
+ L2cache0                                                     L2 Cache
+ mem0                                                         Memory
+ proc0                                                        Processor
+ proc8                                                        Processor
6

--- corrected some info.

You can see the cd device and physical location in the code, but you don't find it on the screenshot attached.

7

Ok so from the LPAR you are trying to find the CDROM run a
lsdev -Cl cd0 -F parent

On one of my S824-42A's this is the path to the CD drive:

# lscfg -vpl cd0
  cd0              U78C9.001.WZS01PX-P2-D27  SATA DVD-RAM Drive

        Manufacturer................IBM.
        Machine Type and Model......RMBO0140512
        ROS Level and ID............RA65
        Device Specific.(Z0)........058002028F000030
        Part Number.................74Y7346
        EC Level....................N23938
        FRU Number..................74Y7341
        Hardware Location Code......U78C9.001.WZS01PX-P2-D27


  PLATFORM SPECIFIC

  Name:  disk
    Node:  disk
    Device Type:  block
# lsdev -Cl cd0 -F parent
sata0

# lscfg -vpl sata0
  sata0            U78C9.001.WZS01PX-P1-C14-T1  Controller SATA Protocol

  PLATFORM SPECIFIC

  Name:  sata
    Node:  sata
    Device Type:  sata_ioa

So, when you look at the HMC, the optical drive is hanging off P1-C14-T1.

This is why bakunin was saying VIO's make this easier. You could virtualize the optical drive and dynamically add it to any lpar. The above example I gave was from a box with no VIO. 100% of resources of the frame given to the lpar.

8

Hello RecoveryOne,

bash-4.4# lscfg -vpl cd0
  cd0              U78CB.001.WZS0GY4-P2-D15  SATA DVD-RAM Drive

        Manufacturer................IBM.
        Machine Type and Model......RMBO0140532
        ROS Level and ID............RA64
        Device Specific.(Z0)........058002028F000030
        Part Number.................00RW610
        EC Level....................N99020
        FRU Number..................00RW611
        Hardware Location Code......U78CB.001.WZS0GY4-P2-D15


  PLATFORM SPECIFIC

  Name:  disk
    Node:  disk
    Device Type:  block
bash-4.4# lsdev -Cl cd0 -F parent
sata0
bash-4.4# lscfg -vpl sata0
  sata0            U78CB.001.WZS0GY4-P1-C14-T1  Controller SATA Protocol

  PLATFORM SPECIFIC

  Name:  sata
    Node:  sata
    Device Type:  sata_ioa

We can see the physical location of parent device sata0 is U78CB.001.WZS0GY4-P1-C14-T1. Check again in the HMC, it shows that the device is Raid controller. You can see in screenshot attached.

It is normal the sata device for cd is raid controller :confused:

9

Yes I know. I just take over the system from previous vendor. I don't know why they don't install the VIOS.

10

Sorry, was out for a while traveling.

There's pro's and cons of VIO's but not the time and place.

Ok so lets do a smitty cdrfs

First, lets see if something was setup in the past. I doubt it, but let us check. Arrow down to Change / Show Characteristics of a CDROM File System
You will likely be greeted to this message: 1800-051 There are no items of this type.

If that's the case, exit that prompt, and go to Add a CDROM File System . The first option for device can be auto populated via the F4=List option. You should see cd0 there.
Fill out device name and mount point (you created the /cd directory right, if so use that for the mount point). I'd leave automount set to no.

From there, go ahead and try to mount your device. Should be good to go.

11

This is actually what i already mentioned above (see #4) with smitty storage , which is the upper-level menu fastpath. As it seems Phat didn't give that even a try.

My (unfounded) suspicion is that they tried to do it the Linux way (see the mount command given above) and now the remnants of their various configuration attempts lurk there to bite them. The ODM first needs to be cleaned from all these leftovers and then the (correct) setup should work.

bakunin

12

Hi Bakunin,

Sorry for not doing that sooner. Below is the detailed output:

bash-4.4# lsdev | grep -i cd
cd0        Available 03-00-00    SATA DVD-RAM Drive
cd1        Defined   02-00-00    SATA DVD-RAM Drive
bash-4.4# lscfg -vl cd0
  cd0              U78CB.001.WZS0GY4-P2-D15  SATA DVD-RAM Drive

        Manufacturer................IBM.
        Machine Type and Model......RMBO0140532
        ROS Level and ID............RA64
        Device Specific.(Z0)........058002028F000030
        Part Number.................00RW610
        EC Level....................N99020
        FRU Number..................00RW611
        Hardware Location Code......U78CB.001.WZS0GY4-P2-D15

bash-4.4# lsdev -Cl cd0 -F parent
sata0
bash-4.4# lscfg -vl sata0
  sata0            U78CB.001.WZS0GY4-P1-C14-T1  Controller SATA Protocol
bash-4.4# rmdev -Rdl cd1
cd1 deleted
bash-4.4# rmdev -Rdl cd0
cd0 deleted
bash-4.4# lsdev | grep -i cd
bash-4.4# cfgmgr
bash-4.4# lsdev | grep -i cd
cd0        Available 03-00-00    SATA DVD-RAM Drive

Also tried this as well, but cannot put the device name. You can see it in the screenshot

https://publib.boulder.ibm.com/tividd/td/TEDW/GC32-0744-03/en_US/HTML/insmst293.htm
13

Hi RecoveryOne,

Have tried that Change / Show Characteristics of a CDROM File System and found the screenshot attached.

Tried with Add a CDROM File System got the same issue as suggested by Bakunin.