Unsolved
This post is more than 5 years old
2 Posts
0
32856
January 4th, 2014 05:00
PowerEdge T410, Perc H700, RAID-5, Issues after installing operation system on RAID array
Greetings,
We are using PowerEdge T410. Recently we had to reinstall operation system as well as replacing RAID-5 array for a bigger hard drives after all.
Used 4x 3TB WD red hard drives for RAID-5 configuration.
Went for CTRL+R configured raid array, left most setting by default. Fast Initialization was running on background.
Appeared one virtual drive with ~8.3TB free space.
Next move was to insert Windows Server 2012 DVD and install OS. When I was promted to choose a drive to install I cut 120 GB from RAID-5 and installed OS.
Currenly, after all the updates, windows as well as updates for Dell server - in Disk management I can only see 120 GB disk C, 1.8TB unallocated drive and ~6.3TB unallocated drive.
Apparently MBR partition can't be bigger than 2TB, so during OS installation it cut 2TB space and automatically split it for a boot drive where OS is installed and unallocated drive with 1.8TB.
I waited until initialization is over for raid array(thought that was the reason), but still can't do anything with ~6.3TB unallocated space.
Other words instead of having ~8.3TB raid-5 array I am having disk C with 120GB, ~1.8TB unallocated space(which I can assign a letter and work with), and ~6.3TB which I can't modify in anyway - can't assign a letter or do anything else with it.
Attaching screenshot.
Would be more than grateful to have any assistance with this issue. There is no important data on drives, so I can easily reinstall everything from the scratch, but I am not sure which changes I must make to be able to enjoy RAID-5 fully after all.
Thank you!
Chernov
2 Posts
0
January 4th, 2014 07:00
*Update*
I recreated RAID array, but this time configured 3 virtual drives in the same RAID-5 array, one with 120GB for system, one 3TB and the rest is 3rd VD.
OS is installed and I am able to add new simple volume on both none system VD's.
I would still like to ask if I need to wait for "background initialization" which shows in OMSA(I did fast one during RAID-5 configuration) or I can just create volumes on VD's and proceed with this server?
Thank you!
*FINAL update*
Assigned new simple volumes on both virtual drives, everything works fine.
Best regards!
theflash1932
11 Legend
•
16.3K Posts
0
January 4th, 2014 18:00
"I would still like to ask if I need to wait for "background initialization" which shows in OMSA(I did fast one during RAID-5 configuration) or I can just create volumes on VD's and proceed with this server?"
Sounds like you should have waited to post in the first place, eh? Well, let me explain WHY what happened happened.
In order to a have a "disk" (not partition) larger than 2TB, it MUST be converted to GPT. Windows cannot boot to a GPT disk unless installed on a UEFI-enabled system.
Options
1. Change boot mode to UEFI, configure one big RAID 5, then install Windows. 2. Keep it in BIOS mode, configure a VD for the OS (less than 2TB), and another VD(s) with the remaining space. There is no [practical] limitation on "disk" size for "data disks".
Each VD (Virtual Disk) on a hardware RAID controller is presented to the OS as a separate disk.
Obviously, you figured this out (you did number 2) ... I just wanted to make sure you understood why it worked.