08-24-2020 03:49 AM
Hi,
I'm trying to create a raid1 config on an UCS managed C240M5 server with 240GB SATA M.2 disks.
I have done the same as described in this thread:
But when I apply my service profile to a rack server, I get an error that RAID mode needs a key.
Has anyone been able to create a raid1 config on m.2 sata disks used for ESXi boot?
Best Regards
Bo
Solved! Go to Solution.
08-24-2020 04:56 AM - edited 08-25-2020 09:49 AM
Greetings.
When you are creating a Disk Group Policy,
make sure you are using following options:
Disk Group Policy name=YOURM2Name
"Raid 1 Mirrored"
"Disk Group configuration (Manual)"
+Add, use slot 253
+Add, use slot 254
Create Storage Profile
+ Add (under Local LUNs)
Give LUN a name
Set the size to 1
Fractional size to 0
Expand to Available
Select Disk Group Configuration (drop down, pick your YOURM2Name)
Reference this Storage Profile, within your Service Profile.
See https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt63621
Thanks,
Kirk...
08-24-2020 04:56 AM - edited 08-25-2020 09:49 AM
Greetings.
When you are creating a Disk Group Policy,
make sure you are using following options:
Disk Group Policy name=YOURM2Name
"Raid 1 Mirrored"
"Disk Group configuration (Manual)"
+Add, use slot 253
+Add, use slot 254
Create Storage Profile
+ Add (under Local LUNs)
Give LUN a name
Set the size to 1
Fractional size to 0
Expand to Available
Select Disk Group Configuration (drop down, pick your YOURM2Name)
Reference this Storage Profile, within your Service Profile.
See https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt63621
Thanks,
Kirk...
08-24-2020 06:08 AM
Thanks,
I changed the disk group policy to a Manual disk group configuration, and that cleared most of the warnings.
Unfortunately I still get's an warning regarding the raid key:
Regards Bo
08-24-2020 06:46 AM
Have only seen that error when related to this defect:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt63621
Can you try the workaround or upgrade to a fixed release and see if the issue persist?
08-24-2020 06:54 AM
Yes, I have tried to add the diag boot policy, but still get's the same warning.
I will see if I can schedule an UCSM upgrade later this week.
08-25-2020 07:31 AM
Hi again,
We upgraded to 4.1.2a and that solved the problem.
Thanks for your help to both of you.
Regards Bo
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide