FishCustard Posted September 17, 2013 Posted September 17, 2013 I'm currently setting up a new server - I want one RAID volume to contain the OS (Server 2012) and another volume for data (backups). The data volume is just over 4 TB. I created both volumes in the pre-boot RAID config menu (it's an HP ProLiant DL580 G5 server with the HP P400 card) and installed Windows, but the installer in its infinite wisdom shoved the 350 MB system reserved partition onto the data volume, which meant I couldn't convert it to GPT. So, I then deleted the 4 TB volume and reinstalled with just the small disk online. Everything OK, so I reboot and recreate the large volume. Now, the sodding thing refuses to boot from the RAID controller, as if there's no OS installed at all! Surely creating another logical volume shouldn't affect the first? Am I being an idiot? Either way, how do I achieve what I'm after? Thanks!
DMcCoy Posted September 17, 2013 Posted September 17, 2013 (edited) If the Windows installer put it's system partition on the data drive, that's where the boot sector went. You deleted it. Windows doesn't always detect the drive order the way you expect, disk 0 is where the system partition and boot go. Edited September 17, 2013 by DMcCoy
FishCustard Posted September 17, 2013 Author Posted September 17, 2013 No, I deleted the volume, kept it deleted (so there was just the small volume online) while I reinstalled Windows. Then I recreated the large drive, which would be completely blank. Sorry if that wasn't clear.
DMcCoy Posted September 17, 2013 Posted September 17, 2013 (edited) Seen next Edited September 17, 2013 by DMcCoy
DMcCoy Posted September 17, 2013 Posted September 17, 2013 Hmm, reading again more carefully you still have two *RAID* volumes say RAID-A I assume less than 2TB for boot (MBR) RAID-B I assume more than 2TB for data (GPT) Make sure the P400 has the right boot volume Make sure that windows installer (Shift F10, diskpart, list disks) shows Disk 0 as the boot volume. It *is* possible for the install to create both the system partition and windows volume on one drive, while placing *only* the boot MBR on another disk, although it doesn't happen often. I suspect the installer is seeing the volumes the wrong way round and making the data drive the active one. 1
FishCustard Posted September 17, 2013 Author Posted September 17, 2013 I'll check which volume is active tomorrow, thanks.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now