Utility RAIDCFG to slow initialize virtual disks

Similar Questions

• The initialization of the swap file to virtual disk periodically (40% of the time +/-) fails to start Windows

  Greetings-

  For the past year or so I put my Windows 7 32-bit, 8 GB RAM system to initialize the page automatically on a virtual disk file (in order to reduce the physical disk reads/writes and to speed up the access to the page files).

  Here's how I set up: I installed Dataram Ramdisk and configured to use memory beyond 4 GB (which, as everyone here knows, 32-bit Windows can not otherwise use) as the ramdisk.  In setting up manually formatted the 4 GB unallocated space virtual drive as an NTFS volume and it gave the letter a: (what else!). Then I got the software save an image file of the ramdisk formatted my hard drive F:. Additional configuration of the software wants to initialize the virtual disk to start and immediately copy the image file to the virtual disk, thus creating a 4 GB NTFS formatted volume a:. (Incidentally, I also use the virtual disk to the cache of the browser and the print spooler). The theory here is flawless. But to make it work in practice, the virtual disk must be initialized and the image file copied into ramdisk (making it a formatted disk R :) front Windows initializes the pagefile.

  It runs about 60% of the time, but for the remaining 40 percent Windows gives an error message indicating that Windows has created the page file in a temporary location (it's always the C: drive, the pagefile in general where default.). The only reasonable explanation I see why it fails is that, for nearly 40% of my computer boots window wants to initialize the page file before the ramdisk is ready to receive. What I don't understand is why that happens.

  This happen to my main question: is it possible to control the Windows boot sequence so that the ramdisk is initialized and the filename of the image copied to him on a basis consistent before Windows wants to initialize the page file? Operationally, I guess it boils down to whether it is possible, during each startup sequence, to delay initialization of the page files or to move the virtual boot record earlier in the sequence. If so, how to do that? If not, can someone explain why the order of the respective boots usually works, but does not reach a good amount as well?

  Ideas on this would be appreciated.

  RAS43

  Create a small paging file to 20 MB on the boot volume (the partition where the Windows files are installed) this way the session manager will be able to start the Windows session and create additional paging files without complaining.  You can have more than one paging on several disks, Windows will favour the less busy the disk paging file.

  John

• Failed to initialize the library for the assembling and disassembling workstation virtual disks 9

  I am using VMware Workstation 9.0.4 build-1945795 and have a problem with "map of the virtual disks. I tried map a virtual drive on windows server 2008 r2, windows server 2008, windows 7, windows xp, windows 2000, windows 98, and BACK 6.22. I have went to the file - card virtual disks and get 'Could not initialize the library for the Assembly and disassembly of the virtual disks', every time I have try to map any operating system for the virtual machine. Some have snapshot while others do not is a mixture of 64-bit and 32-bit virtual machines. My system is Windows 7 Enterprise 64-bit. What I'm missing here because if a feature is available in the menu you seem to expect it to work actually on something.

  OK the fix for me was that I had to uninstall VMware workstation and now it seems to work very well on all the OS preceding reinstall it.

• Cannot change the size of the virtual disk in a converted VM

  Hi, I have converted many physical machines into virtual machines using the VM converter. All off them were converted using the minimum for their HDs size so that the conversion process minutes last as little as possible. Because now there are in all readers of 'C' for all virtual machines only 1 GB of free space I want to resize their virtual disks. The problem is that I can resize them to a larger size, but Windows does not allow me to expand the volume inside Windows. When I want to expand the size of the Windows volume shows me a message saying "the selected volume is a system disk or a boot disk, or it was created in an earlier version of Windows, a basic disk. It cannot be extended.

  I am attaching two files. The first is the configuration of the VM. The second is the error that appears inside of Windows. The message is in Spanish cause that Windows is in that languaje, but I have translated from English in the previous paragraph.

  Is anyone of you know why this kind of errors appear? Does perform a work around? It seems that the problem is because the converted Convert the HD as a base virtual HD. In this format (Basic) Windows does not allow to expand. You have to change its format in Dynamics to develop, but when you try this error appeard.

  The first work-around, I thought to do is to make a picture of this disc with Ghost and try to paste this image into a new hard drive for the virtual machine, but I don't know if it will work.

  Thank you.

  Warlock.

  I have had success in utility Dell ExtPart help to resize on the fly without interruption of service to initialize volumes (drives C :).  Other methods such as attaching the drive as a data volume to another server or using GParted require at least downtime of this virtual machine and often down more than one time.  With ExtPart, I was able to avoid it completely.

  Check out this blog for more information post:

  http://blogs.kraftkennedy.com/index.php/2009/06/30/expand-virtual-machine-boot-volumes-with-no-downtime/

• 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.

• MD 1220 / PERC H800 - how Raid 1 virtual disks?

  Hello I'm trying to configure Raid 12 1 (two pairs disks) in my Inbox MD 1220 with PERC H800. I started with 12 discs as 12 virtual drives Raid 0 and have recently added 12 additional physical disks for a mirror. I am able to mirror 9 virtual disks but when I select my 9th virtual to the mirror, no drives appear as available. The other 3 drives are there in the 'ready' State, but manage to open or the BIOS configuration utility seem to be able to use them as candidates of mirror. My computer is running in a kind of limitation of Raid 1 with Cabinet / card? Operating system: Windows 2008 R2 Datacenter Open Manage 7.4 Latest firmware / drivers for PERC H800 thanks! Dan ouedraogo

  Hi Joey

  I just tried OMCleanup and reinstalled 7.4.  He exhibited the same symptoms showing is not the physical drives in the H800.  I can't find a download 7.2 but would be willing to try the previous versions.  A previous version of OM worked with the same controllers / speakers / computer, but I do not remember the version where I improved.  (I am an individual shop and am not very informed when it comes to managing open, its versions and how to install/uninstall).

  I can still kill the DSM SA connection Service by running a foolish occupation for the H800 report.  The report H700 works fine.

  Dan

• MD1220 disk expansion & expansion / resize virtual disk

  I seek to add 6 new MD1220 to a current configuration of 6 who are chained together.  Two quick questions on this...

  (1) is there as a limit to how many MD1220 can be connected?

  (2) once the virtual disks were created in all of my original 6 devices, is it possible to resize or add to this Setup?  Or I should blow away and recreate?

  Thank you
  Greg

  Hello Greg,.

  (1) is there as a limit to how many MD1220 can be connected?  You can put a maximum of 4 cases with the MD1220 can be chained together (which gives a total of 96 disks per SAS port).

  (2) once the virtual disks were created in all of my original 6 devices, is it possible to resize or add to this Setup?  Or I should blow away and recreate? You can add disks to your virtual drive and can increase the size, but depending on how much space you add that it can be faster to back up data and then recreate the virtual disk and restore your data.  A virtual disk expansion is really slow and it may take weeks or even months depending on the size of the virtual disk.

  Please let us know if you have any other 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 Manager "the device is not ready".

  I don't know about the format from outside, possibly MAC OS EXTENDED. He was not ejected a Mac and will not mount on an operating system MAC or PC (Windows 7 Professional) using Firewire (800 to 800 and 800 to 400), eSATA and USB 2.0. When I use disk management, disk will appear as not initialized and next to the "disk 33", there is a red arrow pointing down. Whenever I open the Disk Manager, the window to initialize the disk appears, but once I chose a style of partition and press OK, the virtual disk manager pops up saying "the device is not ready". I also tried to wipe the drive using CMD, (disc of DiskPart/list / select disk 33/clean), CMD said the drive was clean, but when I went to disk management, without change.

  I'm looking for a way to clean the drive so that it can be reformatted and reused.

  Hi Catherine,

  The question you posted would be better suited in the TechNet Forums. I would recommend posting your query in the link below.

  http://social.technet.Microsoft.com/forums/Windows/en-us/7e214b16-E415-449a-8f25-4cace51e5106/Virtual-Disk-Manager-error

  Good day!

• 5.4 OpenManage cannot initialize new disks PowerEdge 840

  I'm bored of Array Manager. I think Openmanage is a poor substitute.

  I have a new Dell PowerEdge 840 Server with two disks SAS and SAS 5i/R controller of berries in a mirror Raid-1 (made in hardware)

  I have installed OpenManage 5.4 WITH the storage option.

  I put two new hard drives SAS I want to initialize and create another virtual disk of Raid-1.

  OpenManage sees the drives (loans and OK but not online) and gives me two options under tasks "Blink" and "Unblink.

  Now when I put two drives in my component Snap Server PowerEdge 1600SC Array Manager 3.6 MMC 3 years, I could create a virtual disk from the operating system.

  What happens with Array Manager. Why he let do this to me?

  What is going on? Why can't initialize new disks and create a virtual disk?

  It comes to my main server. I can't take it offline for 10 hours initialize disks.

  I went into Windows disk management and that he sees the drives but I don't want a Software Raid.

  Thank you

  Lara

  
  

• Consolidation of many to one of the virtual disks?

  Hello world

  I use a XP client inside a Windows 7 host (using 8 workstations).

  In the configuration of my XP virtual machine I previously assigned (of 50 gigabytes) of disk space into separate virtual folders, about 2 GB each, as shown below.

  

  I now want to have a single vmdk file, with the pre-allocated 50 GB of capacity.

  Is it possible that I can achieve this goal, while keeping my VM in tact? For example can I create a second virtual disk, and then use a cloning tool (from the client) BONE to make a copy to the new virtual drive?

  Here, any help will be greatly appreciated.

  Kind regards

  DAVO

  Hello world

  This can indeed be done! Because I started with a scalable, split, virtual disk, there were several steps; Here's the gist of these measures-

  (1) using the vmware-vdiskmanager merge files into a single.

  http://hostilecoding.blogspot.com.au/2013/06/VMware-merge-multiple-VMDKs-into-single.html

  Note: when running this utility do not forget to include the '2' parameter, which refers to the creation of a virtual disk prealloue, otherwise the following steps (use the shrinkvd program will NOT work!).

  Here is a screenshot of the order that worked for me-

  

  (2) add the newly created virtual disk, 'merged.vmdk' to the existing virtual machine, using these installation instructions.

  https://www.VMware.com/support/WS5/doc/ws_disk_add_virtual.html

  (3) remove the existing virtual machine virtual drive

  (4) to start the Virtual Machine (you will probably be asked if you have moved or copied the VM, I responded with "Proposed").

  (Optionally)-rename the virtual disk of "merged" into something else by renaming the files in the ".vmx" and "hard" files.

  (5) using the shrinkvd resize the virtual disk

  http://www.Softpedia.com/get/system/system-miscellaneous/shrinkvd.shtml

  

  Above, note that the first time, I ran the command it failed with the message "ddb.deletable" is the crux of the problem. I just deleted this line in the relevant file "hard" and the command is represented.

  Now, when I boot on my virtual XP I use only 24 GB of space, and I am able to transfer the Virtual Machine to a smaller drive. in this case a 30 Gig old SSD.

  I hope this helps others.

  Kind regards

  DAVO

• Why can't I reduce the file size of virtual disk?

  Workstation help 8.0.4, why is the file size of virtual disk for my more bigger than the amount of space used within the instance instance?

  The instance (Windows 7 Ultimate 32 bit) HARD drive is 40 GB... He is currently using 28.6 GB of this space.

  But the hard for instance file is 34.5 GB size - it is more than 20% larger.

  I defragmented the drive on the instance.

  I defragmented and compacted file hard (via the 'vmware-vdiskmanager' command line utility)

  I defragmented the host drive.

  Any not really - I'm just curious as to why I can't get it down to a smaller size (mainly to speed up backups)

  Narrowing of a virtual disk is done in two steps. Unused disk space must first be cancelled in the comments, what OS, then blocks not null the hard are copied to a new file hard. With VMware Workstation 8, you can start this process in the VMware Tools window (right-click the icon in the system tray)

  André

• Virtual disk on an iscsi SAN

  I have a question about virtual disks and how they actually read and wrote on the physical disks on a San.   Lets say I have the Exchange virtual server and a virtual SQL Server on the same RAID set on the SAN.  As you know, Exchange writes on the disc at random while MS SQL server writes sequentially.  Each app just write randomly and successively on their respective virtual disk?  If so, VMware wrote how physical disk with regard to how the application has written to the virtual disk?  For example, if Exchange writes randomly on the disc, which is technically the virtual disk on the ESX host file, VMware writes the changes to virtual disk random file on the physical disk?

  It depends on your performance needs - usually it's a good practice (virtualized or not) in order to isolate the workloads that shouldn't be able to influence the other.

  So, you can choose to create small groups of raid for the individual applications.  This has the advantage of better insulation, but at the cost of reduced performance for this application (and reduced the efficiency of storage capacity).

  It depends on your business needs.  If your SQL server server have been got nutso and eats all your IOPS / s, it would be OK that the Exchange has become terribly slow until you figured it out?  If so, then of course keep 1 large group.  If this isn't the case, then it split and bite the bullet on the cost.

• Performance of the virtual disks

  Hello!

  Two questions

  1 - it there really a big difference in the performance of the discs thin vs thin discs? one of my friends said slim is slower because he may need more and this growing each time may reduce the speed and performance. is this really?

  2. I get no difference between the discs of updated zero lazy-reset and greedy. that means for the impatient..., are the blocks are written by 0 at the beginning?

  There are a few blocks in the disc ok? then, what is the point to write zero in each of them and then change the exact data we want to be on that block? (maybe there is 1 maybe 0)

  Thank you very much

  So I will use zero - eager to drive thick for my server files (300 users and millions of files) and lazy zero for databases and thin for operating systems and machines at low load of I/O and small changes

  I recommend thick eager-reset to zero especially for databases. It can depend on the workload, however, there are various tutorials for how to configure databases. MS - SQL I usually create virtual discs eager-reset to zero and follow the best spirit of practice of MS formatting NTFS with a 64 KB Cluster size. Where the OS is Windows 2003, don't forget to align the partition! For more information, see Disk Partition alignment Best Practices for SQL Server

  Since, as you have discovered - reset is required will certainly benefit you eager-reset of the virtual disks.

  When you use thin disks, make sure you have the alarms in place to avoid the problems of out-of-space drive!

  André

• Virtual disk migration takes too long

  Hi, I am in the process of migration of virtual disks to another data store and the process is extremely slow. After 1 hour, the progress bar indicates 20%. At this rate, it will take several hours to complete the task.  I'm migrating three virtual disks (all thin provisioned) to one NFS data store to another. Sizes are:

  100 GB

  300 GB

  15 GB

  It would be the size fully provisioned. Actual usage is much less, as the discs have approximately 75% of free space, except fot the disc of 15 GB that has about 3 GB of free.

  I use the function of migration in VCenter to do this, right-click the virtual machine, and then choose "migrate", then change the store data, then advanced, and then selecting the new data store so that three virtual disks I want to migrate, leaving any other set to the "place of current residence.

  I do this with the virtual machine power off and with the configuration file and disk 1 swap partition remaining in the same data store.

  Any ideas on why it would take so long or how to speed it up?

  Thank you

  Hello

  Any ideas on why it would take so long or how to speed it up?

  What is your speed of NFS storage network? The faster the faster Migration

  In addition, the time is calculated on the full size which is 475 GB, even if only 200 GB may represent real data.

  Because it is thin and put into service, what you'll see is running slow copy while it is copying data for example the first 50% but then there after the advanced bar will move to 100% very fast because as it is no real data to copy, just space put into service.

  Therefore it will not be a case of 1 hour = 20%, or a total of 5 hours to do the migration complete

  I will estimate that it will take between 2.5 to 3 hours (calculated estimate)

  Hope all that makes sense

  Please allow points if you find this useful/correct