08-04-2022 09:58 PM
I'm getting no where trying to get this server up and running because I can't find a way to allocate the RAID groups to the locally installed SSD disks.
The server has the following disks in the following order:
Disk | Size (GB) |
1 | 960 |
2 | 960 |
3 | 960 |
4 | 960 |
5 | 960 |
6 | 960 |
7 | 960 |
8 | 960 |
9 | 300 |
10 | 300 |
11 | 240 |
12 | 240 |
13 | 240 |
14 | 240 |
15 | 960 |
16 | 960 |
17 | 960 |
18 | 960 |
I'd like to configure the disks in the following fashion:
Disk | Size (GB) | Desired RAID Group |
1 | 960 | RAID10- DDB |
2 | 960 | RAID10- DDB |
3 | 960 | RAID10- DDB |
4 | 960 | RAID10- DDB |
5 | 960 | RAID10- DDB |
6 | 960 | RAID10- DDB |
7 | 960 | RAID5- Index |
8 | 960 | RAID5- Index |
9 | 300 | RAID1- Boot |
10 | 300 | RAID1- Boot |
11 | 240 | NA |
12 | 240 | NA |
13 | 240 | NA |
14 | 240 | NA |
15 | 960 | RAID5- Index |
16 | 960 | RAID5- Index |
17 | 960 | SPARE |
18 | 960 | SPARE |
When I apply my Service Profile (SP) to the physical server, I get this error:
Failure Reason: There are not enough resources overall
Insufficient disks for the specified raid level
LUN Resource Selection Logs for Service Profile ecmsp09, LUN RAID5-INDX:
Order Description
1 | Disk selection process started for local lun: org-root/org-Dedicated/org-MedAgt/profile-STR-MediaAgnt01/das-scsi-lun-RAID5-INDX |
2 | Try to find out an existing disk group for the new LUN |
3 | Cannot carve out of the existing disk groups. Trying to create a new disk group |
4 | Controller sys/rack-unit-8/board/storage-PCH-7 does not support OOB |
5 | Failed to find sufficient disks |
I don't get it. The disk groups should only use up 12 disks while there are 18 disks in the server.
I then removed the RAID5 disk group from the storage profile, and tried again, and get this error:
Failure Reason: There are not enough resources overall
Insufficient disks for the specified raid level
LUN Resource Selection Logs for Service Profile ecmsp09, LUN RAID10-DDB:
Order Description
1 | Disk selection process started for local lun: org-root/org-Dedicated/org-MedAgt/profile-STR-MediaAgnt01/das-scsi-lun-RAID10-DDB |
2 | Try to find out an existing disk group for the new LUN |
3 | Cannot carve out of the existing disk groups. Trying to create a new disk group |
4 | Controller sys/rack-unit-8/board/storage-PCH-7 does not support OOB |
5 | Failed to find sufficient disks |
My disk groups look like this:
<lstorageDiskGroupConfigPolicy
childAction="deleteNonPresent"
descr="Storage for OS using 2 disks in RAID1"
dn="org-root/disk-group-config-STR-OS-2D-R1"
intId="80455880"
name="STR-OS-2D-R1"
policyLevel="0"
policyOwner="local"
raidLevel="mirror">
<lstorageVirtualDriveDef
accessPolicy="platform-default"
childAction="deleteNonPresent"
driveCache="platform-default"
ioPolicy="platform-default"
readPolicy="platform-default"
rn="virtual-drive-def"
security="no" stripSize="platform-default" writeCachePolicy="platform-default"/>
<lstorageDiskGroupQualifier
childAction="deleteNonPresent"
driveType="SSD"
minDriveSize="290"
numDedHotSpares="unspecified"
numDrives="2"
numGlobHotSpares="unspecified"
rn="disk-group-qual"
useJbodDisks="no"
useRemainingDisks="no"/>
</lstorageDiskGroupConfigPolicy>
<lstorageDiskGroupConfigPolicy
childAction="deleteNonPresent"
descr="Storage Group for RAID10 from 6 disks"
dn="org-root/disk-group-config-STR-DATA-6D-R10"
intId="80711146"
name="STR-DATA-6D-R10"
policyLevel="0"
policyOwner="local"
raidLevel="mirror-stripe">
<lstorageVirtualDriveDef
accessPolicy="platform-default"
childAction="deleteNonPresent"
driveCache="platform-default"
ioPolicy="platform-default"
readPolicy="platform-default"
rn="virtual-drive-def"
security="no"
stripSize="platform-default"
writeCachePolicy="platform-default"/>
<lstorageDiskGroupQualifier
childAction="deleteNonPresent"
driveType="SSD"
minDriveSize="950"
numDedHotSpares="unspecified"
numDrives="6"
numGlobHotSpares="unspecified"
rn="disk-group-qual"
useJbodDisks="no"
useRemainingDisks="no"/>
</lstorageDiskGroupConfigPolicy>
I won't post the RAID5 config unless it's required, but it's a 4x SSD disk RAID5 setup.
I then re-applied the Service Profile using just the "BOOT-R1" & "RAID10-DDB" disk groups and it looks like it would be successful, however it's using the wrong disks for the BOOT LUN:
Service Profile ecmsp09 (org-root/org-Dedicated/org-MedAgt/ls-ecmsp09) [Server: sys/rack-unit-8]
LUN Resource Selection Logs for Service Profile ecmsp09, LUN BOOT-R1:
Order Description
1 | Disk selection process started for local lun: org-root/org-Dedicated/org-MedAgt/profile-STR-MediaAgnt01/das-scsi-lun-BOOT-R1 |
2 | Try to find out an existing disk group for the new LUN |
3 | Cannot carve out of the existing disk groups. Trying to create a new disk group |
4 | Controller sys/rack-unit-8/board/storage-PCH-7 does not support OOB |
5 | Select normal disk in slot: 7 |
6 | Select normal disk in slot: 8 |
LUN Resource Selection Logs for Service Profile ecmsp09, LUN RAID10-DDB:
Order Description
1 | Disk selection process started for local lun: org-root/org-Dedicated/org-MedAgt/profile-STR-MediaAgnt01/das-scsi-lun-RAID10-DDB |
2 | Try to find out an existing disk group for the new LUN |
3 | Cannot carve out of the existing disk groups. Trying to create a new disk group |
4 | Controller sys/rack-unit-8/board/storage-PCH-7 does not support OOB |
5 | Select normal disk in slot: 1 |
6 | Select normal disk in slot: 2 |
7 | Select normal disk in slot: 3 |
8 | Select normal disk in slot: 4 |
9 | Select normal disk in slot: 5 |
10 | Select normal disk in slot: 6 |
Is there a way to achieve the required result?
My last hope will be to go to the datacenter and re-arrange the disk order then modify the disk groups by setting them to "Disck Group Configuration (Manual)" and manually selecting the disk slots to use for each RAID group.
08-04-2022 10:49 PM
- These bug reports might be involved : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuy86027 and or https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvd26834
M.
08-04-2022 11:34 PM
Doesn't look relevant as one talks about creating LUNs using external means and the other is about using PCH controller definitions. But thanks for the info.
08-05-2022 05:35 AM
These UCS errors are very annoying:
There are not enough resources overall
When disks have this error most of the time the disk is NOT in the correct state to be consumed (but doesn't tell you that in the error message).
UCS RAID configuration will only use "Unconfigured Good" disks (but doesn't say that explicitly.)
Usually right-click the individual disks and set to "Unconfigured Good".
Select dedicated hot spares by using the same method as normal disks.
Disks are only selected if they are in an Unconfigured Good state.
Hope that helps.
08-07-2022 05:38 PM
I've found that when working with servers with existing disk configurations, I need to delete the Orphaned LUNs else new Service Profiles will not apply. I have done this with the above server.
I've ensured that all physical disks on the server are in the Unconfigured Good state.
The Disk Groups & Service Profiles apply OK to the servers, as long as I remove the Minimum Drive Size value, however the wrong disks are used for each RAID group.
For now, I've asked the DC team to re-arrange the disks so that the 300GB disks are in slots 1 & 2 and the 960GB in the rest and I'll just create a manual slot assignment in the Disk Group. I don't think there is a way for UCSM to choose the correct disks in this situation!?
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