Solved

Changing Device ID numbers in Drive Management

Posted on 2008-06-13
2
341 Views
Last Modified: 2013-12-05
Orginally I installed 2000server on an HP Proliant ML 570 G4 server along with an MSA60 Storageworks.  There are two internal arrays within the server (2 logical drives) each logical drive is raid 1 and each raid consists of 2 146gb 10k sas drives.  So there is the first array of 146gb, C:\  and the 2nd array of 146gb D:\
The storage works was F:\ at 1.3TB.  A lot of data had been copied to these drives already.  

The server has more memory than the OS can see (8gb), and the PAE switch added to the end of the boot ini file did not work because, as I found out later, 2000 server does not support that, only advanced and 2003 server do.  I then turned the storageworks off, and removed the D:\ array (logical disk 2) from the server and ran the smartinstall disc from HP again.  The only option when installing from the smart disk, is to 'erase all drives and reinstall the os' hence, why i shut down the storage works and physically removed the 2nd logical drive.

Windows advanced server installed fine.  I shut the server down, physically put the 2nd logical drive back in and turned the storageworks on, then turned the server back on.  It booted into windows fine.  I looked at drive management and noticed the C:\ instead of being device 0, is now device 2, and the storageworks is device 0 instead of being device 2.  

Is there a way to change which device is which?  So that the C:\ is once again device 0 and the storage works is device 2?  If a restart is performed it will hang, and the hard drive lights on the storageworks blink furiously.  A hard reboot is required to get it to load back into windows.  
0
Comment
Question by:netfriendsinc
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 55

Accepted Solution

by:
andyalder earned 500 total points
ID: 21793129
I would shutdown, unplug the MSA60, power on, check device numbering is now OK, plug in MSA60 live, rescan disks, check if numbering is still correct, reboot and see if that fixes it. SAS is hot-plug as opposed to the old parallel SCSI which wasn't hotplug by default.
0
 

Author Closing Comment

by:netfriendsinc
ID: 31467123
Worked, thanks so much!
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
Great sound, comfort and fit, excellent build quality, versatility, compatibility. These are just some of the many reasons for choosing a headset from Sennheiser.
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question