• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 344
  • Last Modified:

Changing Device ID numbers in Drive Management

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
netfriendsinc
Asked:
netfriendsinc
1 Solution
 
Handy HolderSaggar makers bottom knockerCommented:
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
 
netfriendsincAuthor Commented:
Worked, thanks so much!
0

Featured Post

Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now