Local cache cannot be seen on local disk after reboot.

In general the important thing to check in local cache problems is the ability to see the local disk.  Make sure that the local disk is formatted and has a drive letter assigned. You can do this either from a local OS or you can boot to a vDisk in standard image mode.  Once the drive is formatted and has a drive letter you should be all set. 

Disk can be moved from system to system as long as the local OS can see the file system. The one problem that you may encounter is that in 2003 server Enterprise edition, auto-mounting of volumes is disabled by default. (http://support.microsoft.com/kb/834911/en-us )

Assigning a drive letter is done by the auto-mounting process.  This is controlled by the registry.  On dynamic disks, behavor changed from Windows 2000 to Server 2003.  The  NoAutoMount key can be controlled by GPO as well.  Auto-mounting can be re-enabled using the command "mountvol /E"

Microsoft reference:

Drive letters are not automatically assigned to dynamic volumes in Windows Server 2003

function loadTOCNode(){}

Article ID : 867819
Last Review : February 6, 2007
Revision : 2.4

INTRODUCTION

loadTOCNode(1, 'summary');

This article describes a behavior in Microsoft Windows Server 2003 where a drive letter is not automatically assigned to a dynamic volume that you create or you mount.

Back to the top

MORE INFORMATION

loadTOCNode(1, 'moreinformation');

When you create a new dynamic volume in Windows Server 2003, or when you mount a dynamic volume in Windows Server 2003, a drive letter is not automatically assigned to the volume. You must explicitly assign a drive letter to the volume.

This behavior occurs because in Windows Server 2003, the NO_DRIVELETTER volume attribute is set to Yes on all dynamic volumes. You cannot clear or set this attribute in Windows Server 2003.

The NO_DRIVELETTER attribute is set on dynamic volumes because the NoAutoMount registry value does not affect dynamic volumes. Therefore, if the NO_DRIVELETTER attribute was not set for dynamic volumes, a dynamic volume would have a drive letter assigned when that volume was auto-mounted. This behavior would affect technologies such as storage area networks (SANs). The NoAutoMount registry value does work for basic disks.

Back to the top

In Windows Server 2003, the NO_DRIVELETTER attribute is set as follows:
On a dynamic volume, the NO_DRIVELETTER attribute is always set.
For a GUID partition table (GPT) basic disk, the NO_DRIVELETTER attribute is set at the time of volume creation. This attribute is then turned on or off when drive letters are assigned to the volume or removed from the volume.
For a master boot record (MBR) partition table basic disk, the NO_DRIVELETTER attribute is not set when the volume is created. However, in this scenario, a drive letter is not assigned to the volume because the Virtual Disk Service (VDS) removes the automatically-assigned drive letter when the VDS receives the volume device arrival notification from the Windows Plug and Play component.

The NO_DRIVELETTER attribute is not turned on or off on a MBR basic disk when drive letters are assigned to the volume or removed from the volume. In this scenario, the NO_DRIVELETTER attribute is only changed when the SetFlags function or the ClearFlags function is called. The NO_DRIVELETTER attribute is applied to all the volumes on the hard disk at the next volume restart. • For a MBR or GPT dynamic disk, NO_DRIVELETTER attribute is always set.

Microsoft Windows 2000 automatically assigns drive letters to dynamic volumes. However, the Windows code was changed in Windows Server 2003 and in Microsoft Windows XP so that Windows does not automatically assign drive letters to dynamic volumes. This code change is intended to improve support for storage area networks (SANs).

You can assign a drive letter to a volume by using the Disk Management snap-in in Windows Server 2003 or by using the diskpart command. For additional information about how to assign a drive letter in Windows Server 2003, visit the following Microsoft Web site:

For additional information, visit the following Microsoft Web site:

Back to the top


APPLIES TO
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Web Edition
Windows Server 2008 Datacenter without Hyper-V
Windows Server 2008 Enterprise without Hyper-V
Windows Server 2008 for
Itanium-Based Systems
Windows Server 2008 Standard without Hyper-V
Windows Server 2008 Datacenter
Windows Server 2008 Enterprise
Windows Server 2008 Standard
Windows Web Server 2008

Back to the top

Keywords: 
kbhowto kbinfo kbfilesystems kbdiskmemory KB867819

 

 



Primary links

Custom Search

Who's new

  • Rullydery
  • eagenorce
  • rittaarier
  • swasseZex
  • gaterfoko

Who's online

There are currently 0 users and 4 guests online.

KrissysCorner.com RuthSwensonLaw.com CreativeLizardProductions.com

DISCLAIMER:

None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no way, shape, or form answerable to anyone for any consequences arising from the aforementioned or indeed any other actions, similar or otherwise, because it was not us that did, or did not do anything. It is not even remotely our fault, and we are in no way prepared or willing to accept any liability, not even slightly, ever. We are, in fact completely and utterly blameless, in that it is definitely not our concern, and no blame can possibly be laid at our doorstep, even if we had one, the possession of which we hereby reserve as being entirely our own free choice. The onus is not on us at all, and furthermore, never has been. The entire matter is wholly beyond our control, and completely out of our hands, each of which are washed scrupulously clean of the whole business. We are not accountable for anything at all, and we hereby categorically deny all responsibility for all that has ever, or will ever happen. Our innocence is therefore wholly beyond doubt and absolutely unimpeachable, and so cannot, under even the remotest or unlikeliest circumstances, be brought into question. By clicking either on a link on this site, clicking on a link that leads to this site, or by arriving at this site by natural or supernatural means, you are in effect accepting responsibility for the fact that it is all entirely your own fault, down to the most miniscule detail, and that you are wholly accountable for whatever outcome may arise as a consequence of the aforementioned action or actions insofar as they were undertaken personally by you on an entirely voluntary basis and without any persuasion, coercion or influence from any party or parties other than yourself. Don't come sniveling to us, we are only figments of your imagination. I also agree that if I am ever with a contributor to this website during mealtimes I agree to pay for any super-sizing of their meal, or at least a nice dessert or one of those foo-foo drinks with an umbrella or a monkey. By admitting to have seen the worthless spineless drivel on this website (also known as content)

I Agree Wholeheartedly and Without Reservation to the above. (Except maybe for that part about the monkey.)

All Your Base Are Belong To Us.

Soylent Green Is People!

Never make a bet with a Sicilian when Death is on the Line!

No. Really, I do agree.