Drive Letter Assignment Problem

 

We have noted an issue in which the Windows operating system assigns a drive letter identical to the one that is already selected for use by the InveStore file system. This results in a failed attempt to start up the InveStore system to a "Ready" state with no other apparent errors.

 

When a new SCSI storage drive device (storage or other) is added to an existing server system, the Windows operating system automatically assigns the next available drive letter to the drive following those of the existing server hard drive(s). This could be the letters "D", "E", "F", "G" etc., depending on how many drives and/or drive partitions are in the Windows server. This causes a drive letter conflict when the Windows OS uses a letter already assigned by the operator within the InveStore console.

 

The typical sequence of events for this problem is as follows:

 

      An existing storage device is used or tested on the Windows storage server. The operator assigns a drive letter via the InveStore console and successfully accesses the device via this letter. (Usually the first available drive letter shown in InveStore list has been selected by the operator in this scenario.)

      After a period of usage, a new SCSI device with additional drives is added to the Windows server SCSI Bus.

      During a restart, if the drives are Storage they are seen by the Windows OS as removable hard drives and drive letters are assigned to each of them regardless of a previous assignment by any other programs, including InveStore.

      Upon an attempt to startup InveStore, there appears to be successful mounting of media but the system fails with the following message:

 

09:55:08 (Help) Volume XXXXX mounted in 120 seconds. <SLOT 1>
09:55:08 (Error) Volume Interface Manager Initialization Failed, rc= 3 (0x0003)
09:55:23 (Info) StartKernel: PDTKRNLE.EXE started, but did not initialize properly
09:55:23 (Info) Unsuccessfully started storage subsystem

 

The Hex error "0x0003" is a "path not found" error. InveStore could not "find" the drive letter path that had been previously selected.

 

When InveStore is started, it will first identify any supported SCSI storage devices attached to the Bus and then mount the existing media in the library. After the media in the library is successfully mounted, the InveStore file system re-assigns the drive letter that has been previously selected by the operator.

 

In this scenario, since the drive letter is now being used by the WINDOWS OS, the InveStore system fails to start to a ready state.

 

To correct his problem, please do the following:

 

      Shutdown the InveStore console screen completely.

      From the Windows Control Panel > Services screen, "Stop" the Pegasus File System (InveStore) Service.

      From the Pegasus InveStore folder on the Start menu, select "Service Uninstall".

      Reboot the server.

      Make sure Windows assignment of storage drive letters is now gone. Look in My Computer or Windows Explorer to make sure they no longer appear.

      Restart InveStore.

      Reassign a new drive letter, such as "O:\" and verify access.

      Re-establish the shares for the new drive letter.

      Shutdown the console and re-install the InveStore Service option.

There may be some instances where the above steps do not correct the problem due to Windows drive assignments. If this should occur, then please do the following:

 

      Shutdown the InveStore console screen completely.

      From the Control Panel > Services screen, "Stop" the InveStore Service.

      From the Pegasus InveStore folder on the Start menu, select "Service Uninstall".

      In the Pegasus InveStore folder select "Uninstall" to uninstall the InveStore program.

      Delete the \PDT directory completely.

      Re-install InveStore.

      Power down the Windows server.

      Power down the storage devices.

      Restart the Windows operating system.

      Make sure Windows assignment of storage drive letters is now gone. Look in My Computer or Windows Explorer to make sure they no longer appear.

      Power on the storage libraries.

      Start up InveStore to a "Ready" state.

      Reassign a new drive letter such as the "O:\" drive and verify access.

      Re-establish the shares for the new drive letter.

      Shutdown the console and re-install the InveStore Service if desired.