VRTX - Server, fabric, PERC, Virtual Disk - understanding of the FAILURES of components

Similar Questions

• MD1000 attached to MD3000. Virtual disk not on the preferred path

  Hello

  I have a MD3000i box connected to 2 boxes of MD1000, these are connected to a Dell Power Vault Storage server 2003 running.

  Last night I connected the 2nd MD1000 and added in 25 TB of drives worth. I had initially hurt mapping the new virtual disk after 20 minutes or so, I noticed that I had shot the Ethernet cable plugged into the Module Raid 0 by mistake. I plugged it back in and was able to map the drive and started the initialization of disks.

  I came this morning to check how everything is done and found an error on the table. Disk not on favorite virtual path, preferred owner: at location 0 RAID Controller Module. Current owner: Module to slot 1 RAID controller. Group MD1000_2 of disc. Ramdisk: Virtual4.

  Now, it seems that influence the new virtual disk that I created. I checked the path virtual disk property and all the other virtual disks are using path 1 and try that I created to use channel 0.

  The virtual disk seems to be working for the moment it is detectable and to initialize itself in the area of operations of MDSM. I'm under pressure to get the space of storage as soon as possible, so I can't really afford to have to blow the virtual disk and restart the initialization. I'm hoping a simple reboot of the storage array will cure the problem, but I guess I can't do so until the end of the initialization of the disks. I could also remap the path to the virtual disk, but I saw online that it does not solve the problem, and I always have to wait until the initialization is complete.

  Any help would be appreciated.

  Hello

  I deleted the disk group and created a new one that even once, did not help even after that I tried to change the path. I deleted again and created a new and then changed to RAID 1 controller quickly while he was still on the controller 0 (before it came with the failure of the path) as the preferred path that has cleared the error. There must be a mistake with the controller or the wiring to it.

  Thank you

• Virtual disk degraded and predictive failure Messages

  Hi Experts

  We get following errors in OpenManage for RAID 10. There are 8 hard drives, and one of them creates this problem. It is green / flashing orange.

  A foreign configuration has been found. : 0 controller (PERC H710 Mini)

  The 21.1.0 - 0007 current version firmware is older than the 21.2.0 - 0007 version firmware required for a model 0x1F38 controller: controller 0 (PERC H710 Mini)

  Virtual disk degraded: virtual disk 0 (virtual disk 00) 0 controller (PERC H710 Mini)

  Predictive Failure reported: physical disk 0:1:5 Controller 0, slot 0

  Event log: lack of PD: SasAddr = 0x5000c500437c0025, ArrayRef = 2, RowIndex = 0 x 1, EnclPd = 0 x 20, Slot = 5. : 0 controller (PERC H710 Mini)

  Storage Service event log: Predictive failure: PD 05 (e0x20/s5): controller 0 (PERC H710 Mini)

  See the errors, we bought new HARD drive and need your advice how we should move forward? Should we take offline from the old hard drive and then warm the new HARD drive? or we just need to upgrade the firmware of raid controller?

  If the disc is in a foreign State (or 'disappeared'), then it is already 'offline'... you simply remove it and replace it with a new one.  ALWAYS replace the replaceable drives to hot 'hot', then make sure that the drivers and firmware are updated once the reconstruction is complete and the system is sound (start with iDRAC and the BIOS, then the other firmware system).

• What is the right way to expand the virtual disk and then the OS partition?

  I have a Windows XP operating system in a virtual machine VMware.  I have

  you want to increase the size of the hard drive.  It currently has a 50 GB

  partition on a 50 GB VHD.  I increase the size of the

  50 GB to 100 GB in VMware virtual hard drive.  Then, can I use

  Windows disk management to increase the size of my partition of the

  side OS to use all the 100GB he sees now?  Or will

  corrupt my data or cause a problem as I really need to

  use a third party tool like EAUSUS inside Windows to extend Windows

  on the size of the virtual hard disk?

  In fact the way you describe, resize the virtual disk and then developing the partition are the way to go. But there are some things that you should be

  aware of.

  -If the VHD is on an IDE controller, you may not be able to resize the virtual disk. In this case use the converter. With the converter, you can resize the disk including the partition and - if desired - replace the IDE controller by a SCSI controller.

  -If you have only one partition under XP (that is, drive c :)) you cannot extend the partition with the diskmanager/diskpart. In this case, start your virtual machine from a CD/DVD Vista/Windows 7 in Repair Mode, open a command line and use "diskpart" from there to "extend" your partition.

  André

