LDOM multipathing feature: failback of disk io?

Hello,
I have two io domains and have passed a FC LUN to a guest LDOM via both io domains using the LDOM multipathing feature ("mpgroup"). When one io domain is shut down, failing over the io to the other io domain works without a problem.
But when the io domain is up again, the disk io continues to run over the io domain that remained online. This means that after a reboot of an io domain all disk io from all guest LDOMs (which use LDOM multipathing) continues to run over the other io domain. No traffic will be running over the io domain that was rebooted.
Of course every io domain should be sized big enough to carry all io in the case of a failure of the other io domain. But still the question: Is there a way to redistribute LDOM multipathing disk io more evenly when an io domain recovers and is up again?
I'm using:
- T4-4
- LDoms Manager software 2.1.0.4
- Solaris 11 on both io domains (pkg://solaris/system/[email protected],5.11-0.175.0.0.0.2.1:20111019T075711Z)
Kind regards,
Jochen
Edited by: user6353652 on 25.05.2012 00:56
Edited by: user6353652 on 25.05.2012 00:58
Edited by: user6353652 on 25.05.2012 00:59

As far as I know then only way to "re-balance" the I/O across the domains is to unbind/bind the guests. Not a great answer, but this could be done as part of the guests patching cycle.
I think there is an RFE to provide MPxIO-like features to guests.

Similar Messages

  • Best multipath config for Asm disks?

    Hi,
    I want to install grid 11.2.0.4 on linux with netapp.
    Netapp lun needs multipath.
    What is the best config?
    Actually this is my ocr lun:
    360a98045342554d4f3f453274477178 dm-8 NETAPP,LUN
    size=3.0G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=4 status=active
    | |- 0:0:1:3 sdh 8:112 active ready running
    | `- 1:0:1:3 sdp 8:240 active ready running
    `-+- policy='round-robin 0' prio=1 status=enabled
      |- 1:0:0:3 sdl 8:176 active ready running
      `- 0:0:0:3 sdd 8:48  active ready running
    Thank you

    ASMLib does not handle device path failover, which is the purpose of DM multipath. ASM cannot handle seeing the same disk twice. If it does, it will cause an error. There are special considerations when using ASMLib with Multipath and it is required to configure ASMLib to only use the multipath access point:
    A single disk can appear three times in a multipath configuration:
    The first path to the disk
    The second path to the disk
    The multipath access point
    Configuring Oracle ASMLib on Multipath Disks

  • Cold migration of old LDoms with slice-based system disks - not possible?

    We have a couple of older T5120s that we would like to upgrade both the firmware and LDoms software on.
    Currently they both run LDoms 1.2; we'd like to go to 2.0 or hopefully 2.1.
    cas2:1:1006 [root] # ldm -V
    Logical Domain Manager (v 1.2_patch)
    Hypervisor control protocol v 1.4
    Using Hypervisor MD v 1.1
    System PROM:
    Hypervisor v. 1.7.4. @(#)Hypervisor 1.7.4.a 2009/09/21 08:25\015
    OpenBoot v. 4.30.4 @(#)OBP 4.30.4 2009/08/19 07:23
    We thought we would clear out our other "sandbox" T5120 (with LDoms 2.0) and migrate the client LDoms in the machines to be updated over to the sandbox, so if anything went wrong we could clear out the old 1.2 machine and then re-migrate the LDoms back over to it.
    Well, it turns out the client LDoms on the 1.2 system were made with paired slices as the system disks instead of files :-(
    vdisk0@casdev c1t0d0s3
    vdisk1@casdev c1t1d0s3
    vdisk0@casray c1t0d0s1
    vdisk1@casray c1t1d0s1
    In one of the client LDoms it has (as you would expect, given this setup)
    NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
    casdev active -n---- 5000 12 4G 0.1% 414d 18h
    DISK
    NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
    vdisk0 c1t0d0s3@primary-vds0 0 disk@0 primary
    vdisk1 c1t1d0s3@primary-vds0 1 disk@1 primary
    The control LDom for these client LDoms has 2 disks and slice 0 of each disk (~ 20 GB) is used for the control LDom, and there are these other slices (slice 1, 3, ... also each ~ 20 GB) for the client LDoms.
    The target "sandbox" system we wanted to migrate to also has 2 disks, but slice 0 of each is a single, disk-spanning partition - since we're using files as virtual disks for the client LDoms that were previously on that system (since wiped out), there was no need for multiple slices.
    I'm guessing that with this setup there is no way to even do a cold migration of the old LDoms 1.2 client LDoms to the newer LDoms 2.0 sandbox system, short of a complete reinstall of the sandbox to create a similar slice-based setup. :-(
    (Unless it involved somehow re-slicing the control LDom's disks and making identically-sized partitions to match the old system's and then - somehow - "dd"'ing the source system's client LDom disk slices over into the target system's)
    Am I right?
    Edited by: Riot Nrrrd™ on Oct 28, 2011 3:30 PM

    I'm guessing that with this setup there is no way to even do a cold migration of the old LDoms 1.2 client LDoms to the newer LDoms 2.0 sandbox system, short of a complete reinstall of the sandbox to create a similar slice-based setup. :-(
    (Unless it involved somehow re-slicing the control LDom's disks and making identically-sized partitions to match the old system's and then - somehow - "dd"'ing the source system's client LDom disk slices over into the target system's)If you are not using SAN-disks, then it is a bit difficult to do the migration. If you are using ZFS on LDoms 2.0 sandbox, you could try to create ZFS volumes for guest domains and send data on those volumes from LDoms 1.2 system, after creating guest domains from exported XML configurationg files.
    Does this sound tryable solution?

  • Windows 7 start up says feature requires removable disk or usb drive

     I have a hp pavilion windows 7 home, the last 4 times I have tried to log on I get a pop up that says feature requires removable media like a floppy disk or usb drive. Insert then try again. I have never seen this before and have not had any problems until now. Can someone please let me know whats going on. I have not added or changed anything to cause this and it's very frustrating not able to log on quickly.Thanks

    Deb04, welcome to the forum.
    When requesting help you should always include the make/model of the computer and/or monitor. This information is necessary for us to review the specifications of them.  
    Signature:
    HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
    HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
    HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
    HP Photosmart 7520 AIO
    ++++++++++++++++++
    **Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
    Intelligence is God given; Wisdom is the sum of our mistakes!
    I am not an HP employee.

  • Physical path of disk are differing in OBP and OS in LDOM's

    Hi,
    {0} ok devalias
    screen /pci@380/pci@1/pci@0/pci@3/display@0
    rootmirror /pci@3c0/pci@1/pci@0/pci@2/scsi@0/disk@w5000cca04327a4a1,0
    rootdisk /pci@3c0/pci@1/pci@0/pci@2/scsi@0/disk@w5000cca043280f69,0
      pool: rpool
    state: ONLINE
    scan: none requested
    config:
    NAME STATE     READ WRITE CKSUM
    rpool ONLINE       0 0     0
    mirror-0 ONLINE       0 0     0
    c0t5000CCA043280F68d0s0  ONLINE 0     0     0
    c0t5000CCA04327A4A0d0s0  ONLINE 0     0     0
    errors: No known data errors
    ${PWD}#ls -l /dev/rdsk/c0t5000CCA043280F68d0s0
    lrwxrwxrwx   1 root root          52 Oct 21 22:25 /dev/rdsk/c0t5000CCA043280F68d0s0 -> ../../devices/scsi_vhci/disk@g5000cca043280f68:a,raw
    ${PWD}#ls -l /dev/rdsk/c0t5000CCA04327A4A0d0s0
    lrwxrwxrwx   1 root root          52 Oct 21 22:25 /dev/rdsk/c0t5000CCA04327A4A0d0s0 -> ../../devices/scsi_vhci/disk@g5000cca04327a4a0:a,raw
    ${PWD}#prtconf -vp | grep -i bootpath
            bootpath: '/pci@3c0/pci@1/pci@0/pci@2/scsi@0/disk@w5000cca043280f69,0:a'
    can any one explain this differecne. It is an alternate LDOM. (LDOM version3)
    Regards
    Yogi

    Hi Eze,
    Thankyou for your reply. I need some more help from you to understand in depth.
    I tried all possiblity of the document you gave but i am unable to find the info about mpxio in scsi (but in fp).
    please help me how it is acting in my setup.
    #/dev/dsk#zpool status rpool
      pool: rpool
    state: ONLINE
    scan: none requested
    config:
            NAME                         STATE     READ WRITE CKSUM
            rpool                        ONLINE       0     0     0
              mirror-0                   ONLINE       0     0     0
                c0t5000CCA043280F68d0s0  ONLINE       0     0     0
                c0t5000CCA04327A4A0d0s0  ONLINE       0     0     0
    errors: No known data errors
    #/dev/dsk#cfgadm -al
    Ap_Id                          Type         Receptacle   Occupant     Condition
    c1                             scsi-sas     connected    configured   unknown
    c1::dsk/c1t3d0                 CD-ROM       connected    configured   unknown
    c2                             scsi-sas     connected    configured   unknown
    c2::w5000cca043280f69,0        disk-path    connected    configured   unknown
    c3                             scsi-sas     connected    configured   unknown
    c3::w5000cca04327a4a1,0        disk-path    connected    configured   unknown
    c4                             scsi-sas     connected    unconfigured unknown
    c5                             fc           connected    unconfigured unknown
    c6                             fc-fabric    connected    configured   unknown
    c6::21000024ff58c7b7           unknown      connected    unconfigured unknown
    c6::500507680110d6ed           disk         connected    configured   unknown
    c6::500507680110d702           disk         connected    configured   unknown
    c7                             fc           connected    unconfigured unknown
    c8                             fc-fabric    connected    configured   unknown
    c8::21000024ff596e77           unknown      connected    unconfigured unknown
    c8::500507680120d6ed           disk         connected    configured   unknown
    c8::500507680120d702           disk         connected    configured   unknown
    #/dev/dsk#grep -i mpxio /kernel/drv/scsi_vhci.conf
    # For enabling MPxIO support for 3rd party symmetric device need an
    #/dev/dsk#grep -i mpxio /kernel/drv/fp.conf
    # I/O multipathing feature (MPxIO) can be enabled or disabled using
    # mpxio-disable property. Setting mpxio-disable="no" will activate
    # I/O multipathing; setting mpxio-disable="yes" disables the feature.
    # Global mpxio-disable property:
    # To globally enable MPxIO on all fp ports set:
    # mpxio-disable="no";
    # To globally disable MPxIO on all fp ports set:
    # mpxio-disable="yes";
    # Per port mpxio-disable property:
    # You can also enable or disable MPxIO on a per port basis.
    # To disable MPxIO on port 0 whose parent is /pci@8,600000/SUNW,qlc@4 set:
    # name="fp" parent="/pci@8,600000/SUNW,qlc@4" port=0 mpxio-disable="yes";
    # NOTE: If you just want to enable or disable MPxIO on all fp ports, it is
    mpxio-disable="yes";
    #/dev/dsk#luxadm display /dev/rdsk/c0t5000CCA04327A4A0d0s0
    Error: Could not find valid path to the device. - /devices/scsi_vhci/disk@g5000cca04327a4a0:a,raw.
    #/dev/dsk#luxadm display /dev/rdsk/c0t5000CCA04327A4A0d0s2
    Error: Could not find valid path to the device. - /devices/scsi_vhci/disk@g5000cca04327a4a0:c,raw.
    #/dev/dsk#ls -l /dev/dsk/c0t5000CCA04327A4A0d0s0
    lrwxrwxrwx   1 root     root          48 Oct 21 22:25 /dev/dsk/c0t5000CCA04327A4A0d0s0 -> ../../devices/scsi_vhci/disk@g5000cca04327a4a0:a
    #/dev/dsk#prtconf -vp | grep -i bootpath
            bootpath:  '/pci@3c0/pci@1/pci@0/pci@2/scsi@0/disk@w5000cca043280f69,0:a'
    #/dev/dsk#fcinfo hba-port
    HBA Port WWN: 21000024ff58c71c
            OS Device Name: /dev/cfg/c5
            Manufacturer: QLogic Corp.
            Model: 371-4325-02
            Firmware Version: 05.08.00
            FCode/BIOS Version:  BIOS: 2.02; fcode: 2.03; EFI: 2.01;
            Serial Number: 0402T00-1408178861
            Driver Name: qlc
            Driver Version: 20130621-4.02b
            Type: unknown
            State: offline
            Supported Speeds: 2Gb 4Gb 8Gb
            Current Speed: not established
            Node WWN: 20000024ff58c71c
    HBA Port WWN: 21000024ff58c71d
            OS Device Name: /dev/cfg/c6
            Manufacturer: QLogic Corp.
            Model: 371-4325-02
            Firmware Version: 05.08.00
            FCode/BIOS Version:  BIOS: 2.02; fcode: 2.03; EFI: 2.01;
            Serial Number: 0402T00-1408178861
            Driver Name: qlc
            Driver Version: 20130621-4.02b
            Type: N-port
            State: online
            Supported Speeds: 2Gb 4Gb 8Gb
            Current Speed: 8Gb
            Node WWN: 20000024ff58c71d
    HBA Port WWN: 21000024ff5a87dc
            OS Device Name: /dev/cfg/c7
            Manufacturer: QLogic Corp.
            Model: 371-4325-02
            Firmware Version: 05.08.00
            FCode/BIOS Version:  BIOS: 2.02; fcode: 2.03; EFI: 2.01;
            Serial Number: 0402T00-1424200657
            Driver Name: qlc
            Driver Version: 20130621-4.02b
            Type: unknown
            State: offline
            Supported Speeds: 2Gb 4Gb 8Gb
            Current Speed: not established
            Node WWN: 20000024ff5a87dc
    HBA Port WWN: 21000024ff5a87dd
            OS Device Name: /dev/cfg/c8
            Manufacturer: QLogic Corp.
            Model: 371-4325-02
            Firmware Version: 05.08.00
            FCode/BIOS Version:  BIOS: 2.02; fcode: 2.03; EFI: 2.01;
            Serial Number: 0402T00-1424200657
            Driver Name: qlc
            Driver Version: 20130621-4.02b
            Type: N-port
            State: online
            Supported Speeds: 2Gb 4Gb 8Gb
            Current Speed: 8Gb
            Node WWN: 20000024ff5a87dd
    #/dev/dsk#luxadm -e port
    /devices/pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0/fp@0,0:devctl        NOT CONNECTED
    /devices/pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0/fp@0,0:devctl        NOT CONNECTED
    /devices/pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0:devctl      CONNECTED
    /devices/pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0:devctl      CONNECTED
    #/dev/dsk#echo | format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
           0. c6t500507680110D6EDd0 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,0
           1. c6t500507680110D6EDd1 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,1
           2. c6t500507680110D6EDd2 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,2
           3. c6t500507680110D6EDd3 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,3
           4. c6t500507680110D6EDd4 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,4
           5. c6t500507680110D6EDd5 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,5
           6. c6t500507680110D6EDd6 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,6
           7. c6t500507680110D6EDd7 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,7
           8. c6t500507680110D6EDd8 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,8
           9. c6t500507680110D6EDd9 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,9
          10. c6t500507680110D6EDd10 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,a
          11. c6t500507680110D6EDd11 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,b
          12. c6t500507680110D6EDd12 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,c
          13. c6t500507680110D6EDd13 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,d
          14. c6t500507680110D6EDd14 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,e
          15. c6t500507680110D6EDd15 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,f
          16. c6t500507680110D6EDd16 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,10
          17. c6t500507680110D6EDd17 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,11
          18. c6t500507680110D6EDd18 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,12
          19. c6t500507680110D6EDd19 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,13
          20. c6t500507680110D6EDd20 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,14
          21. c6t500507680110D6EDd21 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,15
          22. c6t500507680110D6EDd22 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,16
          23. c6t500507680110D6EDd23 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,17
          24. c6t500507680110D6EDd24 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,18
          25. c6t500507680110D6EDd25 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,19
          26. c6t500507680110D6EDd26 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,1a
          27. c6t500507680110D6EDd27 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,1b
          28. c6t500507680110D6EDd28 <IBM-2145-0000-30.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,1c
          29. c6t500507680110D6EDd29 <IBM-2145-0000-30.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,1d
          30. c6t500507680110D6EDd30 <IBM-2145-0000-30.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,1e
          31. c6t500507680110D6EDd31 <IBM-2145-0000-120.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,1f
          32. c6t500507680110D6EDd32 <IBM-2145-0000-120.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,20
          33. c6t500507680110D6EDd33 <IBM-2145-0000-120.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,21
          34. c6t500507680110D6EDd34 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,22
          35. c6t500507680110D6EDd35 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,23
          36. c6t500507680110D6EDd36 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,24
          37. c6t500507680110D6EDd37 <IBM-2145-0000 cyl 5118 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,25
          38. c6t500507680110D6EDd38 <IBM-2145-0000-120.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,26
          39. c6t500507680110D6EDd39 <IBM-2145-0000 cyl 12798 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d6ed,27
          40. c6t500507680110D702d0 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,0
          41. c6t500507680110D702d1 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,1
          42. c6t500507680110D702d2 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,2
          43. c6t500507680110D702d3 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,3
          44. c6t500507680110D702d4 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,4
          45. c6t500507680110D702d5 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,5
          46. c6t500507680110D702d6 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,6
          47. c6t500507680110D702d7 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,7
          48. c6t500507680110D702d8 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,8
          49. c6t500507680110D702d9 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,9
          50. c6t500507680110D702d10 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,a
          51. c6t500507680110D702d11 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,b
          52. c6t500507680110D702d12 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,c
          53. c6t500507680110D702d13 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,d
          54. c6t500507680110D702d14 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,e
          55. c6t500507680110D702d15 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,f
          56. c6t500507680110D702d16 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,10
          57. c6t500507680110D702d17 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,11
          58. c6t500507680110D702d18 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,12
          59. c6t500507680110D702d19 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,13
          60. c6t500507680110D702d20 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,14
          61. c6t500507680110D702d21 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,15
          62. c6t500507680110D702d22 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,16
          63. c6t500507680110D702d23 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,17
          64. c6t500507680110D702d24 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,18
          65. c6t500507680110D702d25 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,19
          66. c6t500507680110D702d26 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,1a
          67. c6t500507680110D702d27 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,1b
          68. c6t500507680110D702d28 <IBM-2145-0000-30.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,1c
          69. c6t500507680110D702d29 <IBM-2145-0000-30.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,1d
          70. c6t500507680110D702d30 <IBM-2145-0000-30.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,1e
          71. c6t500507680110D702d31 <IBM-2145-0000-120.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,1f
          72. c6t500507680110D702d32 <IBM-2145-0000-120.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,20
          73. c6t500507680110D702d33 <IBM-2145-0000-120.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,21
          74. c6t500507680110D702d34 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,22
          75. c6t500507680110D702d35 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,23
          76. c6t500507680110D702d36 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,24
          77. c6t500507680110D702d37 <IBM-2145-0000 cyl 5118 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,25
          78. c6t500507680110D702d38 <IBM-2145-0000-120.00GB>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,26
          79. c6t500507680110D702d39 <IBM-2145-0000 cyl 12798 alt 2 hd 64 sec 256>
              /pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680110d702,27
          80. c8t500507680120D6EDd1 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,1
          81. c8t500507680120D6EDd3 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,3
          82. c8t500507680120D6EDd5 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,5
          83. c8t500507680120D6EDd7 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,7
          84. c8t500507680120D6EDd9 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,9
          85. c8t500507680120D6EDd11 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,b
          86. c8t500507680120D6EDd13 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,d
          87. c8t500507680120D6EDd15 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,f
          88. c8t500507680120D6EDd17 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,11
          89. c8t500507680120D6EDd19 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,13
          90. c8t500507680120D6EDd21 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,15
          91. c8t500507680120D6EDd22 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,16
          92. c8t500507680120D6EDd23 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,17
          93. c8t500507680120D6EDd24 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,18
          94. c8t500507680120D6EDd25 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,19
          95. c8t500507680120D6EDd26 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,1a
          96. c8t500507680120D6EDd27 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,1b
          97. c8t500507680120D6EDd29 <IBM-2145-0000-30.00GB>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,1d
          98. c8t500507680120D6EDd31 <IBM-2145-0000-120.00GB>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,1f
          99. c8t500507680120D6EDd33 <IBM-2145-0000-120.00GB>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,21
         100. c8t500507680120D6EDd34 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,22
         101. c8t500507680120D6EDd35 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,23
         102. c8t500507680120D6EDd36 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,24
         103. c8t500507680120D6EDd37 <IBM-2145-0000 cyl 5118 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,25
         104. c8t500507680120D6EDd38 <IBM-2145-0000-120.00GB>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,26
         105. c8t500507680120D6EDd39 <IBM-2145-0000 cyl 12798 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d6ed,27
         106. c8t500507680120D702d0 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,0
         107. c8t500507680120D702d2 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,2
         108. c8t500507680120D702d4 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,4
         109. c8t500507680120D702d6 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,6
         110. c8t500507680120D702d8 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,8
         111. c8t500507680120D702d10 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,a
         112. c8t500507680120D702d12 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,c
         113. c8t500507680120D702d14 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,e
         114. c8t500507680120D702d16 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,10
         115. c8t500507680120D702d18 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,12
         116. c8t500507680120D702d20 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,14
         117. c8t500507680120D702d22 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,16
         118. c8t500507680120D702d23 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,17
         119. c8t500507680120D702d24 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,18
         120. c8t500507680120D702d25 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,19
         121. c8t500507680120D702d26 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,1a
         122. c8t500507680120D702d27 <IBM-2145-0000 cyl 1022 alt 2 hd 32 sec 64>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,1b
         123. c8t500507680120D702d28 <IBM-2145-0000-30.00GB>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,1c
         124. c8t500507680120D702d30 <IBM-2145-0000-30.00GB>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,1e
         125. c8t500507680120D702d32 <IBM-2145-0000-120.00GB>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,20
         126. c8t500507680120D702d34 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,22
         127. c8t500507680120D702d35 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,23
         128. c8t500507680120D702d36 <IBM-2145-0000 cyl 8958 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,24
         129. c8t500507680120D702d37 <IBM-2145-0000 cyl 5118 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,25
         130. c8t500507680120D702d38 <IBM-2145-0000-120.00GB>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,26
         131. c8t500507680120D702d39 <IBM-2145-0000 cyl 12798 alt 2 hd 64 sec 256>
              /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/ssd@w500507680120d702,27
         132. disk_0s6 <HITACHI-H109030SESUN300G-A690 cyl 46873 alt 2 hd 20 sec 625>  solaris
              /dev/vx/rdmp/disk_0s6
         133. disk_1 <HITACHI-H109030SESUN300G-A690 cyl 46873 alt 2 hd 20 sec 625>  solaris
              /dev/vx/rdmp/disk_1
         134. san_vc0_00070as4 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /dev/vx/rdmp/san_vc0_00070as4
         135. san_vc0_00070bs7 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /dev/vx/rdmp/san_vc0_00070bs7
         136. san_vc0_00070cs0 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /dev/vx/rdmp/san_vc0_00070cs0
         137. san_vc0_00070ds1 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /dev/vx/rdmp/san_vc0_00070ds1
         138. san_vc0_00070es6 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /dev/vx/rdmp/san_vc0_00070es6
         139. san_vc0_00070fs5 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /dev/vx/rdmp/san_vc0_00070fs5
         140. san_vc0_000704 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /dev/vx/rdmp/san_vc0_000704
         141. san_vc0_000705s0 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /dev/vx/rdmp/san_vc0_000705s0
         142. san_vc0_000706s3 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /dev/vx/rdmp/san_vc0_000706s3
         143. san_vc0_000707s4 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /dev/vx/rdmp/san_vc0_000707s4
         144. san_vc0_000708s1 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /dev/vx/rdmp/san_vc0_000708s1
         145. san_vc0_000709s6 <IBM-2145-0000 cyl 10238 alt 2 hd 64 sec 256>
              /dev/vx/rdmp/san_vc0_000709s6
         146. san_vc0_000710s5 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /dev/vx/rdmp/san_vc0_000710s5
         147. san_vc0_000711s2 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /dev/vx/rdmp/san_vc0_000711s2
         148. san_vc0_000712s1 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /dev/vx/rdmp/san_vc0_000712s1
         149. san_vc0_000713s6 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /dev/vx/rdmp/san_vc0_000713s6
         150. san_vc0_000714s7 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /dev/vx/rdmp/san_vc0_000714s7
         151. san_vc0_000715s0 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /dev/vx/rdmp/san_vc0_000715s0
         152. san_vc0_000716s3 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /dev/vx/rdmp/san_vc0_000716s3
         153. san_vc0_000717s4 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /dev/vx/rdmp/san_vc0_000717s4
         154. san_vc0_000718s1 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /dev/vx/rdmp/san_vc0_000718s1
         155. san_vc0_000719s6 <IBM-2145-0000 cyl 20478 alt 2 hd 32 sec 64>
              /dev/vx/rdmp/san_vc0_000719s6
         156. san_vc0_000720s2 <IBM-2145-0000-30.00GB>
              /dev/vx/rdmp/san_vc0_000720s2
         157. san_vc0_000721s5 <IBM-2145-0000-30.00GB>
              /dev/vx/rdmp/san_vc0_000721s5
         158. san_vc0_000722s6 <IBM-2145-0000-30.00GB>
              /dev/vx/rdmp/san_vc0_000722s6
         159. san_vc0_000723s1 <IBM-2145-0000-120.00GB>
              /dev/vx/rdmp/san_vc0_000723s1
         160. san_vc0_000724s0 <IBM-2145-0000-120.00GB>
              /dev/vx/rdmp/san_vc0_000724s0
         161. san_vc0_000725 <IBM-2145-0000-120.00GB>
              /dev/vx/rdmp/san_vc0_000725
    Specify disk (enter its number): Specify disk (enter its number):
    #/dev/dsk#
    Regards
    Yogi

  • Can't get the partition disk back

    So I basically want to remove my windows 7 on my macbook air 2013
    I followed the instruction until the last step it should be restore, but during the process something went wrong and it just stopped, and quitted.
    Now I could not restore my drive space, and I need it around these days, could anyone help me with this?

    varjak paw wrote:
    There is no DMG of Lion, at least not anything legal. From where did you get this file?
    Well there is a DMG of both Lion and Mt Lion. But it is included in the Lion/Mt Lion OS X Install.app package files and can be copied out.
    But that is Not the Operating System. It is the Install files for the operating system. Restoring that DMG would, supposedly, give you bootable media for installing the OS on a drive.
    To the OP I have found that the Restore feature/function in Disk Utility doesn't always work as expected. Best thing to do is use this program for creating a Dual Layer DVD or USB thumb of the Mt Lion install files. It works every time.
    Make the USB thumb as most of the, Not So, Superdrives can't really write to Dual Layer DVDs. You will be very lucky if you have a Superdrive that will actually write to Dual Layer DVDs.

  • E3000, USB NAS storage - disk disappears when unit sleeps the drive

    Working to get network attached storage working on my new E3000.  Have Western Digital My Book drive and the unit has a feature where the disk goes into a sleep mode when not used. 
    Appears that when the disk does this when attached to the E3000, the router thinks the disk is gone. Trying to connect to the drive from the network does not seem to wake up the storage.
    Like to be able to save power and wear by not spinning the disk all the time....
    Firmware 1.0.03
    Any suggestions?

    the issue is the drive is going to sleep and the router can not detect it to wake it up. western digital has stated (based from others who have contacted WD support) the drive is not compatible with NAS'ed routers.
    i dont know about WD but seagate has software in the drive to disable the sleep state..
    and you would rather have the drive SPINNING rather than sleeping/spinning/sleeping as this causes MORE WEAR vs. having it spin constant.
    i have a couple buffalo drives 500gb, and had one on an e2 and e3 and now an e42(which ive now added a 2TB seagate go flex drive--no issues btw...) and never had them spin down and give the error.
    so perhaps since you can not disable the sleep mode on the WD, and that WD itself has stated thru internet users/google searchers, that this drive is not a good fit.. perhaps you should replace the drive.

  • Increase root filesystem in ldom

    Hi
    I have a ldom   having  a  flat file  /ldoms/ldom1-data  in the backend used as a virtual disk c0d2s0  for data  In the ldom .Now this virtual disk  is running out of space  in the ldom  How can I increase the size of this filesystem in the ldom or my only option is to create another file of bigger size in the primary domian ,export it to the ldom as a new Virtual disk ,parttion it in the  ldom  and  copy the data from the old disk to the new
    Appreciate any inputs
    TIA

    Hello
    I don't think you can do with sol10u6 without any patch,  assuming that you don't have SVM just and slice
    Solaris Does Not Automatically Handle an Increase in LUN Size (Doc ID 1382180.1)
    How to expand a UFS Lun in Solaris 10 (Doc ID 1451858.1)
    And the previous doc I gave you has the example for ufs too but with sol11, so mixing a bit all this docs I think you will be able to do, but first don't forget to do a backup just in case something goes wrong.
    How to Increase the Size of a Vdisk and Filesystem on a LDom Guest Domain (Doc ID 1549604.1)
    —snip —
    Procedure to increase size of a UFS filesystem based on SMI  label in a guest domain running Solaris 11
    Another way, is add a new LUN and do a mirror to a bigger LUN then remove the small LUN. (for this you need SVM or ZFS in the guest)
    Regards
    Eze

  • Oracle ASM disk group

    Hi,
    Having a multiple Oracle ASM disk group is more beneficial for Oracle database? if no why? if yes why?
    Any metalink note if have.
    thanks

    Any metalink note do you refer?What is your database version?
    Please see these docs.
    11g ASM New Feature [ID 429098.1]
    ASM 11g New Features - How ASM Disk Resync Works. [ID 466326.1]
    Thanks,
    Hussein

  • Problems with the CS6 Master Collection disk image (invalid checksum)

    I have problems downloading the trial for CS6 Master Collection for MacOS X.
    I've tried downloading using the Download Assistant, both as a privileged and an unprivileged user, and have also tried the direct download as both privileged and unprivileged. Each time I've waited until the download was complete before trying to install, but every time the disk image fails to open, complaining of an "invalid checksum".
    I've tried mounting the disk image without validating the checksum, but while I can then run the installer, the installation fails due to lack of privileges – again, this is regardsless of user privileges. I've also tried deleting the preferences and cache-files for Download Assistant, but to no avail.
    Can anyone confirm that the english version of the CS6 Master Collecion disk image is working and can be mounted without error on MacOS X 10.7? I have now downloaded and re-downloaded the disk image at least eight times, and while I have a fast Internet-connection, this is getting tedious.

    I just downloaded the DMG from Adobe.com using the trial and it mounts fine. I was able to start the installation.
    I did not get a checksum error or any other error.
    However, I found these instructions in another thread:http://forums.adobe.com/message/4370247#4370247
    <quote>
    If the download is completed in the Adobe Download Assistant you can temporarily turn off the feature to verify the checksum.  The following steps will allow you to temporarily disable this feature:
    Open the Disk Utility located in Applications/Utilities
    Go under the Disk Utility menu and select preferences
    Deselect the option to verify checksums
    Try mounting your DMG file
    I would recommend turning this feature back on though after the installation is complete.  Also if you notice this happening on additional files it can indicate a problem with your Internet connection.
    </quote>
    Could you try these steps and let us know if you were able to proceed.

  • Full disk encryption for the Mac ?

    I desperately require a security measure against data compromise in the event of a physical theft of one of my Macs.
    Is there some full disk encryption solution, similar to the TrueCrypt solution for Windows, that can work with a Mac? (TrueCrypt works on Mac but not its feature of full disk encryption)
    Any other ideas on reinforcing security in such physical theft incidents?
    Thanks!

    Visited http://www.macintouch.com/
    PGP Corporation is now shipping PGP Desktop 9.9 for Mac OS X, a major update of the encryption software. Highlights of this release include full support for pre-boot authentication, full support for external drives (including the sharing of Whole Disk Encrypted thumb drives between Mac and Windows clients), use of the FIPS 140-2 validated PGP SDK for cryptographic operations,
    http://www.pgp.com/

  • Any way to run diagnostic (like Disk Utility) on the Time Capsule Drive?

    I have a Time Capsule with an internal drive that "needs repair", and yet I have no way of repairing it. I have a call in with AppleCare and am still awaiting their call back (2 days) as to what can be done about the drive short of erasing it, and my entire music library with it.
    7.3.1 introduced the archive feature in the disk tab and I am currently trying to do that to an external USB drive in hopes of at least saving my music library.
    But I have to think it's strange and not reassuring at best, that there is no way to check/validate the integrity of the drive. Especially since a lot of people will be using Time Capsule for more than storage of the BU's.
    Ironically enough, the archive feature strangely feels like I am backing up the backup… meaning why did I buy the 1TB Time Capsule if I still have to buy a drive to attach to it?
    Message was edited by: John Teeter

    I suggest you archive the TC drive, or alternatively copy the sparsebundle to a USB drive connected directly to your computer. Then use the erase function on the Airport Utility to re-initialize the TC drive. As long as there is not a hardware problem with the drive, initializing the drive should repair it better than any disk repair utility.
    Then copy the sparsebundle back to the TC and Bob's your uncle.
    I should warn you that my experience is that if you are copying anything large between a USB drive and TC, the USB drive should be attached to your Mac, not to the TC. I suspect if it is attached to the TC, the data flows from the TC to your Mac and then back to the USB drive attached to the TC, in effect going through your ethernet connection twice (don't even think about wireless!).
    I also suspect the archive tab in the TC is a means to transfer files directly from the TC to a connected USB drive without going through the attached compter, so it may be quite fast. However, when you tranfer back, do it with the USB drive attached to the computer.
    Message was edited by: John Strung

  • Installing OS into an LDOM without network?

    I am in the process of evaluating LDOMs at my company. I have a loaner T2000 with two disks and would like to configure 4 LDOMs, so using a whole disk is not an option. The system has limited network connectivity and no SAN. By the documentation, Jumpstart is not an option to install the OS on new LDOMs. Nor can I boot a DVD directly.
    So, I sliced my second disk into four equal partitions and gave one to each LDOM when I configured them. I thought I was ready to install... so here comes the challenging part:
    I attempted to boot a Solaris 10 11/06 DVD image file through loopback as a virtual disk. The kernel panicked almost immediately when attempting to mount the root filesystem.
    So, I used dd to extract slice 1 from the DVD and put that as a virtual disk via loopback. I booted the kernel with -a from the DVD image and specified the root filesystem as my new loopback device. This got me a running kernel and the system booted up until the point where a few services failed to start and left me in a loop where the system complained about being unable to execute sulogin, attempted to go to maintenance mode, unable to execute sulogin, etc.
    I'm starting to think that I am going about this task in the completely wrong way... but almost all the documentation I have read has suggested using a whole disk and doing a network install, which is not an option for me.
    So, going under the assumption that the only network connectivity I have is between the T2000 and some non-*nix laptop, how do I get an OS onto a LDOM?                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    Hi,
    You can make use of virtual disk images. But you'll need to setup jumpstart to get your domains running. Check out my blog at http://unixconsole.blogspot.com for details.

  • Lacie mini HD and Hub with Airport Disk

    Has anyone tried a Lacie mini HD and Hub with the Airport Disk and can you confirm whether the full features of the disk are available - i.e. the hub?

    I have a Lacie 250 drive/mini hub connected to airport. I also have a printer connected to the USB hub on the Lacie.
    I have had no problem with the drive or the printer being recognized by the AEBS. I have also had no problem with networked mac computers recognizing or accessing either the drive or the printer.
    I have NOT been able to get my one windows computer to connect to the drive. Also, the drive drops out inexplicably a lot of data is transferred, and it requires a restart of the AEBS to reconnect. On restart the macs have no problem seeing it again.
    I am trying to use it as a backup drive for a couple of computers. It is OK as long as the backups are incremental (after doing a full backup with the drive connected to the computer). If the backup is large, it won't work (today it crashed at 8 Gigs. Based on threads I have read, others are having this problem.

  • T5 with "split I/O" LDOM's

    On a brand new T5-2, the first ldom could be set up routinely. It saw four pci-buses and four disks HDA[0-1-4-5].
    I created a second LDOM, deleted the pci_2 and pci_3 buses from the primary ldom and assigned them to the new one. The primary domain now sees two disks, as expected, and continues to work fine. My issue is that the added ldom does not see any disks so I cannot install the O/S. What do I do to make the two "disappeared" disks available to the added LDOM?
    (tried to paste output from list-io here but that seems not to work??)

    found  a way finally:
    # ldm list-io
    NAME                                      TYPE   BUS      DOMAIN   STATUS
    pci_1                                     BUS    pci_1    primary
    pci_0                                     BUS    pci_0    primary
    pci_3                                     BUS    pci_3    oraprd1
    pci_2                                     BUS    pci_2    oraprd1
    /SYS/MB/PCIE5                             PCIE   pci_1    primary  EMP
    /SYS/MB/PCIE6                             PCIE   pci_1    primary  OCC
    /SYS/MB/PCIE7                             PCIE   pci_1    primary  OCC
    /SYS/MB/PCIE1                             PCIE   pci_0    primary  OCC
    /SYS/MB/SASHBA0                           PCIE   pci_0    primary  OCC
    /SYS/MB/NET0                              PCIE   pci_0    primary  OCC
    /SYS/MB/PCIE8                             PCIE   pci_3    oraprd1  UNK
    /SYS/MB/SASHBA1                           PCIE   pci_3    oraprd1  UNK
    /SYS/MB/NET2                              PCIE   pci_3    oraprd1  UNK
    /SYS/MB/PCIE2                             PCIE   pci_2    oraprd1  UNK
    /SYS/MB/PCIE3                             PCIE   pci_2    oraprd1  UNK
    /SYS/MB/PCIE4                             PCIE   pci_2    oraprd1  UNK
    /SYS/MB/PCIE6/IOVNET.PF0                  PF     pci_1    primary
    /SYS/MB/PCIE6/IOVNET.PF1                  PF     pci_1    primary
    /SYS/MB/PCIE6/IOVNET.PF2                  PF     pci_1    primary
    /SYS/MB/PCIE6/IOVNET.PF3                  PF     pci_1    primary
    /SYS/MB/PCIE7/IOVNET.PF0                  PF     pci_1    primary
    /SYS/MB/PCIE7/IOVNET.PF1                  PF     pci_1    primary
    /SYS/MB/PCIE7/IOVNET.PF2                  PF     pci_1    primary
    /SYS/MB/PCIE7/IOVNET.PF3                  PF     pci_1    primary
    /SYS/MB/NET0/IOVNET.PF0                   PF     pci_0    primary
    /SYS/MB/NET0/IOVNET.PF1                   PF     pci_0    primary

Maybe you are looking for

  • Sharing applications (Quicken) wirelessly?

    We have a new iMac with OS X Leopard, a Powerbook G4 with Mac OS X 10.4.10 and Airport Extreme, which we currently use to print wirelessly. The iMac has Quicken 2007 and currently I have to physically go to the iMac to enter my transactions. I would

  • 30 gig Video Died

    I have a new 30 gig Video iPod 1 week old, and it was working fine. I plugged it in to download some music and the compter did not see it and the screen on the iPod went dark and started to make clicking sounds, like it is spinning up. It will not re

  • Connecting JDBC to MS SQL Server 2000

    I need help! I just download a type 4 jdbc driver for MS SQL Server 2000, but i try the help files. i don't really understand how to connect. there is hostname, port but if i want to connect to the northwind database and query from customers table, h

  • Oracle Database Client -- Oracle Database in SSL mode.

    Experts, I am trying to connect to a remote oracle database which in SSL mode. I installed "Oracle database client" on other server and trying to connect to remote database in SSL mode. Can you please provide brief steps ? Do I need configure any wal

  • How to dynamic create Select SQL statements.

    Hi frnds, I want to make a SELECT statement in which all values I will get dynamically. Like i have two fields on selection screen, one for table name and one for field name. Now I need to make my ITAB according to the table selected and field name s