Cannot extend a VMFS volume

I have an installation of VMWare Essentials 5 I've updated since version 4.

Initially, I had 4 300 GB drives in a hardware raid. After the upgrade to version 5, I added 4 additional disks and used the HP software to extend the logical volume to 1.9 TB.

I am trying to add this new space to my store of VMFS data but am unable to.

When I select my host in VCenter and go to storage in the Setup tab and then go to devices so I can see my disk is recognized as 1.91 TB.

It also shows the primary and logical partitions current:

Primary:

1 BACK 16-bit < M 4.00 32 MB

2 BACK 16-bit > = 32 M 4.00 GB

3 VMFS 833,22 GB

4 scope 896,00 MB

Logic:

1 BACK 16-bit > = 32 M 250.00 MB

When I go to the store database properties dialog box and click the button increase then I should see the list of available free space.

This list remains empty and so I can't extend the volume.

The file system is 5.54 VMFS with a block size of 1 MB.

Any help would be much appreciated!

Regarding kind.

Marcel bourdon

Sorry for the delay, I did a rebuild of my test system these days.

I have reproduced what you have and was able to successfully complete such VMFS volume that documented in the link I provided (except VMFS partition 3)

I did install ESXi 4.1 U2 on a 900 GB drive, then upgrade to ESXi 5.0 and increase the size of the disc to 1.9 TB. Then I opened a session SSH, fdisk used to resize/increase the VMFS partition (which btw. is a primary partition with the new additional disk space adjacent to it) and expanded the cultivated partition using vmkfstools.

If do not already rebuild you the host, please after af fdisk-lu as well as ls/vmfs/devices/disks

André

Tags: VMware