• Server 2003 - out of disk space on the partition of 12 GB

  I have a Dell PowerEdge 1800 server with Server 2003 R2 SP2 standard. 'Windows' resumes Go 9.51 to a 12 GB partition that has been installed and installed with the o/s by Dell. Now I have less than 2% left open (267 MB) and I don't know how to get more space. I did a disk cleanup and return the marginal space.

  Cliff

  Server issues are best addressed on the Technet site.

  http://social.technet.Microsoft.com/forums/en-us/categories/

  I can tell you that 12 concerts is not enough and same server 2003 will grow over time.

• understand the average physics to share the virtual disk

  Hello

  I wanted to understand the physical way to share a virtual disk by configuring the scsi controller.

  

  As you can see in the image as an attachment, I chose the option - "physical - virtual disks can be shared between virtual machines on a server any."

  So, I have a scenario and please let me know if the above applies or not?

  I have 2 ESX host. I have created a virtual machine on ESX host1 and now I want the virtual disk of the virtual machine to be shared and eventually used by the virtual machine on the other ESX host2. can I use the option above to satisfy my need?

  Also on a special note, 2 ESX hosts are not on the shared storage. they run with their own local disk.

  Still, I'll be able to do what I want?

  Thanks in advance.

  No storage shared or using the storage equipment. The 2nd esxi host does not see the local storage on the original host.

  Discover will have on the creation of a Cluster of Mirosft see how you can share disks. You can create a cluster in a box on the same host or use of RDM with shared storage to allow multiple vm' hosts aces acros the same storage.

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1004617

• initializing virtual disks

  I have a powervault MD1000 (Bay raid storage) connected to a backup server. It is set up with 3 virtual drives that each use 2 terabytes of storage in RAID 5 from our range of 8 physical disks.

  I had to replace two of the physical drives, and I need to initialize my virtual disks. In the Perc 6/E management screen VD, I can select the virtual disks (that show in red) and press F2 to display the operations, but the initialization button is dimmed and I can't select it. In the PD management screen, the new drives show as ready.

  How do I initialize my virtual drives? Should I delete them and create new virtual disks? It's my first time doing this, so please bear with me. Any help would be appreciated.

  I just updated the firmware of the 6th Perc to version 6.3.3 - 0002, which has a rep to support Dell recommended that I do, if this is useful.

  After you remove virtual drives, I was able to create a new virtual disk and initialize it. It seems that I just have to build the virtual disks from scratch.

  Thank you for your time.

