Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows NT / Setup / October 2005

Tip: Looking for answers? Try searching our database.

NT4 not retaining drive letter settings

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Paul S. - 11 Oct 2005 22:59 GMT
I assign a secondary IDE drive its letter (the primary drive is a SCSI
drive).  It takes the letter fine, and shows up in explorer.

Then when I reboot, the drive letter is gone again.

This box is is a backup server running NT that was ghosted from the main
server if that matters at all.

Also, the CDROM drive won't keep its drive letter either.

Any help?  Thanks,
Paul
Calvin - 12 Oct 2005 06:27 GMT
Hi Paul,

I've seen this problem before. It is caused by the fact that you have 'ghosted'
the installation of NT from another machine, and that machine had drive letter
assignments already in place.

To elaborate:

When you assign drive letters using Disk Administrator (as opposed to allowing
the 'natural flow' of letters with no overrides) a new key at:

HKEY_LOCAL_MACHINE\SYSTEM\DISK is created.

This contains a series of subkeys in the form:

\Device\CDRom0 = "Letter:"

and a key called 'Information' with binary entry associated with it.

The CDRom drives etc are assigned by the first style of terminology, while hard
disk partitions are stored in the 'Information' key.

The solution to your problem is easy - using RegEdit REMOVE all the subkeys
under the 'DISK' key EXCEPT the (Default) subkey. Then reboot the system - the
drive letter assignments will revert to 'natural flow' letter assignments. If
you now go back in with Disk Administrator and re-assign the drives the way you
want them, the subkeys are re-created, and this time the assignments WILL stick !

BE ADVISED that the system (the partition with NTLDR etc..) and boot (the one
with NTOSKRNL etc...) partitions CANNOT have their drive letters changed or
assigned under normal circumstances. If they are not the correct drive letters
with a 'natural flow' assignment (ie: the order in which drive letters are
assigned if you don't override anything) then removal of the 'Information' key
may result in an unbootable system. There are tricks to change this behaviour to
- but they can be complex and carry an element of risk. Please ask if you need
further information.

Hope this helps.

Calvin.
Jiri Tuma - 12 Oct 2005 19:47 GMT
ALLWAYS backup registry BEFORE manipulating with critical keys!!!

there is an utility in NT resource kit called FTEDIT that is able to remove
"used" letters from DISK key and to keep stripe and volume sets intact. This
utility is also able to reestablish broken volume and stripe sets, if you
know physical order of member partitions and have all of them in order.

If you remove DISK key content, you will LOST all partition sets, so if you
have any stripe, volume or mirror set defined, use only FTEDIT to edit DISK
key and never manipulate it through registry editor. If you have only mirror
set, broke it before ghosting and reestablish after.

Also if you are using ghosting with forced letters, it is good to
incorporate the same NT disk signature to ghosted mirror disk (however it is
better to let an expert to do this, manipulating with critical disk
structures directly is very dangerous!).

> Hi Paul,
>
[quoted text clipped - 36 lines]
>
> Calvin.
Calvin - 12 Oct 2005 23:18 GMT
Hi Jiri,

I should have mentioned that he should backup up the registry keys before
changing/removing them.

I also meant to mention there is a useful article from Mark Russinovich on the
actual structure of the binary 'DISK' key data. Read it here:

http://www.sysinternals.com/Information/DiskKey.html

I was unaware that the FTEDIT utility could manipulate settings not related to
fault tolerant sets - thanks for the tip :-)

Calvin.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.