According to this article, and many other articles and videos, I need to convert the two drives to dynamic disks before being able to setup RAID 1 array. ( -RAID-0-1-5-or-JBOD-Using-Windows-XP-Pro-SP3)
But when I right-click on any of the drives, I only see 'Properties' and 'Help'. I can't see 'Create dynamic disk' option in the right-click menu. I haven't come across a similar problem while doing research on this issue.
windows xp pro disk
Are the drives installed via SATA/ATA. Removable disk wont convert to dynamic. Sounds like the disks are initialized. Do you see anything else on the drop-down menu (are the options there but just greyed out)? Are you logged in as an Administrator?
* running list disk gave:DISKPART> list disk Disk ### Status Size Free Dyn Gpt -------- ---------- ------- ------- --- --- Disk 0 Online 466 GB 0 B Disk 1 Online 466 GB 0 B
running the command: select Disk 1, followed by: convert dynamic, gave the following output:DISKPART> list disk Disk ### Status Size Free Dyn Gpt -------- ---------- ------- ------- --- --- Disk 0 Online 466 GB 0 B Disk 1 Online 466 GB 0 BDISKPART> select Disk 1Disk 1 is now the selected disk.DISKPART> convert dynamicINTERNAL Error - The commit status has been lost
Other than that I think you may need to check your disks for errors. There are a few reasons why your disks appear full when they are not. You can find a list of troubleshooting methods here I would start by running chkdsk /F in the command prompt to fix any errors immediately. If your disks pass this test run through the other steps the page provides. Also note that if your system's file system is FAT32 that could be your problem. FAT file systems will not know what to do with NTFS. If your XP machine is FAT you can convert it to NTFS without losing any data however I would check the disks for errors first, and of course back up everything. If any of the troubleshoots give you error or unexpected results let me know if you need help sorting it out.
This article shows you how to create a recovery disk for Windows XP, if you have the original CD (can be used as a recovery disk) or, if not, how to create a recovery diskette (floppy disk).
The location of the operating system. Boot.ini uses the Advanced RISC Computing (ARC) naming convention to display the path to the disk partition and directory where the operating system resides. For example:
Upon running 'SFC /SCANNOW' I get a message to insert the Windows XP Pro SP3 disk.I had previously never heard of a Windows XP pro Service Pack 3 disk, I though there was only one type of SP3 CD. After some research, I located a service pack 3 disk, so I downloaded it, and tried running the command again. It complained about the CD being for the wrong version of XP. I've searched google for ages trying to find the correct one, to no avail. So, my question is:
Create a partition: To create a partition, highlight Non-partitioned space for the hard disk drive on which you want to install Windows XP Professional and press C. You are prompted to indicate how much available space to allocate from the nonpartitioned drive. Type the amount of space (in MB) and press Enter.
Good news, the base virtual hard disk "Windows XP Professional.vmdk" still exist on the old computer and you'll need to copy it to the new one and place it inside the Virtual Machine Document Package with the other files that comprise the Virtual Machine.
Unable to open file "/Users/pkitani/Documents/Virtual Machines.localized/Windows XP Professional.vmwarevm/Windows XP Professional-000006.vmdk": One of the disks in this virtual machine is already in use by a virtual machine or by a snapshot.
The Virtual Machine is configured to use a 20 GB monolithicSparse virtual hard disk and has 8 Snapshots giving the Virtual Machine Document Package a size of over 50 GB and without the Snapshots it would be 20 GB or less. In addition to the overall size having a large number of Snapshots decreases the overall performance of the Virtual Machine and makes it easier to become broken because of the number of files being managed and needed to make the Virtual Machine work normally.
So to the point of this, if you do not need to be running with 8 Snapshots I'd suggest doing some housekeeping on the Virtual Machine and get rid of the Snapshots all together and once cleaned up and a separate backup of the Virtual Machine Document Package is made for the purpose of Disaster Recovery you could then choose to run with one Snapshot and every so often delete the Snapshot and continue running with just one Snapshot. This would be more efficient then your current configuration of 8 Snapshots and will consume much less Host physical disk space and have better overall performance.
Now if you choose to delete the Snapshots there are several ways to go about this and because of the number and size of the Snapshots and type of virtual hard disk (monolithicSparse vs. twoGbMaxExtentSparse) personally I'd not use the normal route of using the Snapshot Manager and instead use vmware-vdiskmanager to create a new .vmdk (virtual hard disk) and then either swap it out for all the others in the Virtual Machine or just create a new Virtual Machine using it. The Snapshot Manager is in some ways the easier but longer route to take to consolidate all of the Snapshots Disks into the Base Disk however using vmware-vdiskmanager requires using Terminal and long command lines with several parameters and then additional steps to use the newly created .vmdk. There are some orther ways as well however under the circumstances using either the Snapshot Manager or vmware-vdiskmanager are the more appropraite methods at this place in time.
If you what to take the more complex but faster route using vmware-vdiskmanager I can make it much easier by providing exact commands to either copy and paste into the Terminal or also provide a shell script that will do it upon execution and a new .vmx file (Virtual Machine configuration file) that will go with to new .vmdk file but retain relevant information from the original.
Although I forgot to mention it when we talked nonetheless there is still one more housekeeping chore to do before backing up the new Virtual Machine to the Time Capsule as we discussed. This next step will further reduce the amount of Host disk space that the virtual hard disk take up. Using VMware Tools from within Windows you'll shrinking the C: Drive. You can access VMware Tools from Windows Control Panel or from the System Notification Area of the Windows Taskbar, by the clock. Once you have shrunk the disk you can then reboot the Virtual Machine to make sure all is well and then shutdown from within Windows and close VMware Fusion in order to make the backup copy of the Virtual Machine Document Package to the Time Capsule as we discussed.
Just wanted to let you know I was able to complete this tonight, including the shrink disk via VM Tools. It seemed to go smoothly and my virtual machine seems to be intact. I am keeping the copy of my VM before I did this and storing it on my Time Capsule just to be safe, then will delete it after I'm sure everything is ok.
What is the ASR feature in Windows XP/2003? How do I use it?If you run a Windows XP Pro or Windows Server 2003 computer and you wish to backup the system you can use a new feature called Automated System Recovery (ASR).The ASR process allows to restore the system disk (usually the C: drive) including the Windows files, all Registry settings and all user programs and data, allowing to recover a completely crashed system. To use this procedure you must be able to boot the Windows XP Pro Setup-program from the installation CD-ROM.During the restore process all data previously found on the System partition (usually C:) will be erased, then XP/2003 will be reinstalled, and the data from the ASR backup will be restored.
Windows XP Professional with Service Pack 1 Utility: Setup Disks for Floppy Boot InstallThe Windows XP startup disk allows computers without a bootable CD-ROM to perform a new installation of the operating system. The Windows XP startup disk will automatically load the correct drivers to gain access to the CD-ROM drive and start a new installation of Setup. You cannot upgrade from a Windows XP startup disk.
Related: What are the differences between Windows XP SP1 and Windows XP XP1a?Windows XP Home Edition startup disks will not work for Windows XP Professional installations and vice-versa.
The Windows XP startup disk allows computers without a bootable CD-ROM to perform a new installation of the operating system. The Windows XP startup disk will automatically load the correct drivers to gain access to the CD-ROM drive and start a new installation of Setup. You cannot upgrade from a Windows XP startup disk.Windows XP Home Edition startup disks will not work for Windows XP Professional installations and vice-versa.
This is essential. Without this, the procedure outlined on this page will not work. To find out whetheryou can use the steps listed on this page to re-create your bootable Windows XP setup disk, look for into yoursystem drive (usually the C: drive), and see if you can find a folder named I386 in the root directory.That is, see if you have the C:\I386 folder on your hard disk.
Some manufacturers provide you with the device drivers for your system on a CD that comes with your system. Others require you to go to theirwebsite and download these drivers. Whichever the case may be, make sure you have all your drivers handy before you start. Burn them onto a CD or DVD.Do not leave them on your hard disk, since your clean installation of Windows will probably wipe out everything on your hard disk.If your computer has SATA, IDE, SCSI or other mass storage devices (for your hard disks) that the Windows installer does not recognize out of the box,you will need to create a floppy disk with the drivers for that device. At the appropriate time, when Windows prompts you to hit F6 to load the driversfrom a floppy disk, you will need to so. This is however outside the scope of this tutorial. 2ff7e9595c
Comments