• Dell virtual disk are larger. You want to increase the size of the data store.

  Hello

  I started the implementation of a server ESXi 5.5 Update 1 this week. I didn't know Dell shipped the server with two virtual disks instead of one. I realized this _apres_ that I had already created the data store and setup a few virtual machines to the breast. I called Dell who sent specific instructions to increase the removal of the second (empty) virtual disk and add it to the main. In the end, I increased the single VD from 2 TB to 3 TB and I want to give the remaining space in my store of data.

  I tried to follow the article here that explains how to do this via the CLI.

  Well, he did not altogether. Fortunately, I was able to recover my datastore my setting start and end sectors to their original numbers. But I'm still left with this almost 1 TB of space that I can not attribute to the data store. After that I reread storage adapters in the client, the new Dell disk size resulted under measurement devices. Click on "increase...". ", generates the following error which led me on the way to the CLI method:

  Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" to object "ha-datastoresystem" on ESXi '[myservername]' failed.

  I will paste my notes that I took everything by jobs. Things have exploded the rails when I put 4 partition size to the largest size. Any help, please?

  ---

  I use that as a guide:

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2002461

  
  

  1 use start hardware device management tools to increase the capacity of additional disk to the device. For more information, commit your hardware provider.

  This has been done. The new size of the virtual disk is 2791,88 GB (TB 2,79188)

  
  

  2. open a console to the ESXi host.

  Pretty simple.

  
  

  3. get the DeviceID for the data store to change.

  ~ # vmkfstools Pei "/ vmfs/volumes/datastore1 / '.

  System file VMFS-5, 60 extending on 1 partition.

  File system label (if applicable): datastore1

  Mode: public

  Capacity 1971926859776 (blocks of files 1880576 * 1048576), 1042688245760 (994385 blocks) prevail, max size of the 69201586814976 file

  UUID: 534e5121 - 4450-19dc-f8bc1238e18a 260d

  Partitions split (on 'lvm'):

  NAA.6c81f660ef0d23001ad809071096d28a:4

  
  

  A couple of things to note:

  a. the device for Datastore1 ID is: naa.6c81f660ef0d23001ad809071096d28a

  b. the number of Partition on the disk is: 4 ' [...]: 4 "»

  c. the prefix, "naa," means "Network address authority" the number immediately after is a single logical unit number.

  4. Enter the amount of disk space available on the data store.

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 1. 8T 865.4 G 971,1 G 47% / vmfs/volumes/datastore1

  
  

  5 team of the device identifier, to identify the existing partitions on the device by using the partedUtil command.

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  ~ #

  
  

  According to the table in article KB

  4 13711360 3865468766 251 0 - primary #4, type 251 = 0xFB = VMFS, 13711360-3865468766 areas

  | |        |          |   |

  | |        |          |   \---attribut

  | |        |          \---type

  | |        \---se finishing sector

  | \---a starting from sector

  partition \---Numero

  
  

  Also note how the number of section start the old end sector number is + 1.

  
  

  6 identify the partitions that need to be resized and the size of the space to use.

  We want to resize partition 4. I don't really understand the last part of this sentence, however. Read more.

  
  

  7 the number of sector end you want for the target data store VMFS partitions. To use all out at the end of the disc space, remove 1 of the size of the disk in the areas as described in step 5 in order to get the last usable area.

  ESXi 5.x has a command to do this:

  ~ # partedUtil getUsableSectors "/ vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a".

  1 5854986239

  This means that we want 4 Partition of "naa.6c81f660ef0d23001ad809071096d28a" to be:

  13711360 - 5854986239 (i.e. the end of the disc)

  
  

  8 resize the partition containing the target VMFS Datastore using the command partedUtil, specifying the original existing partition and the desired end sector:

  Using the above information, our command is:

  resize # partedUtil ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 5854986239

  
  

  9 step 8, the partedUtil command can report the warning:

  He did not. Displacement.

  
  

  10. the tables of partitions have been adjusted, but the VMFS data within the partition store is always the same size. Now there is an empty space in the partition where the VMFS data store can be grown.

  
  

  11 launch this v vmkfstools command to perform a refresh for VMFS volumes.

  Fact.

  
  

  12 reach the VMFS Datastore in the new space using the command - growfs vmkfstools, specifying the partition containing the VMFS Datastore target twice.

  vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 '.

  
  

  It did not work. I got an error:

  / vmfs/volumes # vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' /vmfs/devices/disks/naa.6c81f660ef0d «»

  23001ad809071096d28a:4 ".

  Cannot get device head way /dev/disks/naa.6c81f660ef0d23001ad809071096d28a:4 information

  
  

  Also the partition was very different to what I asked:

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 1560018942 251 0

  
  

  I fixed it by running these commands:

  ~ # partedUtil resize ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 3865468766

  ~ # vmkfstools v

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  Update:

  Since it was such a new machine, not in active production, we have safeguarded the VMs management off the ESXi host. Then flattened the virtual disk, recreated, and then created a store of data with the right size. (TPG this time, naturally.) We put the management of virtual machines on the data store. For Windows virtual machines, we have restored the using AppAssure. Everything is ok now.

  Need to add a new item to the list of punch: check what Dell has done the configuration of the virtual disks. :-)

• Cannot resize the virtual disk, the virtual machine by using a «child» vmdk file

  Release: VMWare workstation 9

  SE host: Windows 7 64-bit

  Screenshots below.

  I want to resize my VM from 50 GB to 100 GB.

  It seems that VMware workstation 9 uses a child for my VM vmdk.  In my case, using its "Windows Server 2008 R2 x 64 - 000001.vmdk" for its virtual disk file.  The correct file should be "Windows Server 2008 R2 x64.vmdk", I think.

  There are currently no snapshots registered for this virtual machine, I see.

  The virtual machine works well as is, but I can't resize the disk without the VMWare gui, saying I should be perform the operation on the parent vmdk file.

  It seems that I do run a snapshot that is not really a snapshot?  How to merge with the older files - Sxx.vmdk to 0000xx - Sxxx.vmdk

  I also tried to use the command line tool to manually resize the vmdk parent, but I get permission "access denied" errors.

  Kind regards

  Matt

  -------------------------------------------

  Parameters of the HARD disk:

  

  Error:

  

  Files:

  

  He no snapshots are displayed in the Manager of snapshot with the check box 'Show AutoProtect snapshots' verified then the snapshot is an orphan and the best way I use normally to fix this if I want the contents of the snapshot of orphan to be among the basic disk is with tab of the virtual machine in VMware Workstation GUI closed I simply delete the .vmsd file and then open the virtual machine tab in the VMware Workstation GUI and cover and immediately remove a snapshot in the Snapshot Manager.  This will force the orphan snapshot to merge with the parent disk.  Then to clean I still remove the .vmsd file and orphans, .vmsn and .vmem file.

  Note: Before the procedure you have a good backup of the virtual machine in case you accidentally mess something up.

