Add Physical Disk to VM

Hyper-V 2012 R2. We have a SE3016 JBOD devices that hooked up to the physical server via SAS 6mbps HBA. On the physical server (2012 r2 core), diskpart lists the disk as offline. In hyper-v manager in the settings of the VM, i have added the hard drive via
scsi:
As you can see, the physical drive shows up in the settings. However, when i go into computer management of the VM, the drive is not listed there. The lights for the drive in the JBOD device is light-up and does not show any erros. I have rebooted the server
and JBOD device. Still no drive in computer management of the VM.
Am i doing this process right to get the VM to see the drive?

Hi Sir,
Unfortunately there is no JBOD at hand in my lab for reproduce this .
As I know , to take full advantage of JBOD you may try to use storage pool to create virtual disk then pass-through to VMs or store VM's vhd file :
http://blogs.technet.com/b/keithmayer/archive/2012/10/06/optimize-it-budgets-with-storage-spaces-in-windows-server-2012-31-days-of-favorite-features-part-6-of-31.aspx
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Similar Messages

Storage Pool - Add Physical Disk Window Empty

I have a storage space configured with 5 physical drives on a clustered pair of servers. The drives themselves are MPIO iSCSI targets that are attached to each server. When I try to add an additional drive to the pool, the window to add the drives is blank.
I know the drives will work in a storage pool because I've tested creating the pool with all drives from scratch.
Any idea why this window would be blank? (FYI, the error isn't related to the pool, its a server I need to remove from the all servers list)

Hi Delocx,
Please check whether the new added disk can display in disk management. If so, is there any volume created on the disk? It should be an unallowcated disk.
In addition, you can also run the windows powershell cmdlet Get-PhysicalDisk
to check the status of "can pool" is ture or false.
I hope this helps.

How do I add three disks to a server?

How can i add 3 Physical disk to a server

Can you provide more details on this ?
Refer : https://support.microsoft.com/en-gb/kb/555375?wa=wsignin1.0
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Cannot add cluster disk on windows 2012

I have 2 servers connected to a shared storage array using Fibre Channel. Currently there are 2 luns on the storage device.
From the Failover Cluster Manager, when I select “Add Disk” from Storage – Disks, both luns show up and I can add them without problems. But if I choose to only
add one of them first (it doesn't make a difference which one is added first), then it will not allow adding the second one later. I get a message: "No disks suitable for cluster disks were found. For diagnostic information about disks available to the
cluster, use Validate a Configuration Wizard to run Storage tests."
When I do add one (or both disks at the same time), they work just fine for failover clustering.
I can’t imagine this is by design. Is this a known/unknown issue, or is there something special that needs to be done?
Thanks

Ok, no problem. I run the validation tests (Validate Cluster - Storage only) and I received the details shown below. I can clearly see that Cluster Validation tool does not find any disk suitable for 2012 cluster, and even I can see why (it is plain English).
Unfortunately this still does not explain how to fix the problem. Recommendations like "run Clear-ClusterDiskReservation PowerShell cmdlet to remove the Persistent Reservation from the disk" do not work - this discussion is available in another thread where
people having the same issue and no luck so far. I guess that I'm using old SAN (and I know that) that simply does not support SCSI-3 persistent reservation so those disks cannot be used in 2012 cluster. Oh well, will have to wait fro new SAN and then I can
play again...
Validation test results:
Physical disk with identifier {95059d50-a173-49bd-b029-fec326acd78c} has an existing Persistent Reservation placed on it, and will be removed from the validation set. This disk may already be clustered, on a different cluster or in use by another system.
Please verify the storage configuration and LUN zoning. If you wish to cluster this disk, you can use the Clear-ClusterDiskReservation PowerShell cmdlet to remove the Persistent Reservation from the disk.
Physical disk with identifier {0b301c72-c88f-47ee-9389-11efdeed6cdb} has an existing Persistent Reservation placed on it, and will be removed from the validation set. This disk may already be clustered, on a different cluster or in use by another system.
Please verify the storage configuration and LUN zoning. If you wish to cluster this disk, you can use the Clear-ClusterDiskReservation PowerShell cmdlet to remove the Persistent Reservation from the disk.
Physical disk with identifier {eec0be37-5dfe-47f7-a149-4f1dec18450b} has an existing Persistent Reservation placed on it, and will be removed from the validation set. This disk may already be clustered, on a different cluster or in use by another system.
Please verify the storage configuration and LUN zoning. If you wish to cluster this disk, you can use the Clear-ClusterDiskReservation PowerShell cmdlet to remove the Persistent Reservation from the disk.
Physical disk with identifier {dcb8b1fe-7671-41c9-b996-da26c0b93751} has an existing Persistent Reservation placed on it, and will be removed from the validation set. This disk may already be clustered, on a different cluster or in use by another system.
Please verify the storage configuration and LUN zoning. If you wish to cluster this disk, you can use the Clear-ClusterDiskReservation PowerShell cmdlet to remove the Persistent Reservation from the disk.
No disks were found on which to perform cluster validation tests. To correct this, review the following possible causes:
* The disks are already clustered and currently Online in the cluster. When testing a working cluster, ensure that the disks that you want to test are Offline in the cluster.
* The disks are unsuitable for clustering. Boot volumes, system volumes, disks used for paging or dump files, etc., are examples of disks unsuitable for clustering.
* Review the "List Disks" test. Ensure that the disks you want to test are unmasked, that is, your masking or zoning does not prevent access to the disks. If the disks seem to be unmasked or zoned correctly but could not be tested, try restarting the servers
before running the validation tests again.
* The cluster does not use shared storage. A cluster must use a hardware solution based either on shared storage or on replication between nodes. If your solution is based on replication between nodes, you do not need to rerun Storage tests. Instead, work
with the provider of your replication solution to ensure that replicated copies of the cluster configuration database can be maintained across the nodes.
* The disks are Online in the cluster and are in maintenance mode. No disks were found on which to perform cluster validation tests.

Disks not avialable and cannot add new disks to existing pools

I have a few disks that are RAW and I want to add them to existing pools. However, only 1 disk shows up as a Primordial disk and the others do not. I cannot add these drives to a new volume and when I try to add any drive to an existing
pool, the add disk option is greyed out. I have search everywhere to resolve this but no luck.
What is interesting is one of the drives that shows available for a volume is the drive I have associated to backing up the OS on the server itself and is initialized, i.e. not RAW.

Hi,
Please try to run the following commands in PowerShell to obtain the information about disks:
Get-physicaldisk
Get-disk
In additional, the physical disk added to a storage pool must be 4GB or larger. If the space is less 4GB, the disk will not appear in the storage pool window.
For more information, please refer to the thread below:
Storage Pool in WS2012
http://social.technet.microsoft.com/Forums/windowsserver/en-US/d230ef80-8791-4eaf-84b5-a41b8f7fef10/storage-pool-in-ws2012?forum=winserver8gen
Best Regards,
Mandy
If you have any feedback on our support, please click
here .
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.

How to tell what physical disk is an ASM volume?

Hello all,
I'm trying to install some clusterware. I have attached, a SAN unit, that was previously used for ASM.
After I installed the ASM libs/drivers...I ran oracleasm scandisks, and it found all of them.
I have ASM1,ASM2....ASMn
I thought, "great"..saves me time having to go through, find each disk device and configure them. I don't mind losing data on them.
I'm in the middle of the OUI for cluster install (11Gr2 on RHEL5)...and on the ASM portion (getting ready to create a disk group for the cluster for voting disk, etc)...well, under candidate disks...it shows nothing.
If I click the all disks option..it shows all my oracle volumes...but their status is 'member'. It will not allow me to add them to my to be new disk group.
I'm not sure what to do.
One problem...is that I can't seem to find a way to find out what physical disk device is associated with each ASM disk.
For instance:
oracleasm querydisk ASM33
Disk "ASM33" is a valid ASM disk
It just shows it's a valid disk...but if I wanted to release it, reconfigure it..etc, I don't know what physical disk it is, and I'd like to use the same layout that was used before.
Is there a way to find out what disk (example: /dev/sda12) is associated with ASM33?
I don't see any options listed for this in the man page for oracleasm, and I can't seem to find much documentation for this either...
Thanks in advance,
cayenne

Well for this you can use oracleasm querydisk.Using this you can identify which device as marked for asm or not. for example you can see this below example.
[oracle@localhost init.d]$ sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.4.0 - Production on Thu Jun 3 11:52:12 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select path from v$asm_disk;
PATH
/dev/oracleasm/disks/VOL2
/dev/oracleasm/disks/VOL1
SQL> exit;
[oracle@localhost init.d]$ su
Password:
[root@localhost init.d]# /sbin/fdisk -l
Disk /dev/sda: 80.0 GB, 80000000000 bytes
255 heads, 63 sectors/track, 9726 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot      Start         End      Blocks   Id System
/dev/sda1   *           1        1305    10482381   83 Linux
/dev/sda2            1306        9401    65031120   83 Linux
/dev/sda3            9402        9662     2096482+ 82 Linux swap / Solaris
/dev/sda4            9663        9726      514080    5 Extended
/dev/sda5            9663        9726      514048+ 83 Linux
Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
   Device Boot      Start         End      Blocks   Id System
/dev/sdb1               1        4859    39029886   83 Linux
/dev/sdb2            4860        9729    39118275   83 Linux
[root@localhost init.d]# ./oracleasm querydisk /dev/sdb1
Device "/dev/sdb1" is marked an ASM disk with the label "VOL1"
[root@localhost init.d]# ./oracleasm querydisk /dev/sdb2
Device "/dev/sdb2" is marked an ASM disk with the label "VOL2"
[root@localhost init.d]# ./oracleasm querydisk /dev/sda1
Device "/dev/sda1" is not marked as an ASM disk
[root@localhost init.d]#Also in windows :
C:\Documents and Settings\comp>asmtool -list
NTFS                             \Device\Harddisk0\Partition1           140655M
ORCLDISKDATA1                    \Device\Harddisk0\Partition2             4102M
ORCLDISKDATA2                    \Device\Harddisk0\Partition3             4102M
NTFS                             \Device\Harddisk0\Partition4           152617M
C:\Documents and Settings\comp>answered by chinar in thread:how to identify which rawdevice Disk Is named as VOL1 IN ASM from os level

Physical Disk

Hi,
I am unable view my Physical Disk in my VM Manager console , can any help me solve the problem.
I am using HP ProLiant BL460c G6 Blade Server

Hello.. I've tried multiple times too, to get the local disks to be discovered, but having no luck.
Hardware.. IBM x346 server.. 2 x 73gb drives (mirror)... 4 x 146gb drives (raid 5).
Install OVM Server 3.0.3 server and it installs to /dev/sba no problem... It trys to install the / to the /dev/sdb, but I remove it and put it back on /dev/sba, so that nothing but Free Space is showing for /dev/sdb.
After it's all installed/rebooted, etc.. I go to the OVM Mgr (3.0.3 build 240) server and discover the new box.
It sees the oelvmibm02 server. I'm able to add it to the ibm-pool, and when I discover Physical Disks.. nothing shows.
I've ensured that iptables is OFF for the vm mgr server.
I've looked at the multipathd service on VM Svr.. it's running.
However, when I issue the command multipath -ll
here is what I get:
DM multipath kernel driver not loaded
I've reinstalled OVM Svr 3.0.3 multiple times on this box, with different configuration trying to get it to recognize the 2nd array so I can have a repository, but nothing seems to work.
Any ideas on what to try next? I'm all open for suggestions.

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.

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

Physical disk for OS and read only filesystem after live migration

I am running OVM 3.1.1 connected to an EMC storage array. I have a situation where physical disks are being used for OS and binary filesystems (i.e. /u01, etc..) rather than virtual disks inside a repository. When a VM is migrated from one host to another, I sometimes get a message stating the size of the disk changed and shortly afterwards the filesystem is changed to read only and I have to reboot to fix the problem. Is this an unsupported configuration or do I have potential problems with my LUN mapping? Has anyone seen this problem before?

I am running OVM 3.1.1 connected to an EMC storage array. I have a situation where physical disks are being used for OS and binary filesystems (i.e. /u01, etc..) rather than virtual disks inside a repository. When a VM is migrated from one host to another, I sometimes get a message stating the size of the disk changed and shortly afterwards the filesystem is changed to read only and I have to reboot to fix the problem. Is this an unsupported configuration or do I have potential problems with my LUN mapping? Has anyone seen this problem before?

What is the difference between Logical Disk and Physical Disk?

Hi.
When I do Performance Monitor, I got Logical Disk Avg. Disk sec/Write counter and Physical Disk Avg. Disk sec/Write counter.
But I can see the different Avg. value and Max. value.
Even if Logical and Physical Disk are one-to-one mapping.
Why did i get the result?
One the other hands, I got a same result that Logical Disk Avg. Disk sec/Read counter and Physical Disk Avg. Disk sec/Read counter's Avg. value and Max. value.

Physical Disk refers to an actual physical HDD (or array in a hardware RAID setup), whereas Logical Disk refers to a Volume that has been created on that disk.
So if you have one disk with one volume created on it then the values are likely to be 1 to 1, but if you have multiple volumes on the disk, for instance a physical disk with C:\ and D:\ volumes running on it, then the logical disks relate to c:\ and d:\
rather than the disk they're running on.
See
http://blogs.technet.com/b/askcore/archive/2012/03/16/windows-performance-monitor-disk-counters-explained.aspx for a more in depth explanation.

Physical disk not showing up in Disk Utility

I'm in the process of selling my mac mini.
I went to the disk utility and erased per the instructions here:
http://support.apple.com/en-us/HT201065
The only thing I did differently was I adjusted the security settings to do a pass of writing zeroes.
Then I went to reinstall OS X per the instructions and there was no drive available on the "select the disk where you want to install os x" screen.
I tried to do a restore from backup and got the same symptom - no disk to restore to. Also doesn't show when I go to choose a startup disk.
I went back to the Disk Utility and noticed some weirdness:
- The Macintosh HD logical volume is showing in the upper left, but there's no physical disk showing as its parent! See attached screenshot - I can repair and verify the logical volume without any problems. It also says that the volume is online and has 1.1 TB as it should.
I've also tried resetting the NVRAM and PRAM, with no luck
Any help is much appreciated!!!

Hi PabloHoney1979,
When I check my Mac I see the same Macintosh HD, Logical Volume Group with an indented partition under it. So it looks like you are looking at the physical disk without a partition on it. Try the Partition tab and create a partition on the drive.
Disk Utility 12.x: Partition a disk
3. In the Mac OS X Utilities window, select Disk Utility, and then click Continue.
4. Select the disk that you want to partition and click Partition.
5. Choose the number of partitions from the Volume Scheme pop-up menu.
6. Click each partition and type a name for it, choose a format, and type a size. You can also drag the divider between the partitions to change their sizes. If a partition’s name has an asterisk beside it, it’s shown larger than its actual size in order to display its name clearly.
7. If you’ll be using a partition as a Mac OS X startup disk, click Options, and choose the the GUID partition scheme.
8. Click Apply.
Take care,
Nubz

Can't create a repository with a local physical disk

Hi,
I'm using Oracle VM Manager 3.0.3.
I created a non clustered server pool with one server. That server has 2 identical SATA 500GB internal drives and 1 eSATA 750GB drive in AHCI mode. The 750G eSATA drive is the primary boot drive and hosts the MBR with Windows 7. One of the 500GB SATA internal drive hosts Oracle VM Server. The other 500GB SATA drive has no partition and I want to use it as a local OVM repository. When I boot the server I can select to boot Windows 7 or Oracle VM Server with no issue.
After the OVM server boots, OVM Manager 3.0.3 can discover it along with 2 physical disks: the 500GB SATA internal drive (SATA_WDC_WD5000BEKT-_WD-WX41A11X1750) I want to use as a repository and the eSATA 750GB drive. OVM Manager reports these physical disks as SAN type with no file system.
When I create my local repository for the server pool, I select the physical disk SATA_WDC_WD5000BEKT-_WD-WX41A11X1750 and click the "Next" button. But the job always fails with the following details:
Job Construction Phase
begin()
Appended operation 'File System Construct' to object '0004fb0000090000865c3f26b528bc39 (Local FS OracleVS01)'.
Appended operation 'Repository Construct' to object '0004fb0000030000182872191a913bac (SATA_WDC_WD5000BEKT-_WD-WX41A11X1750)'.
commit()
Completed Step: COMMIT
Objects and Operations
Object (IN_USE): [LocalFileServer] 0004fb0000090000865c3f26b528bc39 (Local FS OracleVS01)
Operation: File System Construct
Object (CREATED): [LocalFileSystem] 0004fb0000050000f36710bdcca530d4 (fs_MyLocalRepository)
Object (CREATED): [Repository] 0004fb0000030000182872191a913bac (MyLocalRepository)
Operation: Repository Construct
Object (IN_USE): [StorageElement] 0004fb00001800004e793d6f05fced03 (SATA_WDC_WD5000BEKT-_WD-WX41A11X1750)
Job Running Phase at 12:18 on Tue, Jan 31, 2012
Job Participants: [00:25:22:dc:0a:ee:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff (OracleVS01)]
Actioner
Starting operation 'File System Construct' on object '0004fb0000050000f36710bdcca530d4 (fs_MyLocalRepository)'
Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_B000E Storage plugin command [storage_plugin_createFileSystem] failed for storage server [0004fb0000090000865c3f26b528bc39] failed with [com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_createFileSystem to server: OracleVS01 failed. OVMAPI_4004E Server Failed Command: storage_plugin_createFileSystem oracle.ocfs2.OCFS2.OCFS2Plugin 0004fb0000050000f36710bdcca530d4 /dev/mapper/SATA_WDC_WD5000BEKT-_WD-WX41A11X1750, Status: OSCPlugin.FileSystemBusyEx:'An ocfs2 filesystem already exists on /dev/mapper/SATA_WDC_WD5000BEKT-_WD-WX41A11X1750'
Tue Jan 31 12:18:46 CST 2012
Tue Jan 31 12:18:46 CST 2012] OVMAPI_4010E Attempt to send command: storage_plugin_createFileSystem to server: OracleVS01 failed. OVMAPI_4004E Server Failed Command: storage_plugin_createFileSystem oracle.ocfs2.OCFS2.OCFS2Plugin 0004fb0000050000f36710bdcca530d4 /dev/mapper/SATA_WDC_WD5000BEKT-WD-WX41A11X1750, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.FileSystemBusyEx:'An ocfs2 filesystem already exists on /dev/mapper/SATAWDC_WD5000BEKT-_WD-WX41A11X1750'
Tue Jan 31 12:18:46 CST 2012
Tue Jan 31 12:18:46 CST 2012
Tue Jan 31 12:18:46 CST 2012
at com.oracle.ovm.mgr.action.StoragePluginAction.processException(StoragePluginAction.java:1325)
at com.oracle.ovm.mgr.action.StoragePluginAction.createFileSystem(StoragePluginAction.java:868)
at com.oracle.ovm.mgr.op.physical.storage.FileSystemConstruct.createFileSystem(FileSystemConstruct.java:57)
at com.oracle.ovm.mgr.op.physical.storage.FileSystemConstruct.action(FileSystemConstruct.java:49)
at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:193)
at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:264)
at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1090)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:247)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:207)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_createFileSystem to server: OracleVS01 failed. OVMAPI_4004E Server Failed Command: storage_plugin_createFileSystem oracle.ocfs2.OCFS2.OCFS2Plugin 0004fb0000050000f36710bdcca530d4 /dev/mapper/SATA_WDC_WD5000BEKT-WD-WX41A11X1750, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.FileSystemBusyEx:'An ocfs2 filesystem already exists on /dev/mapper/SATAWDC_WD5000BEKT-_WD-WX41A11X1750'
Tue Jan 31 12:18:46 CST 2012
Tue Jan 31 12:18:46 CST 2012
at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:475)
at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:427)
at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:369)
at com.oracle.ovm.mgr.action.StoragePluginAction.createFileSystem(StoragePluginAction.java:864)
... 18 more
Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: storage_plugin_createFileSystem oracle.ocfs2.OCFS2.OCFS2Plugin 0004fb0000050000f36710bdcca530d4 /dev/mapper/SATA_WDC_WD5000BEKT-WD-WX41A11X1750, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.FileSystemBusyEx:'An ocfs2 filesystem already exists on /dev/mapper/SATAWDC_WD5000BEKT-_WD-WX41A11X1750'
Tue Jan 31 12:18:46 CST 2012
at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:753)
at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:471)
... 21 more
FailedOperationCleanup
Starting failed operation 'File System Construct' cleanup on object 'fs_MyLocalRepository'
Complete rollback operation 'File System Construct' completed with direction=fs_MyLocalRepository
Rollbacker
Objects To Be Rolled Back
Object (IN_USE): [LocalFileServer] 0004fb0000090000865c3f26b528bc39 (Local FS OracleVS01)
Object (CREATED): [LocalFileSystem] 0004fb0000050000f36710bdcca530d4 (fs_MyLocalRepository)
Object (CREATED): [Repository] 0004fb0000030000182872191a913bac (MyLocalRepository)
Object (IN_USE): [StorageElement] 0004fb00001800004e793d6f05fced03 (SATA_WDC_WD5000BEKT-_WD-WX41A11X1750)
Write Methods Invoked
Class=InternalJobDbImpl vessel_id=5063 method=addTransactionIdentifier accessLevel=6
Class=LocalFileServerDbImpl vessel_id=4954 method=createFileSystem accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=setName accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=setFoundryContext accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=onPersistableCreate accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=setLifecycleState accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=setRollbackLifecycleState accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=setRefreshed accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=setBackingDevices accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=setUuid accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=setPath accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=setSimpleName accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=addFileServer accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=setStorageDevice accessLevel=6
Class=StorageElementDbImpl vessel_id=4972 method=addLayeredFileSystem accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=setSimpleName accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=createRepository accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setName accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setFoundryContext accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=onPersistableCreate accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setLifecycleState accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setRollbackLifecycleState accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setRefreshed accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setDom0Uuid accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setSharePath accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setSimpleName accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setFileSystem accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=addRepository accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setManagerUuid accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setVersion accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=addJobOperation accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setSimpleName accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=setDescription accessLevel=6
Class=InternalJobDbImpl vessel_id=5063 method=setCompletedStep accessLevel=6
Class=InternalJobDbImpl vessel_id=5063 method=setAssociatedHandles accessLevel=6
Class=InternalJobDbImpl vessel_id=5063 method=setFailedOperation accessLevel=6
Class=LocalFileServerDbImpl vessel_id=4954 method=nextJobOperation accessLevel=6
Class=LocalFileSystemDbImpl vessel_id=5072 method=nextJobOperation accessLevel=6
Class=RepositoryDbImpl vessel_id=5078 method=nextJobOperation accessLevel=6
Class=StorageElementDbImpl vessel_id=4972 method=nextJobOperation accessLevel=6
Completed Step: ROLLBACK
Job failed commit (internal) due to OVMAPI_B000E Storage plugin command [storage_plugin_createFileSystem] failed for storage server [0004fb0000090000865c3f26b528bc39] failed with [com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_createFileSystem to server: OracleVS01 failed. OVMAPI_4004E Server Failed Command: storage_plugin_createFileSystem oracle.ocfs2.OCFS2.OCFS2Plugin 0004fb0000050000f36710bdcca530d4 /dev/mapper/SATA_WDC_WD5000BEKT-_WD-WX41A11X1750, Status: OSCPlugin.FileSystemBusyEx:'An ocfs2 filesystem already exists on /dev/mapper/SATA_WDC_WD5000BEKT-_WD-WX41A11X1750'
Tue Jan 31 12:18:46 CST 2012
Tue Jan 31 12:18:46 CST 2012] OVMAPI_4010E Attempt to send command: storage_plugin_createFileSystem to server: OracleVS01 failed. OVMAPI_4004E Server Failed Command: storage_plugin_createFileSystem oracle.ocfs2.OCFS2.OCFS2Plugin 0004fb0000050000f36710bdcca530d4 /dev/mapper/SATA_WDC_WD5000BEKT-WD-WX41A11X1750, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.FileSystemBusyEx:'An ocfs2 filesystem already exists on /dev/mapper/SATAWDC_WD5000BEKT-_WD-WX41A11X1750'
Tue Jan 31 12:18:46 CST 2012
Tue Jan 31 12:18:46 CST 2012
Tue Jan 31 12:18:46 CST 2012
com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_B000E Storage plugin command [storage_plugin_createFileSystem] failed for storage server [0004fb0000090000865c3f26b528bc39] failed with [com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_createFileSystem to server: OracleVS01 failed. OVMAPI_4004E Server Failed Command: storage_plugin_createFileSystem oracle.ocfs2.OCFS2.OCFS2Plugin 0004fb0000050000f36710bdcca530d4 /dev/mapper/SATA_WDC_WD5000BEKT-_WD-WX41A11X1750, Status: OSCPlugin.FileSystemBusyEx:'An ocfs2 filesystem already exists on /dev/mapper/SATA_WDC_WD5000BEKT-_WD-WX41A11X1750'
Tue Jan 31 12:18:46 CST 2012
Tue Jan 31 12:18:46 CST 2012] OVMAPI_4010E Attempt to send command: storage_plugin_createFileSystem to server: OracleVS01 failed. OVMAPI_4004E Server Failed Command: storage_plugin_createFileSystem oracle.ocfs2.OCFS2.OCFS2Plugin 0004fb0000050000f36710bdcca530d4 /dev/mapper/SATA_WDC_WD5000BEKT-WD-WX41A11X1750, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.FileSystemBusyEx:'An ocfs2 filesystem already exists on /dev/mapper/SATAWDC_WD5000BEKT-_WD-WX41A11X1750'
Tue Jan 31 12:18:46 CST 2012
Tue Jan 31 12:18:46 CST 2012
Tue Jan 31 12:18:46 CST 2012
at com.oracle.ovm.mgr.action.StoragePluginAction.processException(StoragePluginAction.java:1325)
at com.oracle.ovm.mgr.action.StoragePluginAction.createFileSystem(StoragePluginAction.java:868)
at com.oracle.ovm.mgr.op.physical.storage.FileSystemConstruct.createFileSystem(FileSystemConstruct.java:57)
at com.oracle.ovm.mgr.op.physical.storage.FileSystemConstruct.action(FileSystemConstruct.java:49)
at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:193)
at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:264)
at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1090)
at sun.reflect.GeneratedMethodAccessor867.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:247)
at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:207)
at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: storage_plugin_createFileSystem to server: OracleVS01 failed. OVMAPI_4004E Server Failed Command: storage_plugin_createFileSystem oracle.ocfs2.OCFS2.OCFS2Plugin 0004fb0000050000f36710bdcca530d4 /dev/mapper/SATA_WDC_WD5000BEKT-WD-WX41A11X1750, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.FileSystemBusyEx:'An ocfs2 filesystem already exists on /dev/mapper/SATAWDC_WD5000BEKT-_WD-WX41A11X1750'
Tue Jan 31 12:18:46 CST 2012
Tue Jan 31 12:18:46 CST 2012
at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:475)
at com.oracle.ovm.mgr.action.ActionEngine.sendUndispatchedServerCommand(ActionEngine.java:427)
at com.oracle.ovm.mgr.action.ActionEngine.sendServerCommand(ActionEngine.java:369)
at com.oracle.ovm.mgr.action.StoragePluginAction.createFileSystem(StoragePluginAction.java:864)
... 18 more
Caused by: com.oracle.ovm.mgr.api.exception.IllegalOperationException: OVMAPI_4004E Server Failed Command: storage_plugin_createFileSystem oracle.ocfs2.OCFS2.OCFS2Plugin 0004fb0000050000f36710bdcca530d4 /dev/mapper/SATA_WDC_WD5000BEKT-WD-WX41A11X1750, Status: org.apache.xmlrpc.XmlRpcException: OSCPlugin.FileSystemBusyEx:'An ocfs2 filesystem already exists on /dev/mapper/SATAWDC_WD5000BEKT-_WD-WX41A11X1750'
Tue Jan 31 12:18:46 CST 2012
at com.oracle.ovm.mgr.action.ActionEngine.sendAction(ActionEngine.java:753)
at com.oracle.ovm.mgr.action.ActionEngine.sendCommandToServer(ActionEngine.java:471)
... 21 more
End of Job
I don't understand why I always get the error message 'An ocfs2 filesystem already exists on /dev/mapper/SATA_WDC_WD5000BEKT-_WD-WX41A11X1750' since that disk is blank with no partition.
Please help me.
Daniel.

