Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Int Error 183 - unable to detect windows partition - Volume Manager 2.

Status
Not open for further replies.

StuartMillar

Technical User
Jul 6, 2004
17
GB
Windows 2000 Server (Terminal Services mode)
6 SCSI hdds
On-board SCSI Raid controller Ultra320 (not in use as far as I know, no mirrors)
Volume Manager 2.0 to move EISA partition and extend C: to fill unallocated space.

I have an error when loading Volume Manager:

Int 183
"unable to identify windows partition"

Windows Disk Management clearly shows the C: partition where Windows is installed on as 'basic'. Volume Manager should be able to handle basic partitions, I have no idea why I am getting this error message. Symantec tell me that I have purchased the only product that doesn't include technical support!

Is this occuring because the server is in Terminal Services mode? Do I have to come out of the mode beforehand to use it? Windows Disk Management recognises the drive and their aren't any problems, so whats going on? Formatting the drive is completely out of the question, which is why I bought Volume Manager in the first place, simply to move a partition and resize C:

I am going insane!! Can anyone shed any light on what is happening and any solutions? If I buy technical support from Symantec it will take 3 days to come into affect! Arghh
 
Volume Manager will not work at all because there are dynamic partitions on the server! Big thanks to Symantec for telling me this after buying the product. :>P
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top