Similar Questions

  • When I tried to power on VM ends up in the right error: the specified file is not a virtual disk. Cannot open disk ' / vmfs/volumes/4d48ad95-ad5e027a-67f4-e41f1360cc9e/Iso/ser01/ser01.vmdk' or one of the snapshot disks it depends on.

    I stop a virtual machine after a certain time, I tried to power. Its has ended up in the following error message

    Reason: The specified file is not a virtual disk. Cannot open disk ' / vmfs/volumes/4d48ad95-ad5e027a-67f4-e41f1360cc9e/Iso/ser01/ser01.vmdk' or one of the snapshot disks it depends on.

    The machine was working fine before the closure.

    In the data store, the file type of the virtual machine is 'file' instead of 'virtual drive '.

    Help, please

    You are missing the file descriptor hard. The xxxx - flat hard is the file that contains the data effectively. But the xxxx.vmdk is missing, which is a text file that connects to the flat file.

    AWo

  • Cannot remove dumpfile created volume vmfs - 5.5

    I have a 5.5 with only local storage server I recently upgraded to 5.1.

    A few days ago I had inventoried all my VM folders on the next partition:

    / vmfs/volumes/comments.

    Today, when cleaning latest virtual machines, I find the following:

    /vmfs/volumes/guest/vmkdump/44454C4C-4400-1048-805A-C7C04F4C4631.dumpfile

    I don't know what created this... I understand there dumpfiles that can be created on PSODs, but I can't find any reference to a real folder called "vmkdump."

    When I try to delete it, I get the following:

    / vmfs/volumes/524f80a6-f18c10c7-2 c 16-001e4f204bc4/vmkdump # rm - rf 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile

    RM: cannot remove ' 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile': device or resource busy

    I looked at various KBs and I can't understand it:

    -lsof does not list this file or directory

    -all virtual machines have been cut (maintenance mode)

    -the server has been restarted several times

    I found the following info that may be useful:

    VMkernel.log shows (apparently at the start):

    VMkernel.log:2013 - 10-17 T 03: 13:28.048Z cpu3:70444) FS3: 196: START 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile >

    VMkernel.log:2013 - 10-17 T 03: 13:28.048Z cpu3:70444) FS3: 198: END 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile >

    VMkernel.log:2013 - 10-17 T 03: 17:10.392Z cpu6:70981) FS3: 196: START 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile >

    VMkernel.log:2013 - 10-17 T 03: 17:10.392Z cpu6:70981) FS3: 198: END 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile >

    VMkernel.log:2013 - 10-17 T 03: 33:22.900Z cpu0:73786) FS3: 196: START 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile >

    VMkernel.log:2013 - 10-17 T 03: 33:22.900Z cpu0:73786) FS3: 198: END 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile >

    VMkernel.log:2013 - 10-17 T 03: 40:31.233Z cpu7:75668) FS3: 196: START 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile >

    VMkernel.log:2013 - 10-17 T 03: 40:31.233Z cpu7:75668) FS3: 198: END 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile >

    VMkernel.log:2013 - 10-17 T 03: 41:25.409Z cpu3:75805) FS3: 196: START 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile >

    VMkernel.log:2013 - 10-17 T 03: 41:25.409Z cpu3:75805) FS3: 198: END 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile >

    VMkernel.log:2013 - 10-17 T 04: 36:02.444Z cpu3:36299) FS3: 196: START 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile >

    VMkernel.log:2013 - 10-17 T 04: 36:02.444Z cpu3:36299) FS3: 198: END 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile >

    Also, I get the following with vmkfstools result:

    / vmfs/volumes/524f80a6-f18c10c7-2 c 16-001e4f204bc4/vmkdump # vmkfstools d 44454C4C-4400-1048-805 a - C7C04F4C4631.dumpfile

    Lock [type 10 c 00001 compensate 206995456 v 2409, hb offset 3920384

    GEN 27, mode 1, owner 525f6851-c5108b26 -001e4f204bc4 mtime ce23 - 645

    [num 0 gblnum 0 gblgen 0 gblbrk 0]

    < 4, 465, 104 > addr gen 2238, links 1, type reg, flags 0, uid 0, gid 0, mode 100666

    Len 166723584, n. b. 159 tbz 0, 0, newSinceEpoch 159 cow, mrz 1, bs 1048576

    According to KB 10051, the number of updates in bold above is intended to indicate the MAC address of the owner of the lock.  Which makes absolutely no sense to me, that's the address, it belongs to the second internal NETWORK card in this system:

    list/vmfs/volumes/524f80a6-f18c10c7-2 c 16-001e4f204bc4/vmkdump # esxcli network nic

    Name PCI Device Driver link speed Duplex MAC address MTU Description

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

    vmnic0 bnx2 up to 1000 Full 00:1e:4f:20:4 b 0000:003:00.0: c2 1500 Broadcom Broadcom NetXtreme II BCM5708 1000Base-T Corporation

    vmnic1 bnx2 0000:007:00.0 half low 0 00:1e:4f:20:4 b: c4 1500 Broadcom Broadcom NetXtreme II BCM5708 1000Base-T Corporation

    As you can see that this NETWORK adapter is in down state... it is not plugged in and has never been used (recently) for anything.

    EDIT - Holy coincidence Batman!  It seems that the Mac address of my second card happens to match exactly the last UUID of some of VMFS volumes section!

    / vmfs/volumes # esxcli list of file system storage

    Mount a Volume mounted UUID Type size free name

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

    / vmfs/volumes/524f80a6-f18c10c7-2 c 16-001e4f204bc4 invited true VMFS of the 524f80a6-f18c10c7-16-001e4f204bc4-5 1999038840832 2 c 1153078132736

    swap/vmfs/volumes/5250f9ba-1c2084a1-ccc8-001e4f204bc4 5250f9ba-1c2084a1-ccc8-001e4f204bc4 true VMFS-5 493384368128 492335792128

    / vmfs/volumes/52583d 27-570697be-161 b - 001e4f204bc4 52583 d 27-570697be-161 b - real 001e4f204bc4 4293591040 4161273856 vfat

    / vmfs/volumes/d789b775-b425486f-ac6f-1a3cee25ec3d d789b775-b425486f-ac6f-1a3cee25ec3d true 261853184 13754368 vfat

    / vmfs/volumes/492adf74-59b63f60-76FA-01385be4c120 492adf74-59b63f60-76fa-01385be4c120 true 261853184 97005568 vfat

    / vmfs/volumes/506469eb-d746eb51-3D 506469eb-d746eb51 - 3 d 04-001e4f204bc4 04-001e4f204bc4 true 299712512 99147776 vfat

    If the NIC information above seem to be a loophole... and the owner of the directory in question seems to be simply the volume itself (?)

    I'm worried because not only I want to remove this file from my store of data (or at least understand the need for it), but because of the small cryptic information that I can see so far I don't think that sounds a coredump is / was being created.

    To the best of my knowledge, this system has no other problems, it starts very well and apart from some other errors not apparent, miners, I saw in newspapers, I know not what could be the cause.

    Advice is very welcome as to what is happening!

    Yes NightWing... the coredump file is 5.5

    Size of the system increases lead to larger ESXi unannounced dumps core. The partition of coredump for new installations of ESXi 5.5 is 2.5 GB. For upgrades from previous versions of ESXi 5.5, the core dump partition is limited to 100 MB for ESXi crashes. For many large systems, this limit is not enough space and dump logs are truncated. The limit has an impact on the ability of triage ESXi system issues and the core.

    Updates with limits on partitions of 100 MB, during the boot process, the system might create a dump file. If it does not create a dump file, you can create it manually with the command of file coredump esxcli system.

    The partition which added isn't the vmfs partition, but since the partition created during installation esxi coredump.

    No, you can not have created /vmkdump if you do not have a coredump in vmfs.

    If you think, that your esxi broke down somewhere, look at/var/core... If any coredump is, your Inbox may have thrown some time, otherwise you're good to go.

    In addition, in the case of vmfs partition coredump configured, once you have deleted the file, a new file will be in place if and only if your box has panicked and dumped core.

    Documentation Centre of vSphere 5.5

  • Repair / recover VMFS Volume

    I have a situation where someone had vSphere 4.x older glomerulus. Virtual machines have been welcomed to a rheostat of SAN iSCSI for the nodes in the cluster.  Volume was initially 260 GB when I did a few years ago.   Later, they added enough VMs they needed to expand.  They have developed the ability of LUN to 3 TB, but has never been able to extend the partition.   It's a problem with VMFS3.

    Seems if you epand the LUN, EVEN IF you NEVER develop the score, your systems, if they disassemble the volume can never stand again.

    These are apparently for some time where over time systems more wouldn't have 'access' on MON... and after a power outage, no system could then access dozens of virtual machines.

    Now I need to find a way to mount this 3 TB iSCSI LUN, even if read-only long enough to mount the virtual machines off of it to the NFS share 260 I ready.

    Goal: map iSCSI LUNS on Windows / Linux system.  Turn up the volume of RO.  Copy NFS export data. Destroy and rebuild the data on the new lun VMFS5 iSCI.

    I can mount the LUNS to the CENTOS system and parted shows the 3 TB LUN but only 260 GB primary partition.  So, I see the data as expected.   "Now, I tried to compile ' vmfs-tools - 0.2.5 ', but the compiler errors.  Nothing of any help or comments. I've tried ubuntu and CENTOS48 too and mistakes not much help.

    Is their path another, simpler to get this accomplished?

    Thank you

    If ESXi cannot see content any volumes VMFS - try Linux vmfs-tools - he often sees more.
    Try the LiveCD I do - there last vmfs-tools batim.

    Cut the flat.vmdks is possible but only worth trying if:

    1. you have good reasons to assume that the flat.vmdk was written in a single fragment
    2. the vmdk was thick provsioned (greedy zero works best)
    3. you can provide specific details on the structure of the disc of the lost flat.vmdk

  • After integrated error of VMFS volumes

    Hello

    I have a 5.5 installed on Dell PowerEdge T110 2 ESXi which worked well. I decided to migrate to 6.0, but in case of a problem, I made a clone of my records. During the clone, I had a built-in long and the UPS has been unable to support, and now I cannot start the system and cannot be updated.

    If I try to boot ESXi 5.5 I got an error:

    Error loading misc_dri.v00

    If I start the update with the ISO burned, I got:

    The selected disk has a VMFS volume, which can not be scanned. It may be damaged or disconnected. Please select another disk or fix the problem.

    So I thought I'd start with 5.5 ESXi ISO to fix the system, but I got this error:

    The system has found a problem on your machine and cannot continue.

    Cannot load multiboot module: invalid parameter.


    I also tried to burn 2 times each ISO for you ensure that they are not broken but doesn't change anything.

    I don't see anything on the forum to help me, maybe I missed something?

    Also, I've migrated front of 5.1 to 5.5 and worked well. If I restore the 5.1 system, do I loss my VMs?

    Thanks for help

    I would try a new installation of a key to 16 GB + USB or SD card, first of all and then try to add the data store. Follow this KB: VMware KB: installing ESXi 5.x on a USB flash drive or SD flash card support looks like your least partner/OEM support (DELL) storage controller, and you need the drivers for it.

    If the data store is mounted with this temporary system first of all, I would like to make a backup of all your virtual machines, otherwise you can try to fix it.

  • vmfs volume online

    Thank you for all your help.

    I have a volume VMFS with 200G and 1 virtual machine running on it, I want to develop by:

    -increase the size of the lun to storage san to 500G

    -extend this VMFS to 300G of vcentre.

    Is it safe to do online extend VMFS when the virtual machine is running?

    The comments on this VMFS VM config:

    -Windows 2008

    - c:\ 30 GB

    - d:\ 160 GB

    After developing the VMFS, I will be the drive D:\ this 160 GB to 300 GB virtual machine, which means that the vmdk file will be 300G.

    My question is that vmdk will growth to 300 GB across the old size vmfs and the new vmfs size 300 GB, questions about this scenario?

    That is, can the vmdk expand the size and use on a VMFS keys expanded?

    Thank you

    Patrick

    Hi Patrick,

    Is it safe to do online extend VMFS when the virtual machine is running?

    No Yes No worries on that.

    After developing the VMFS, I will be the drive D:\ this 160 GB to 300 GB virtual machine, which means that the vmdk file will be 300G.

    My question is that vmdk will growth to 300 GB across the old size vmfs and the new vmfs size 300 GB, questions about this scenario?

    That is, can the vmdk expand the size and use on a VMFS keys expanded?

    After you develop the VMFS, your host will see a single 500 GB data store. If you can develop your vmdk to 300 GB without problem.

    To expand your vmdk, just right click on your vm--> 'Change the setting'--> select your hard drive--> and type the new size. Then, in your guest OS expand your partition.

    Kind regards

    Julien.

  • How to extend your VMFS on Esxi host capacity

    I have an IBM X 3650. I originally had 3 discs with a RAID5. This host machine running 2 servers virtuial. We decided to add 2 virtual servers on that host computer and increase memory, HD capability and add an additional processor. Everything goes well until I tried to understand how to develop a data store on the host computer.

    I have setup a test machine (very similar to the production host same controller raid, same type of machine) to play with trying to figure this out without screwing up my production box. I found mutiple documentation for older versions and some esxi4.1, but nothing that helps me. I am very new to VmWare. I have the camera showing a capacity of 1.09 TB but the VMFS volume shows 830,52 GB. I will be happy to provide you with all the necessary information to help get this resolved.

    Welcome to the community,

    There are a few descriptions on how to extend the local VMFS data store. My favorite is http://deinoscloud.wordpress.com/2010/05/03/how-to-increase-the-size-of-a-local-datastore-on-an-esxi4/ , as he explained the steps in detail.

    The article assumes that you already added the new capacity of disks / on the existing game/logical RAID drive.

    André

  • VMFS volumes

    I use Virtual Center 2.5 with four ESX host in the same cluster. Through WinSCP, when I browse to the directory vmfs\volumes on the ESX host all it shows me all the files LUN that has a small black arrow. Does this mean that these folders are shortcuts that point to my CX 300 fibre channel storage array? My ESX servers have only 130 GB of total space so I know that it cannot contain information logic unit number. I boot from SAN and are all VMDK on the SAN. I'm guessing that they are shortcuts pointing to my SAN. Is this correct?

    Thank you

    Hello

    Yes, I think you're right, these shortcuts are your warehouses data pointing back to the LUNS on your CX300.

    I see the same thing using Veeam FASTSCP.

    Alex

  • "Windows cannot display the control volume on the taskbar because the Volume control program has not been installed. To install it use Add/Remove programs in Control Panel. »

    missing volume control

    volume control was gone. I tried to go into my control panel to use it, but I get an error that says:

    "Windows cannot display the control volume on the taskbar because the Volume control program has not been installed. To install it use Add/Remove programs in Control Panel. »

    I have lost my Windows XP disc in a move and can't reinstall the file to a disk, how to fix this?

    When you use certain features sounds and Audio devices, you see a message like this:

    Windows cannot display the control of volume on the taskbar because the Volume control program has not been installed. To install it use Add/Remove programs in Control Panel.

    It seems that the c:\windows\system32\sndvol32.exe file is missing.

    This may occur if your antivirus/antimalware application thinks the file is suspicious and quarantines (effectively delete) the file.  You can replace the missing file with a backup copy of the file that is in another folder on your system.

    Describe your current antivirus and software anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc..

    Assuming that Windows is installed on your C drive...

    We know that XP keeps copies of critical system files in the following folder:

    c:\Windows\System32\dllcache

    Using the Explorer, search for or navigate to the following folder:

    c:\Windows\System32\dllcache

    Locate the sndvol32.exe file, right-click, choose copy (it copies the file to the Windows Clipboard).

    If your Solution Explorer settings are not set to display file extensions, you will see only a file called 'sndvol32' which has an icon that looks like to the volume control slider (this is the file you need).

    If the file is missing in the dllcache folder, look for a copy of the file in this folder:

    c:\windows\ServicePackFiles\i386

    Browsing from a level in the following folder:

    c:\Windows\System32

    Right-click on an empty area in the window of c:\windows\system32 and choose Paste to paste in the missing file where it belongs.

    Answered in the affirmative if invited to replace the existing file.

    Now try your features sounds and Audio devices.

    Note that run sfc/scannow will not replace the missing file because it is not this that sfc/scannow does.

  • Diskpart.exe not extending XP SP3 volume

    I have an old computer with a hard drive that had been partitioned.  The operating system (XP SP3) is on the C: drive, but the C: drive has been allocated only 10 GB on a hard disk of 120 GB.  I deleted the D: partition and made unallocated space, but Diskpart still will not extend the C: drive at all.
    According to the MS website, Diskpart will not extend a volume on a dynamic disk in XP, only a basic disk.  So I checked C: is formatted as a basic disk.  Then, I did all the other disk unallocated space partition and reformatted it as a basic disk.  Then I deleted the partition and once again tried to extend C:.  DiskPart extend yet not the volume, even following the instructions of Diskpart explicitly.
    So, I am now considering making one unallocated space partition again, and then ghosts the c: on the new partition and delete the c: drive.  There are no programs other than the operating system on the C: drive, worth the savings.
    I'm trying to make the usable hard drive, so I can sell this computer.
    Another way I can try to extend the C: volume on the entire disk?
    Is my drive ghost idea worth?

    There are several third-party utilities that can either clone a partition with the same size or larger large size partition (see, for example, http://www.todo-backup.com/products/features/partition-clone.htm).  If you did that, then Yes, you could swap in the new drive and abandon the old disk or wipe, reformat and use it for a backup somewhere drive.

    There are also several score of third-party application manager that will allows to extend system partition / boot in the adjacent free space.  See, for example, http://www.partition-tool.com/easeus-partition-manager/features.htm (this app has two benefits: it's free and it is also able to do a cloning operation if you prefer).

  • Cannot run chkdsk - Chkdsk cannot run because the volume is in use by another process.

    original title: can I run chkdsk on win xp home, but when I try to use switches, I get cannot lock the current drive. Chkdsk cannot run because the volume is in use by another process. HELP PLEASE

    I run chkdsk without switches on win xp home. I told myself I file error and to set running chkdsk with /f. but when I try, I get the cannot lock the drive, chkdsk may not run because ect...  I tried in safe mode, same thing. I sfc/scannow, but it has not fixed the problem files. help please

    It's normal.  You can not run a check disk on your system disk because your system is to use.  The Message you get should ask you if you want to run it at the next reboot.  You must answer 'Yes' to this message, and then restart your computer.  A disk check should take place as it is restarted.

    FYI: A check disk can take hours if you have a large drive or there are a lot of problems on the disc and you cannot use your machine while the scan is in progress.  Better to operate during the night.  Also, I got checkdsk completely erase the hard disk to the point where the only option was to reformat and reinstall Windows.  Make sure that your data available are well-supported before running Chkdsk.

    "How to perform disk error in Windows XP check"
      <>http://support.Microsoft.com/kb/315265 >

    HTH,
    JW

  • Chkdsk cannot run because the volume is in use by another process

    My computer was working fine until last night. Now when I connect I get a blue screen saying that the computer shuts down to prevent further damage from happening. I tried to restore to an earlier point in time when my computer was working but then I get the error:

    The OS disk (C :) has errors.
    Windows has detected corruption on OS (C :) file system. You should check the drive for errors before you can restore it.

    So I'm going to run the chkdsk utility, and I get the error:
    Chkdsk cannot run because the volume is in use by another process. You want to schedule this volume to check the next time the system restarts.

    I'm confused because the chkdsk unility usually works, and I have no idea why she is being used by another process. I am clearly not very good with computers. I tend to do a lot of spywear and adwear on my computer. I have Spyware Doctor that removes any infection.

    Help, please. I've tried everything. Thank you.

    Asha22,
    It appears from your last post why chkdsk did not run on reboot and you gave an incorrect message is that you did not a space between the volume and the f number.  The correct syntax is:

    CHKDSK c: /f

    You can also run the utility disc in this way:
    http://windowshelp.Microsoft.com/Windows/en-us/help/bc1393cf-9f9c-79C7-0f91-9337c2c41f811033.mspx

    1. open the computer by clicking the Start button, click computer.
     
    2. right click on the hard drive you want to check, and then click Properties.
     
    3. click on the Tools tab and then, under check for errors, click check now.  If you are prompted for an administrator password or a confirmation, type the password or provide confirmation.

    To automatically repair problems with files and folders that the scan detects, select automatically fix file system errors. Otherwise, the disk check will simply report a problem, but not to fix them.

    To perform a full disk check, select search and attempt to recover bad sectors. This scan is trying to find and repair physical errors on the hard drive itself, and it may take much longer to complete.

    To check for errors file and the physical errors, select both automatically fix errors in file system and search for and attempt recovery of bad sectors.
     
    4. click on start.
     
    Depending on the size of your hard disk, this may take several minutes. For best results, do not use your computer for any other tasks while it checks errors.

    Note: If you select automatically errors in file system of fix for a disc that is used (for example, the partition that contains Windows), you will need to reschedule the disk check for the next time you restart your computer.

    The reason that it says that the disk is in use by another process is because it is in use by the operating system (Vista), and that's why it must be run at startup, before the operating system loads fully.

    Another utility, you need to perform is the System File Checker, if you can get your computer to start, either normally or in Mode without failure.
    To run the System File Checker tool, follow these steps:
    Click Start and type cmd in the box start the search.
    Right click on cmd in the list programs, and then click Run as administrator.
    If you are prompted for an administrator password or a confirmation, type your password or click on continue
    At the command prompt, type the following line and press ENTER:
    sfc/scannow
    When the analysis is complete, test to see if the problem you are experiencing is resolved.

    Let us know what these tests are and how we can also provide assistance.
    Thank you

    Gloria
    Microsoft Answers Support Engineer
    Visit our Microsoft answers feedback Forum and let us know what you think.

  • Reinstalled Vista, now it cannot find a system volume that meets the criteria for installation

    OK, I caught a virus really bad and had to reinstall vista.  I have 4 hard drives on my computer. When I was going to do a fresh stall of my cd of Vista 64-bit, the first thing I did was to reformatt all my hard drives but the one with the files I wanted to save on this. Now, the problem comes when I try to select a hard drive to install vista, I get a message that says "windows cannot find a system volume that meets its criteria for installation"!  I get this message on each of the hard drives that I tried to install it.  These are the same drives exact I had at first and installed vista on several times before with no problems.  I even deleted the drives and tried repartioning them and always got the same message. Help, please!

    OK, for anyone else who might encounter this problem, the solution is to disconnect all but one of the drives that you want on your computer.  Make sure you leave the one you want installed on connected windows and then do the installation. Subsequently, you can reconnect to the rest of your hard drives. !

  • When you try to run chkdsk, it tells me which cannot be executed, the Volume is in use by another process, but trying to run at startup, I am told that the chkdsk command has been cancelled

    When you try to run chkdsk, it tells me which cannot be executed, the Volume is in use by another process, but trying to run at startup, I am told that the chkdsk command has been cancelled. message also indicates that there are errors.  How can I me then chkdsk to run

    Hello

    See if these two tutorials to help you with this.

    "How to run the check disk at startup in Vista or Windows 7"

    http://www.Vistax64.com/tutorials/67612-check-disk-Chkdsk.html

    "How to difficulty Chkdsk will not run at startup in Vista"

    http://www.Vistax64.com/tutorials/130824-CHKDSK-will-not-run-startup-Vista.html

    See you soon.

  • Discs of ESXi supports local (UFS) as a Volume/vmfs/volumes - didn't want not!

    Hi all

    Updated from 5.5U2 to 6.0

    A race of NAS VM using two disks using RDM (virtual) to get direct access to disks and smart State - created with the flag - z.

    After the upgrade to 6.0, ESXi now mounted (s?) drive - which are SoftRAID(4) 1 and have a file system UFS - to/vmfs/volumes/sink. This happened only after the second start, but now there is no way back for me.

    After the first reboot after upgrade, I was able to assign the disks to a virtual computer and restart it. On the next reboot, the problem above has occurred.

    Perhaps interesting to note that the volume is not mounted as a VMFS storage (at least it seems), but directly in the folder/vmfs volumes - and it is not a symbolic link like usual data warehouses.

    Tried Altready:

    / recreate the files with vmkfstools RDM

    Unmount the volume/vmfs/volumes/disassemble sink via esxcli file storage system (using all the u/n/p options, but ESXi said he "can not find the nas drive", which is not really sense)

    There is a thread on serverfault (not mine) with the same problem and similar details.

    VMware - 6.0 ESXi RDM mounting as local volume - Super user

    For the moment, I went down to 5.5u2 to access the virtual machine to work.

    Any help is appreciated.

    See you soon

    IAM

    It is possible to blacklist the ufs module with the following command to esxcli, and won't automount in volumes of ufs. the host reboot is required

    $ esxcli system module set m eggs e fake

Maybe you are looking for