1 Rookie
•
41 Posts
0
57
February 28th, 2025 05:43
Problem with Disk Drive Number in Windows because of Dell RAID Controllers , VDisk Numbers
Hello ,
I run in an Problem when i install Windows Server 2025 on an Dell R360 Server with one BOSS Controller with two M.2 480 GB SSDs configured as RAID1 and an additional PERC H755 RAID Controller on which was 4 x 1.2TB SAS Disks configured as RAID5 .
When i first only configure the BOSS Controller to an RAID1 virtual Disk with the two 480 GB M.2 SSDs , which was named 1_SYSTEM and then i install Windows the for now all seems correct .
Under Windows Disk Management my Windows Boot Partition resides on Disk0 . Allright .
But when i at next configure in IDRAC my 2_DATA RAID with the PERC H755 Controller as RAID 5 with the 4 x 1.2 TB SAS Drives then it happens .
The later created DATA Partition grabs in Windows Disk Management the Drive0 and my Windows Boot Disk is now Drive1 .
In the Pictures you can see my Config .
Now my Question , is it a normal behaviour or do i something wrong .
We have to install 30 Servers with this Configuration and i dont want to make an Error .
I want that my Windows Partition still resides on Drive0 .
I try to configure the RAIDs direct over the Lifecycle Controller . No Success .
I try to create the Data RAID first then the SSD Raid for Windows after that. No success .
Can somebody help me .
Michael
DELL-Joey C
Moderator
•
3.9K Posts
0
February 28th, 2025 10:08
Hi,
It seems to be as it is designed in OS architecture. When M.2 SSD is installed, SATA/SAS gets priority in numbering order within Windows OS.