• 7 virtual disk added vSphere data protection

  Hi, we are deploying vSphere Protection of data in the model of the FVO, after completion, we found 7 virtual disk listed in the properties of the vm disk of 1x100GB and 6x256GB of the disc, we could just understand why the model gave us 7 disc, a google search didn't really give us any idea either.

  Few can have space constraints. This is for flexibility.

  Other than 1, the disks are disks of data and you have the possibility to migrate to different data warehouses after deployment.

• Help wanted | How to increase virtual disk space

  IM using ubuntu as my client machine and esxi 4.1 running on the server dell 2850. My image is initially sized like 15 GB, but I want to expand to 100 GB, which is the amount available in the actual physical drives attached to the server.

  If I try to change the disk space by changing the settings it does not change the internal space used by ubuntu. ?

  Can someone help me how can I change the settings for the virtual disk grows as the capacity of the physical drives increases?

  Thank you

  If you originally created a thin provisioned disk then it will behave as you describe, but you still need to expand the space inside your file of Ubuntu system using gparted. Download the live CD of gparted.

• large partition or make mutiple small virtual disk virtual disk

  I have a server that is running vmware server and using windows server 2008 as a host operating system. I need to set up two machines vitrual which will act as a file server and database server.

  I have a RAID 5 with the host using 3 were leaving. one for the host, one for file server and the other for the database server. I would like to know what is the best for proformace.  Do I have to create a virtual disk of 1 TB and let the guest operating system put in place three partition for the file server or should I create 3 small virtal drive and let the guest operating system to use all the space on the small virtual disk 3. the reason why I need 3 partiton is due to a mapping application that is 500 GB and we can only save. Therefore a partition for it because our backup software backs up only the partitions.

  the database server will be a p2v and I think there just a single partition.

  With a single RAID set on the host computer, you can choose either way, avoid any difference in performance. However, I'd probably go with 3 virtual drives. This way you can - if it takes more performance disc - add for example an addition RAID 1 go up and turn the virtual disk of db the extra RAID to set.

  André

• Impossible to extend warm a virtual disk with VIC

  When I change the properties of the guest in VIC esx 3.5 and try to extend the current virtual disk I get the error message "a general system error occurred: internal error.  I am trying to extend the partition D 1200 Go 1 300 Go and I have enough space for 1440 GB.  I was not able to try to extend the drive when the prompt is disabled, but as it is a critical server that requires little downtime. I am also able to expand virtual disks on the other guests, but not this one.  Suggestions as to how I can get this virtual drive to extend hot would be welcome.

  You cannot extend a drive over 1 TB in gui in ESX 3.5... bug in vmware.  Take a look at http://kb.vmware.com/kb/1008528

  What you need to do, is extend the command line in ESX.  To do this, you should close the virtual machine. 994 Ko has more details on that. Basically:

  Log in to ESX

  Stop the virtual machine

  Use the vmkfstools command to extend the drive

  for ex:

  vmkfstools x 1300G

  It's been a while since I did it, so please check me, but I'm pretty sure the syntax.

• What are the steps to create, format and install a new virtual disk in Windows

  I swear I've scoured the Internet for days trying to find the details of this process, and I'm embarrassed to have failed in my quest to understand what I must be a very simple thing.  The best I can do is this:

  Step 1: Create a new vmdk using vmware-vdiskmanager

  Step 2:?

  Step 3: Get your vmdk newly formatted using vmware-mount, or using "Map Virtual Disk" of the Workstation option

  Now, you will see that somewhere between step 1 and 3, it is an essential step of the new vmdk format so that it can be recognized and mounted.  Simply, I can't find any example online how to do this.  I just know someone will say "just attach to a virtual machine and format her", to which my answer is "how?  It won't let me get an unformatted disk.  When I try to go directly to step 3 after step 1, I get the following error, "error reading volume information.  Please select another file to disk.

  Help!

  VM--> change the settings.

  Hardware tab.

  Add the button.

  Select "hard drive".  Follow the instructions in the wizard.  At the selection of create new floppy or use existing, select "Use an existing virtual disk" and find the vmdk file, you have created.

• Utility RAIDCFG to slow initialize virtual disks

  I use RAIDCFG. EXE from DTK to configure a Raid of H700 on a R910 controller.

  I would like to start slow initialization of a virtual disk. Documentation, the command is:

  raidcfg - vd - c = X - vd = Y - ac = sli

  I get a message of successful immediately command.

  How do I know what the State of the initialization?

  Thanks for any help.

  For more information on init, slow and fast, please visit NOTE from the ADMIN: broken link has been removed from this post by Dell >