Hi Avi,
Blkid returns the following:
/dev/sda1: LABEL="/boot" UUID="00b66c82-c4e2-4067-bbc4-f22899fce856" TYPE="ext3"
/dev/sda2: LABEL="/" UUID="b6bc51a3-884a-4d9d-8bc1-8c68792cbe57" TYPE="ext3"
/dev/sda3: TYPE="swap" LABEL="SWAP-sda3" UUID="58f3de58-a13b-4239-9894-8dffa0856a1a"
/dev/sdb1: TYPE="ntfs"
/dev/sdb2: TYPE="ntfs"
/dev/sdc: LABEL="OVSd62418098e5d5" UUID="0004fb00-0005-0000-d3ad-62418098e5d5" TYPE="ocfs2"
/dev/mapper/SATA_ST750LX003-1AC1_W2001LHFp2: TYPE="ntfs"
/dev/mapper/SATA_ST750LX003-1AC1_W2001LHFp1: TYPE="ntfs"
/dev/mapper/SATA_WDC_WD5000BEKT-_WD-WX41A11X1750: LABEL="OVSd62418098e5d5" UUID="0004fb00-0005-0000-d3ad-62418098e5d5" TYPE="ocfs2"
/dev/sdd1: SEC_TYPE="msdos" LABEL="CLE" UUID="827A-C3D5" TYPE="vfat"
"CLE" is an attached USB jump drive.
Thanks.

Add a disk to RAC

Hello,
I have a RAC database with 2 nodes and a cluster.
In my Cluster I have 3 disks with RAID5. I need to add 2 disks RAID0 where I will put my redolog files because I have a big waiting time in "log file parallel write"
I' m new in RAC and cluster can I add disksto a cluster with different RAID?

You could mix any kind of RAID (of course not recommended). Indeed, redologs with their high write activity should not be put on RAID5.
Werner

Add Physical Disk to VM

Similar Messages

Maybe you are looking for