Need Command to set retire missing physical disks to always

what is the command to set RetireMissingPhysicalDisks policy to Always?  I can't seem to find this anywhere.  I read this should be set if no hot spare is set.
 Im not using hot spares and if a disk dies or i just pull one out and replace it with a larger one I would like it to start rebuilding.  Idealy this would work just like a drobo where i can mix and match drives and as i need more space i can purhase
it and just pull a drive out and replace it as needed with larger drives.  I like the idea of upgrading storage as needed since I dont have the budget to replace 4 or more drives at once to upgrade storage much like how you would have to do in a RAID
setup.  I have my entire storage space disks backup to a drobo anyways so i have a second location for data in case i need to change things up or for some reason two or more drives fail and i loose data.
Also, why does the action center in server 2012 r2 say check storage spaces for issues, yet when i click it and it opens storage pools everything is OK and healthy?  I see no issues and I am not sure why it tells me to check for issues.
Thanks!

Hi,
When you run the command get-storagepool, you will get (concrete) storage pools and primordial storage pools (which store physical disks that have yet to be added to a concrete storage pool).
You could refer to the article below to know more about primordial pool:
Windows Server 2012 Storage Spaces: Is it for you? Could be…
http://blogs.technet.com/b/askpfeplat/archive/2012/10/10/windows-server-2012-storage-spaces-is-it-for-you-could-be.aspx
For the second question, please provide the detailed error message in the Action Center to troubleshoot the issue.
Best Regards,
Mandy 
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

  • I am installing Adobe Creative Suite6 Design and Web Premium on a newly set up PC and received a pop-up box saying "Please inset disk AdobeDesignWebPremium6-EnglihJapan to continue". Does this mean I am missing a disk? My registration number is good--is t

    I am installing Adobe Creative Suite6 Design and Web Premium on a newly set up PC and received a pop-up box saying "Please inset disk AdobeDesignWebPremium6-EnglihJapan to continue". Does this mean I am missing a disk? My registration number is good--is there a way around this?

    Errors "Exit Code: 6," "Exit Code: 7"
    Acrobat Cleaner Tool
    Sign in or activation errors
    CS6 applications in Creative Cloud unexpectedly revert to trial mode
    Flash Player Help | Installation problems | Flash Player | Windows
    Mylenium

  • OVS 2.2 :: Unable to install RHEL HVM on physical disk from command line

    [root@ovs2 xen]# /usr/sbin/virt-install hvm name=test2 ram=1024 vcpus=1 bridge=xenbr0 file /dev/sdc --nographics
    What would you like to use for the virtual CD image? /var/ovs/mount/1FB2E6B36D21418792A1DD30B62C689F/iso_pool/rhel-server-5.6-x86_64-dvd.iso
    Starting install...
    Guest installation complete... restarting guest.
    exception was: Domain named test2 already exists!
    Domain installation may not have been
    successful. If it was, you can restart your domain
    by running 'xm create -c test2'; otherwise, please
    restart your installation.
    [root@ovs2 xen]# more test2
    # Automatically generated xen config file
    name = "test2"
    builder = "hvm"
    memory = "1024"
    disk = [ 'phy:/dev/sdc,hda,w', ]
    vif = [ 'type=ioemu, mac=00:16:3e:3d:d0:5c, bridge=xenbr0', ]
    uuid = "f99f6a07-6d03-a0ae-8f2f-a7a0e1af5e31"
    device_model = "/usr/lib/xen/bin/qemu-dm"
    kernel = "/usr/lib/xen/boot/hvmloader"
    nographic=1
    timer_mode=0
    apic=1
    acpi=1
    pae=1
    vcpus=1
    serial = "pty" # enable serial console
    on_reboot = 'restart'
    on_crash = 'restart'
    [root@ovs2 xen]# xm console test2
    xenconsole: Could not read tty from store: No such file or directory
    [root@ovs2 xen]#
    + No errors in xend.log or qemu-*.log
    + hypervisor inittab is default .. co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav
    Using similar syntax, and installing paravirtualized guest to physical disk works fine.
    [root@ovs2 xen]# /usr/sbin/virt-install paravirt name=demo3 ram=1024 vcpus=2 bridge=xenbr0 file=/dev/sdc nographics location=http://192.168.229.74/RHEL5764bit
    Starting install...
    Bootdata ok (command line is method=http://192.168.229.74/RHEL5764bit )
    Linux version 2.6.18-238.el5xen ([email protected]) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-50)) #1 SMP Sun Dec 19 14:42:02 EST 2010
    BIOS-provided physical RAM map:
    Xen: 0000000000000000 - 0000000040800000 (usable)
    No mptable found.
    Built 1 zonelists. Total pages: 264192
    Kernel command line: method=http://192.168.229.74/RHEL5764bit ...................................
    Any suggestions ??

    and i go to the temp mountpoint that the script will mount on
    Starting install...
    ERROR: Invalid NFS location given: [Errno 2] No such file or directory: '/var/lib/xen/xennfs.7x4Rf4/boot/x86_64/vmlinuz-xen'
    [root@ovs2 opt1]# df
    Filesystem 1K-blocks Used Available Use% Mounted on
    /dev/cciss/c0d0p2 3050092 3033308 0 100% /
    /dev/cciss/c0d0p1 101086 47114 48753 50% /boot
    tmpfs 288856 0 288856 0% /dev/shm
    none 288768 40 288728 1% /var/lib/xenstored
    /dev/cciss/c0d0p3 288623616 301056 288322560 1% /var/ovs/mount/A52CB661C1CF41D198D50F6379822694
    /var/isos/OracleLinux-R5-U7-Server-x86_64-dvd.iso
    3755446 3755446 0 100% /el/EL5-x86
    192.168.229.110:/el/EL5-x86
    3755456 3755456 0 100% /opt1
    192.168.229.110:/el/EL5-x86/
    3755456 3755456 0 100% /var/lib/xen/xennfs.NnE54I
    [root@ovs2 opt1]# cd /var/lib/xen/xen
    xend-db/ xennfs.7jHT0q/ xennfs.fQNnQD/ xennfs.LR6hDx/ xennfs.QnxyeH/
    xennfs.5Pr0vm/ xennfs.8aMSAA/ xennfs.fRhXiN/ xennfs.NnE54I/ xennfs.yEw4KL/
    [root@ovs2 opt1]# cd /var/lib/xen/xen
    xend-db/ xennfs.7jHT0q/ xennfs.fQNnQD/ xennfs.LR6hDx/ xennfs.QnxyeH/
    xennfs.5Pr0vm/ xennfs.8aMSAA/ xennfs.fRhXiN/ xennfs.NnE54I/ xennfs.yEw4KL/
    [root@ovs2 opt1]# cd /var/lib/xen/xennfs.NnE54I/
    [root@ovs2 xennfs.NnE54I]# ls
    blafdoc.css EULA GPL README-en RELEASE-NOTES-en.html Server VT
    Cluster eula.en_US images README-en.html RPM-GPG-KEY supportinfo
    ClusterStorage eula.py isolinux RELEASE-NOTES-en RPM-GPG-KEY-oracle TRANS.TBL
    [root@ovs2 xennfs.NnE54I]# find . -name vmlinuz\*
    ./images/pxeboot/vmlinuz
    ./images/xen/vmlinuz
    ./isolinux/vmlinuz
    [root@ovs2 xennfs.NnE54I]#

  • Which command can get physical disks information?

    Hi all,
    I need to put datafiles, controlfiles and logfiles into different disks to get better performance.
    I used "df -k" to get the disks' spaces, and I only got the filesystem information.
    I CAN NOT get physical disks information. How can I do that?
    Thanks for your help.

    I need to put datafiles, controlfiles and logfiles into different disks to get better performance.<br>If the disks are different but under the same disk controler, the result will be the same.<br>
    If you want tune, you need to know what disks are under what disk controler.<br>
    <br>
    Anyway, are you sure that you need this repartition ? Is there no other way to increase perf before to think disk repartition ?<br>
    <br>
    And to conclude, try to see in help for IBM AIX : Which physical disk is associated with your logical volume? => lslv<br>
    <br>
    Nicolas.

  • Shareable Physical Disks - Missing files

    Fairly new to FiberChannel Disks here, but we bought the FiberChannel Disk Enclosure to support Oracle VM.
    So we have 2 OVM servers, that are connected to the FC Enclosure. We have created Volumes on the FC Enclosure and those show up as Physical Disks to Oracle VM servers. I then select those Physical Disks for each guest. All seems great.
    We only have one Physical Disk that is marked as shareable and is a part of 2 "guests". In one of the guests, the disk showed up, I created a partition (only 500G) and filesystem, and then mounted the partition. On the other guest, I did not need to create the partition or filesystem as fdisk alreadys showed it was created as expected. I was able to mount the partition on the other guest as well. All files and directory seemed to be visible and are accessible.
    I just created a new file on one of the guests, but the files does not show up on the other guest. If I switch guests and do the same, shows up on the one I created but not the other.
    If I umount and then re-mount the filesystem, the files show up. On my NFS mounts, I do not have to do this.
    My question is - is there something in my configuration that I have done wrong? Is there something I need to do to have files created on one show up on the other automatically.
    Thanks for all your help and advice.
    Edited by: user897654321 on Apr 12, 2012 9:04 AM

    user897654321 wrote:
    Yes ext3 - so I guess I need to rebuild that? I will google some cluster aware filesystems available on linux, but any recommendations?OCFS2 or Oracle Cluster File System V2 is built into Oracle Linux and is mature and well-supported. Anything else would be way more complex to use. Alternatively, instead of using shared disks, use NFS or another network-based solution as you appear to have experience with this already.

  • Assigning folders and files to different physical disks OS X 10.9

    My mid 2010 iMac 27 i7 quadcore, 32 GB memory has two 1 TB SSDs and several 2 to 3 TB 7200 / 5200 SATA, Firewire, LAN and USB external HDs. I would like to direct OS X 10.9 to use frequently accessed System data/images (boot, OS X, utilities and and their attendant folders and files) from SSD 1 and frequently used / accessed applications and their attendant folders and files on the second SSD 2. (I use Microsft Office Word and Excel frequently and also Windows 7 running on VMWare.) Then I would like to keep less frequently used applications and their attendant folders and files on the SATA 7200 external disk (USB 3.0 to 2.0), photos on a fourth external disk (firewire 800), music on a NAS (Raid 1, 1000Gb Ethernet), and movies on a fifth external HD (firewire 800). What I need to know is how to "assign" these various files to a physical disk. Please, I am not looking for opinions and/or guesses. I am looking for a strategy known to work and/or utilites known do set this up easily and correctly. Thanks in advance. BTW, I am a retired OS programmer and software/HW knowlegable. I have no Unix (or of course Apple OS X) programming experience, but have written and modified many other OSs. So one can be reasonably technical with me in their answers. Thanks again, Skip.

    Hope this helps.
    1. Empty Trash.
        http://support.apple.com/kb/PH10677
    2. Start up in Safe Mode
        http://support.apple.com/kb/PH11212
    3. Delete "Recovered Messages", if any.
        Hold the option key down and click "Go" menu in the Finder menu bar.
        Select "Library" from the dropdown.
        Library > Mail > V2 > Mailboxes
        Delete "Recovered Messages", if any.
        Empty Trash. Restart.
    4. Repair Disk
        Steps 1 through 7
        http://support.apple.com/kb/PH5836
    5. Disk space / Time Machine ?/ Local Snapshots
       http://support.apple.com/kb/ht4878
    6. Re-index Macintosh HD
       System Preferences > Spotlight > Privacy
       http://support.apple.com/kb/ht2409

  • Storage Spaces - Remove Physical Disk from Simple layout

    I am running Server 2012 RTM with a single storage pool containing 4 drives - 2.73TB, 1.36TB, 465GB and 148GB. There is a single virtual disk created, with thin provisioning, using the Simple layout, with a current maximum size of 2.73TB, and with 1.32TB
    allocated. I want to remove the 148GB drive and replace it with a 465GB drive. When I right-click the 148GB disk and select Remove, I get a warning that Windows will attempt to rebuild any virtual disks that store data on the disk I'm trying to remove, and
    that in order to succeed, the storage pool must have enough free space to accommodate the data from the disk I'm trying to remove. There is more than enough space in the virtual disk to accommodate whatever files may be stored on the 148GB disk - over 1TB
    unallocated. However, when I confirm that I want to remove the disk from the pool, I get the following message:
    This physical disk is used by one or more virtual disks that use the Simple (no resiliency) layout. To remove this physical disk, delete the following virtual disks: Simple
    Surely the fact that it's a simple volume (rather than mirrored/parity) shouldn't affect the ability to move the data off the disk? It appears that disk removal is implemented as a simulated drive failure, forcing a rebuild of the resiliency data, rather
    than by simply moving the data off the disk onto other available disks.
    Additionally, after I've attempted to remove the disk, it's now been marked as 'Retired'.
    Is there any simple way to remove this disk?

    Same problem here, but I have some workaround for the problem.
    But, even in Windows Home Server with its awesome disk extender (predecessor of Storage Spaces) you had to take the shares (meaning volumes in our case) offline so you could take out the disk from the pool.
    Agree that it would make more sense to be able to remove disk from the pool online and the technology is most likely is already there: online cluster moves with defragmentation API was there for years and ReFS moves clusters online when it detects disk errors.
    Anyway here is the process that may work for you if taking volume offline is an option in your case:
    Try to remove physical disk in Server Manager - it will fail with abovementioned error, but the disk will go into "Retired" state.
    Now provision a new Virtual Disk and a volume of your choice. Most likely you will pick the same disk and volume type as you already had, but this is the chance to change the topology. You should be able to do this since you have a lot of physical disk
    space, especially if you used Thin provisioning.
    It looks like at this point retired physical disk is not included into the new Virtual Disk provisioning, but it is still accessible via existing virtual disk.
    Copy over all files from your old volume to a new volume.
    Now delete old Virtual Disk.
    If you want - change disk name and volume letter of new virtual disk that you created and new volume to what you had before.
    Now in Disk Manager take failing physical disk offline.
    Replace failing disk, initialize new disk and add it to the pool.
    Note: for me sometimes removing disk in via Storage Pool management GUI does not mark it as "Retired". In this case you can open PowerShell as Admin and assuming you want to remove PhysicalDisk2 - run the following command:
    Set-PhysicalDisk -FriendlyName PhysicalDisk2 -Usage Retired
    HTH

  • Is it possible to mount a physical disk (/dev/mapper/ disk) on one of my Oracle VM server

    I have a physical disk that I can see from multipath -ll  that shows up as such
    # multipath -ll
    3600c0ff00012f4878be35c5401000000 dm-115 HP,P2000G3 FC/iSCSI
    size=410G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=active
    | `- 7:0:0:49  sdcs 70:0   active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
      `- 10:0:0:49 sdcr 69:240 active ready running
    That particular is visible in the OVMM Gui as a physical disk that I can present to one of my VMs but currently its not presented to any of them.
    I have about 50 physical LUNs that my Oracle VM server can see.  I believe I can see all of them from a fdisk -l, but "dm-115" (which is from the multipath above) doesnt show up.
    This disk has 3 usable partitions on it, plus a Swap.
    I want to mount the 3rd partition temporarily on the OVM server itself and I receive
    # mount /dev/mapper/3600c0ff00012f4878be35c5401000000p3 /mnt
    mount: you must specify the filesystem type
    If I present the disk to a VM and then try to mount the /dev/xvdx3 partition -it of course works.  (x3 - represents the 3rd partition on what ever letter position the disk shows up as)
    Is this possible?

    Its more of the correct syntax. Like I can not seem to figure out how to translate the /dev/mapper path above into what fdisk -l shows. Perhaps if I knew how fdisk and multipath can be cross referenced I could mount the partition.
    I had already tried what you suggested. Here is the output if I present the disk to a VM and then mount the 3rd partition.
    # fdisk -l
    Disk /dev/xvdh: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/xvdh1   *           1          13      104391   83  Linux
    /dev/xvdh2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/xvdh3            2103       27783   206282632+  83  Linux
    /dev/xvdh4           27784       30394    20972857+   5  Extended
    /dev/xvdh5           27784       30394    20972826   83  Linux
    # mount /dev/xvdh3 /mnt  <-- no error
    # df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/xvda3            197G  112G   75G  60% /
    /dev/xvda5             20G 1011M   18G   6% /var
    /dev/xvda1             99M   32M   63M  34% /boot
    tmpfs                 2.0G     0  2.0G   0% /dev/shm
    /dev/xvdh3            191G   58G  124G  32% /mnt  <-- mounted just fine
    Its ext3 partition
    # df -T
    /dev/xvdh3
    ext3   199822096  60465024 129042944  32% /mnt
    Now if I go to my vm.cfg file, I can see the disk that is presented.
    My disk line contains
    disk = [...'phy:/dev/mapper/3600c0ff00012f4878be35c5401000000,xvdh,w', ...]
    Multipath shows that disk and says "dm-115" but that does not translate on fdisk
    # multipath -ll
    3600c0ff00012f4878be35c5401000000 dm-115 HP,P2000G3 FC/iSCSI
    size=410G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=active
    | `- 7:0:0:49  sdcs 70:0   active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
      `- 10:0:0:49 sdcr 69:240 active ready running
    I have around 50 disks on this server, but the ones of the same size from fdisk -l from the server shows me many.
    # fdisk -l
    Disk /dev/sdp: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdp1   *           1          13      104391   83  Linux
    /dev/sdp2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdp3            2103       27783   206282632+  83  Linux
    /dev/sdp4           27784       30394    20972857+   5  Extended
    /dev/sdp5           27784       30394    20972826   83  Linux
    Disk /dev/sdab: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdab1   *           1          13      104391   83  Linux
    /dev/sdab2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/sdab3            1319       27783   212580112+  83  Linux
    /dev/sdab4           27784       30394    20972857+   5  Extended
    /dev/sdab5           27784       30394    20972826   83  Linux
    Disk /dev/sdac: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdac1   *           1          13      104391   83  Linux
    /dev/sdac2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdac3            2103       27783   206282632+  83  Linux
    /dev/sdac4           27784       30394    20972857+   5  Extended
    /dev/sdac5           27784       30394    20972826   83  Linux
    Disk /dev/sdad: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdad1   *           1          13      104391   83  Linux
    /dev/sdad2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/sdad3            1319       27783   212580112+  83  Linux
    /dev/sdad4           27784       30394    20972857+   5  Extended
    /dev/sdad5           27784       30394    20972826   83  Linux
    Disk /dev/sdae: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdae1   *           1          13      104391   83  Linux
    /dev/sdae2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdae3            2103       27783   206282632+  83  Linux
    /dev/sdae4           27784       30394    20972857+   5  Extended
    /dev/sdae5           27784       30394    20972826   83  Linux
    Disk /dev/sdaf: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdaf1   *           1          13      104391   83  Linux
    /dev/sdaf2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdaf3            2103       27783   206282632+  83  Linux
    /dev/sdaf4           27784       30394    20972857+   5  Extended
    /dev/sdaf5           27784       30394    20972826   83  Linux
    Disk /dev/sdag: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdag1   *           1          13      104391   83  Linux
    /dev/sdag2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdag3            2103       27783   206282632+  83  Linux
    /dev/sdag4           27784       30394    20972857+   5  Extended
    /dev/sdag5           27784       30394    20972826   83  Linux
    Disk /dev/dm-13: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-13p1   *           1          13      104391   83  Linux
    /dev/dm-13p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-13p3            2103       27783   206282632+  83  Linux
    /dev/dm-13p4           27784       30394    20972857+   5  Extended
    /dev/dm-13p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-25: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-25p1   *           1          13      104391   83  Linux
    /dev/dm-25p2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/dm-25p3            1319       27783   212580112+  83  Linux
    /dev/dm-25p4           27784       30394    20972857+   5  Extended
    /dev/dm-25p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-26: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-26p1   *           1          13      104391   83  Linux
    /dev/dm-26p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-26p3            2103       27783   206282632+  83  Linux
    /dev/dm-26p4           27784       30394    20972857+   5  Extended
    /dev/dm-26p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-27: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-27p1   *           1          13      104391   83  Linux
    /dev/dm-27p2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/dm-27p3            1319       27783   212580112+  83  Linux
    /dev/dm-27p4           27784       30394    20972857+   5  Extended
    /dev/dm-27p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-28: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-28p1   *           1          13      104391   83  Linux
    /dev/dm-28p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-28p3            2103       27783   206282632+  83  Linux
    /dev/dm-28p4           27784       30394    20972857+   5  Extended
    /dev/dm-28p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-29: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-29p1   *           1          13      104391   83  Linux
    /dev/dm-29p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-29p3            2103       27783   206282632+  83  Linux
    /dev/dm-29p4           27784       30394    20972857+   5  Extended
    /dev/dm-29p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-30: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-30p1   *           1          13      104391   83  Linux
    /dev/dm-30p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-30p3            2103       27783   206282632+  83  Linux
    /dev/dm-30p4           27784       30394    20972857+   5  Extended
    /dev/dm-30p5           27784       30394    20972826   83  Linux
    How to translate the /dev/mapper address into the correct fdisk, I think I can then mount it.
    If I try the same command as before with the -t option it gives me this error.
    # mount -t ext3 /dev/mapper/3600c0ff00012f48791975b5401000000p3 /mnt
    mount: special device /dev/mapper/3600c0ff00012f48791975b5401000000p3 does not exist
    I know I am close here, and feel it should be possible, I am just missing something.
    Thanks for any help

  • Need to separate drive alerts with Logical Disk Free Space monitoring in SCOM 2012

    I have an interesting need here to separate our SCOM alerts for Logical Disk Free space so that one alert is for OSSystem drives ONLY (C:/D:) and the other monitor alerts on all APP drives only (E:, etc). So far we have had great success using Kevin Holman's
    blog post.
    http://blogs.technet.com/b/kevinholman/archive/2009/11/24/writing-monitors-to-target-logical-or-physical-disks.aspx
    We have overrides set so that the monitors report ONLY the percentage of free space left and ignores any MB threshold. So far so good, the alert comes in that host A reports low disk space on D: at 2.345...% free or host B reports low disk space on F: at
    4.567...% free space etc. Now that we have our monitors working within the Windows Server classes Logical Disk, we need to set these monitors so that one is just for C or D drives with the alert named system Logical Disk Free Space OS Disk Warn and the other
    monitor just reports on E - Z drives (excluding C or D) with the alert named Logical Disk Free Space APP Disk Warn.
    We are very new to SCOM so I made the rookie mistake of creating a dynamic group for all Windows Server 2003 Logical Disk class that only includes Device Name = C or D. But found out too late you cant point a monitor to a group, it has to target a class.
    And using the current monitors we set up with the above blog uses the correct logical disk class, but it doesnt care what instance (device Id = value), it will report low disk space on ANY logical drive. How in the world can we separate and exclude these monitors
    so that one alerts only on OS disks (C and D) and the other only alerts on app disks (E through Z)?

    Hi Kevsharp,
    Quite confusing after reading your question.
    So based on your requirement, What i understand is you need separate alerts for all the drives of the disk is running at low or out of space right ?
    For the above just create a simple performance counter monitor and use the same counters as kevin has used in his blog.
    Now Target: Use Windows server operating system (This will target all the Windows operating system agents in your SCOM. If the specified discovery MP's are installed).
    Set a threshold Below 10% is critical or what ever. You will get the alerts in your console.
    Gautam.75801

  • How to determine physical disk size on solaris

    I would like to know whether there is a simple method available for determining physical hard disk sizes on Sun sparc machines. On HP based machines it is simple:
    1. run "ioscan -fnC disk" - to find all disk devices and there raw device target address ie /dev/rdsk/c0t2d2
    2. run "diskinfo /dev/rdsk/c0t2d2" - display the attributes of the physical disk including size in Kbyes.
    This simple process allows me create simple scripts that I can use to automate collation of audit data for a large number of HP machines.
    On Sun based machines I've looked at the prtvtoc, format, and devinfo commands and have had no joy. Methods and suggestion will be well appriciated.

    ok,
    format should say .....eg
    type format ..
    AVAILABLE DISK SELECTIONS:
    0. c0t0d0 <SUN2.1G cyl 2733 alt 2 hd 19 sec 80>
    if this is not a Sun disk, and you do not get the info,
    select the required disk and select partition and then print. This will display what you need.
    hope this helps

  • Setting up a physical standby on a server with a different structure

    I am having a few issues trying to set up a physical standby database.
    The primary database has a different naming structure than the standby and they are at different sites.
    Physical is /var/hpsrp/ctrorp03/oradata/u0x/<DB_NAME>/<DB_UNIQUE_NAME> and standby is /var/hpsrp/drforp03/oradata/u0x/<DB_NAME>/<DB_UNIQUE_NAME>.
    I have set db_file_name_convert to '<PRIMARY PATH>', '<STANDBY PATH>' times the number of paths as pairs.
    I have created a blank database for standby and having taken a full backup of primary with control file and standby control file.
    Now I hit the issues:
    The DB incarnation numbers are different.
    When I try and do a normal restore e.g. set dbid, restore controlfile; mount; it fails as it is trying to find files in the primary structure and not standby structure.
    When I try renaming via set newname or auxname it can't find files to restore I guess due to the incarnation id's.
    If I set the incarnation id and try to restore backup it fails as the incarnation id's don't match.
    I have tried looking through various forums and the documentation but can't find a solution, probably can't see the wood for the trees though as there is so much.
    Has anyone done this type of setup before and can give me some advice?

    Thanks for you replies I will try and give more information on both.
    srsatya :- Version is 11.2 the controlfile I tried to restore was the one created by the backup not the standby should I be putting the standby in place then before I do the restore? If so just a replacement for the current controlfile by carefully replace at an OS level or by mimicing the controlfile to be restored from autobackup?
    CKPT:- Think I tried that but I have been going around in so many circles may have mucked something up.
    RMAN> set dbid=2261148474 (The PRIMARY Incarnation number)
    executing command: SET DBID
    RMAN> alter database mount;
    using target database control file instead of recovery catalog
    database mounted
    RMAN> run
    2> { 
    3> allocate channel c1 device type disk;
    4> SET NEWNAME FOR DATAFILE 1 TO '/var/hpsrp/drforp03/oradata/u01/SAPDS/DRFSAPDS/system01.dbf';
    5> SET NEWNAME FOR DATAFILE 2 TO '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf';
    6> SET NEWNAME FOR DATAFILE 3 TO '/var/hpsrp/drforp03/oradata/u01/SAPDS/DRFSAPDS/undotbs01.dbf';
    7> SET NEWNAME FOR DATAFILE 4 TO '/var/hpsrp/drforp03/oradata/u01/SAPDS/DRFSAPDS/users01.dbf';
    8> SET NEWNAME FOR DATAFILE 5 TO '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/IPSCMS01.dbf';
    9> SET NEWNAME FOR DATAFILE 6 TO '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/IPSA01.dbf';
    10> SET NEWNAME FOR DATAFILE 7 TO '/var/hpsrp/drforp03/oradata/u02/SAPDS/DRFSAPDS/DSCR01.dbf';
    11> SET NEWNAME FOR DATAFILE 8 TO '/var/hpsrp/drforp03/oradata/u03/SAPDS/DRFSAPDS/ISCR01.dbf';
    12> SET NEWNAME FOR DATAFILE 9 TO '/var/hpsrp/ctrorp03/oradata/u05/SAPDS/CTRSAPDS/DSLR_DEV01.dbf';
    13> SET NEWNAME FOR DATAFILE 10 TO '/var/hpsrp/ctrorp03/oradata/u05/SAPDS/CTRSAPDS/undotbs02.dbf';
    14>
    15> RESTORE DATABASE;
    16> SWITCH DATAFILE ALL;
    17> RECOVER DATABASE;
    18> }
    allocated channel: c1
    channel c1: SID=165 device type=DISK
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 28-JUN-12
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 06/28/2012 10:21:13
    RMAN-06189: current DBID 2261148474 does not match target mounted database (2261834728)
    RMAN> exit
    Recovery Manager complete.
    drfora04 ora_srp3 $ rman
    Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jun 28 10:22:16 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    RMAN> connect target /
    connected to target database: SAPDS (DBID=2261834728, not open)
    RMAN> run
    2> { 
    3> allocate channel c1 device type disk;
    4> SET NEWNAME FOR DATAFILE 1 TO '/var/hpsrp/drforp03/oradata/u01/SAPDS/DRFSAPDS/system01.dbf';
    5> SET NEWNAME FOR DATAFILE 2 TO '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf';
    6> SET NEWNAME FOR DATAFILE 3 TO '/var/hpsrp/drforp03/oradata/u01/SAPDS/DRFSAPDS/undotbs01.dbf';
    7> SET NEWNAME FOR DATAFILE 4 TO '/var/hpsrp/drforp03/oradata/u01/SAPDS/DRFSAPDS/users01.dbf';
    8> SET NEWNAME FOR DATAFILE 5 TO '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/IPSCMS01.dbf';
    9> SET NEWNAME FOR DATAFILE 6 TO '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/IPSA01.dbf';
    10> SET NEWNAME FOR DATAFILE 7 TO '/var/hpsrp/drforp03/oradata/u02/SAPDS/DRFSAPDS/DSCR01.dbf';
    11> SET NEWNAME FOR DATAFILE 8 TO '/var/hpsrp/drforp03/oradata/u03/SAPDS/DRFSAPDS/ISCR01.dbf';
    12> SET NEWNAME FOR DATAFILE 9 TO '/var/hpsrp/ctrorp03/oradata/u05/SAPDS/CTRSAPDS/DSLR_DEV01.dbf';
    13> SET NEWNAME FOR DATAFILE 10 TO '/var/hpsrp/ctrorp03/oradata/u05/SAPDS/CTRSAPDS/undotbs02.dbf';
    14>
    15> RESTORE DATABASE;
    16> SWITCH DATAFILE ALL;
    17> RECOVER DATABASE;
    18> }
    using target database control file instead of recovery catalog
    allocated channel: c1
    channel c1: SID=165 device type=DISK
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 28-JUN-12
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 06/28/2012 10:22:26
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 2 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    RMAN>
    Edited by: gzmzpz on 28-Jun-2012 04:56

  • Harddisk suddenly missing in Disk Utility

    Hi,
    My 2nd hard drive is missing in Disk Utility. It doesn't show in Finder either.
    System profile is the only place where I can see the physical drive, but no partitions are displayed. It only shows this:
    WDC WD5000KS-00MNB0:
    Model: WDC WD5000KS-00MNB0
    Revisie: 07.02E07
    Serienummer: WD-WCAN**262
    Native Command Queuing: Ja
    Queue Depth: 32
    Externe eenheid: Nee
    Whereas for my ROOT drive it says this (including the partition)
    WDC WD2500JS-41SGB0:
    Capaciteit: 232,89 GB
    Model: WDC WD2500JS-41SGB0
    Revisie: 20.06C04
    Serienummer: WD-WCAN**092
    Native Command Queuing: Ja
    Queue Depth: 32
    Verwisselbare media: Nee
    Externe eenheid: Nee
    BSD-naam: disk0
    Naam nis: "Bay 1"
    Mac OS 9-besturingsbestanden: Nee
    Type partitie-indeling: GPT (GUID-partitietabel)
    S.M.A.R.T.-status: Gecontroleerd
    Volumes:
    Macintosh HD:
    Capaciteit: 211,88 GB
    Beschikbaar: 21,48 GB
    Beschrijfbaar: Ja
    Bestandssysteem: Journaled HFS+
    BSD-naam: disk0s2
    Activeringspunt: /
    Furthermore I cannot shutdown my system with this particular internal drive connected. It hangs after a few seconds. With a hard reset using the power button, I removed the whole 2nd drive bay and after a restart leopard shuts down as normal. Since I cannot see the drive in Disk Utility, how am I able to repair it? Any help would be really appreciated. Thanks.
    <Edited by Host>

    Try Disk Warrior (you'll want to have a system for just maintenance and repairs only); or Drive Genius 2; or TechTool Pro.
    The directory and journaling could be so corrupt for various reasons it can't be mounted. Bad sector.
    Other than anything not backed up I'd RMA or zero, but I'd also invest in replacing with a new model.

  • Scripting the Removal of Physical disk from VM

    Hi all
    I have read this thread here which has helped me so far to create a script for the removal of a VM Hard Disk Drive
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/7f00687c-aa8b-4125-a10c-2730ee473e78/auto-add-remove-physical-disk-from-hyperv-vms?forum=winserverhyperv
    So far the script I have knocked up is as follows:
    Remove
    PS C:\Users\Administrator> remove-vmhardDiskDrive -VMName 2012r2 -ControllerType SCSI -ControllerNumber 0 -ControllerLocation 0
    Re-add
    PS C:\Users\Administrator> add-vmhardDiskDrive -VMName 2012r2 -ControllerType SCSI -ControllerNumber 0 -ControllerLocation 0
    This gets me this in the Hyper-V settings:
    I need the script to add the VM Hard Disk drive in with the physical hard disk selected automatically.
    Is there a way to do this?
    As you can see I am not a powershell expert, im not even an "expert"
    Thanks - Dan 

    All done
    The script I used for the removal and then re-adding of the physical disk is as follows:
    remove-vmhardDiskDrive-VMName2012r2-ControllerTypeSCSI-ControllerNumber0-ControllerLocation0
    Add-VMHardDiskDrive-VMName2012R2-ControllerTypeSCSI-ControllerNumber0-DiskNumber1-Passthru
    I then automated it with task scheduler to trigger at 6pm everyday (30 minutes after rotation time)
    The ISCSI controller type allows you to run the command whilst the VM is on.

  • OVM 2.2 -- using physical disk during initial install (virt-install)

    I am trying to create a paravirtualized RHEL564bit vm using the virt-install command. Instead of using file based image or tapblk driver based image, i want to use a physical disk.
    The physical disk is available to the OVS server and formatted : /dev/sdb1
    The disk directive is missing from the virt-install (only file option is present). How do i get the install started?
    bin/virt-install paravirt name=demo ram=1024 vcpus=2 bridge=xenbr0 disk path=/dev/sdb1,driver=phy vnc noautoconsole nographics location=http://192.168.229.74/RHEL5764bit
    <--disk path is not a valid option> .. I tried using --file but it does not work
    *** Basically my vm.cfg's disk directive should look like this :
    bootloader = '/usr/bin/pygrub'
    disk = ['phy:/dev/sdb,xvda,w!’]
    OR .... if you can tell me how to convert a file based image (System.img) to the phy: that would be great.
    Note : This is a recommendation for Oracle RAC installation and in addition to the ASM disks being physical, i want the OS disk to be physical as well (and not use any driver or image based file)
    Edited by: Abhijit on Nov 30, 2011 8:53 AM

    Ok - so confirmed. disk directive is not present .. You can pretty much use the file parameter to specify a physical device path. Infact i tried that, but i missed the = sign.
    So the command syntax should look like :
    /usr/sbin/virt-install paravirt name=demo2 ram=1024 vcpus=2 bridge=xenbr0 file=/dev/sdb nographics location=http://192.168.229.74/RHEL5764bit

  • Rac installation on AIX with physical disks.

    we have aix 6.1 server (2 lpar/vio) and I am planning to install oracle RAC 11GR2.  We do not have storage so need to use available physical disks.
    Is it possible to create RAC with phisical disks.  We do not have Aix administrator so please Guide me by step by step commands.
    We need RAC with ASM.

    Hi user;
    Please check below notes and links:
    IBM General Parallel File System (GPFS) and Oracle RAC [ID 302806.1]
    RAC Assurance Support Team: RAC Starter Kit and Best Practices (AIX) [ID 811293.1]
    RAC: Frequently Asked Questions [ID 220970.1]
    I also suggest check below googling which has very great notes:
    http://www.google.com.tr/search?hl=tr&source=hp&q=RAC+on+AIX&aq=f&aqi=&aql=&oq=&gs_rfai=
    Regard
    Helios

Maybe you are looking for