Known Issues
and Workarounds for Storage Management Service
With Chinese or Japanese language
browser settings, using the Storage Management Service Advanced Create
Virtual Disk Wizard may occasionally result in text overflowing to
the bottom of the side-by-side blue text boxes.
View slot occupancy report shows
4 HDD slots on backplanes with just two HDD slots for any server.
Physical disk clear operation is not
available on PERC 8, PERC 9, and PERC 10 family of Hardware controllers.
Physical disk properties such as Manufacture
day, Manufacture week, and Manufacture year are available for SAS
drives only.
Creating many sliced span virtual
disks using the spun-down drives through the command line or GUI result
may be delayed.
Workaround: After creating
one sliced span virtual disk, wait for some time to create the next
sliced span virtual disk.
For 14G servers, only two enclosures per controller is supported.
A Security Key Identifier can contain
numerals, lowercase alphabets, uppercase alphabets, nonalphanumeric
characters (except space), or a combination of any of these.
NOTE: If
you have used the special characters ”/” (forward slash) or “ ‘ ”
(single quote) in the Security Key Identifier, they are displayed
as “_” (underscore) on the Change Security Key page and Import Secured
Foreign Configurations page. This is applicable only to the Security
Key Identifier and not to the Passphrase.
If Storage Management displays a path
failure message for a Logical Connector after a reboot, use the
Clear Redundant Path View, provided in the
Change Controller Properties controller task,
and restart the system.
NOTE: Use
this command only if you have intentionally removed the multipath
connection while rebooting the system.
In the VMware ESXi 6.x environment, when you create a virtual disk using Storage Management, you may see an error message
"The task failed to complete: The create virtual disk task was successful but the operating system may not be aware of the
new virtual disk." However, the virtual disk is available for all operations on rebooting the system.
Patrol Read is not supported on SSD
media. The Patrol Read feature fails for any controller that has SSD
media on a virtual disk.
Hot plug of enclosures takes time to
enumerate the enclosure and its components. During this time, there
will be a delay in the response time of tasks, such as displaying
the physical disks on the physical disk page and in the virtual disk
selection page.
All virtual disks from the SAS/iR
controller display the name
IR Virtual Disk on the
Preview page. On successful import,
another name is assigned to these virtual disks and the "IR Virtual
Disk" name is not displayed on the "Preview" page.
Storage Management does not permit
connecting the first enclosure in single path and attaching the subsequent
enclosures in multipath. All enclosures must be connected in multipath
to enable the multipath view.
An error message may not appear when
Import Foreign Configuration task is not successful.
Description: The
Import Foreign Configuration task can only
import virtual disks that have consistent data. A virtual disk with
inconsistent data cannot be imported. When importing multiple virtual
disks in a single operation, however, the
Import
Foreign Configuration
task may report successful completion
even when inconsistent virtual disks are present and have not been
imported successfully.
Solution: If the "Import
Foreign Configuration" task is unable to import an inconsistent virtual
disk, then the physical disks that belong to the virtual disk continue
to display a "Foreign" state after the "Import Foreign Configuration"
task completes. In this case, repeat the "Import Foreign Configuration"
task until one of the following occurs:
There are no longer any physical disks
in
Foreign state after the
Import Foreign
Configuration
task completes.
You receive an error stating that
the
Import Foreign Configuration task has not completed successfully. This error indicates that there
are no longer any consistent virtual disks available to be imported.
Therefore, all virtual disks that are not imported are inconsistent
and you can either perform a
"Clear Foreign Configuration" to
remove the virtual disks or remove the physical disks from the controller.
DF60696 : Storage Management responds slowly when using Internet Explorer 9.x or 10.x on a system with mixed SAS and SATA
physical disks.
Description: When using the "Create Virtual Disk" wizard from the Storage Management graphical user interface (GUI), you may
notice decreased performance when using Internet Explorer 9.x or 10.x on a system with multiple physical disks. The MD1000/MD1400/MD1420
storage enclosures that are heavily populated with mixed SAS and SATA physical disks.
Solution: Use a supported web browser other than Internet Explorer 9.x or 10.x or use the Storage Management command line
interface (CLI) to create the virtual disk. See the Dell EMC OpenManage Server Administrator Release Notes for information
on supported browsers. See the Storage Management online Help or the "Server Administrator Command Line Interface User's Guide"
for information on using the Storage Management CLI.
DF152362: Storage Management
may not display controllers installed with the Service and Diagnostics
utility.
Description: Storage Management
may not recognize devices that are installed after Storage Management
is already running.
Solution: If Storage
Management does not recognize a newly-added device and this problem
has not been corrected with a Global Rescan, then reboot the system.
DF120475: Storage Management
SNMP traps are not filtered by Server Administrator.
Description: Server Administrator
allows you to filter SNMP traps that you do not want to receive. To
implement SNMP trap filtering, select the
System tree >
Alert Management tab >
SNMP Traps subtab. The
SNMP Traps subtab has options for enabling and disabling
SNMP traps based on severity or the component that generates the trap.
Even when the SNMP traps are disabled, Storage Management generates
SNMP traps.
Solution: SNMP trap filtering
will be provided in a future release of Storage Management.
When issuing certain
omconfig
storage
CLI commands with
Power User privileges, the
Error! User has insufficient privileges
to run command: omconfig
message may be displayed. You
must be logged on as an Administrator to perform these actions.
Using the Storage Management Service
Advanced Create Virtual Disk Wizard may occasionally
result in a vertical scrollbar of less than normal width. If this
occurs, resizing the Server Administrator window causes the vertical
scrollbar to be redrawn correctly.
Using the GUI, if a virtual disk
is renamed to a name containing multiple blank and consecutive spaces,
the name is truncated to a single space after
Apply is clicked.
BITS118226: The representation
of NVMe devices residing on backplanes that attach to PCIe Extender
cards is inaccurate on Storage Management. This is because Storage
Management does not have a process to understand the mapping of the
NVMe device, backplane, and the PCIe Extender card. This issue exists
only on PowerEdge R920 servers and does not impact the operations
on the NVMe device. Multiple backplanes on Server Administrator indicate
the presence of multiple PCIe Extender cards on the system.
BITS124349: Firmware version
for SAS 9207_8e, SAS 9206_16e, and SAS 9300_8e, will not be displayed
on the Storage Management GUI and CLI.
BITS123999: SAS 9300_8e is
not supported on systems running the VMware ESXi operating system.
BITS128355: The slot occupancy
report displays single backplane ID and backplane name in the Storage
Management GUI and CLI. The physical disk slot occupancy report for
PCIe Subsystem displays NVMe devices present in two different PCIe
backplanes under the same PCIe backplane on PowerEdge R920 servers.
The NVMe devices connected to different PCIe backplanes are displayed
correctly under
Storage >
PCIe-SSD Subsystem >
PCIe-SSD Extender >
Enclosure.
BITS146054: The enclosure
automatically sets the critical and default warning thresholds. The
user cannot set or reset any warning threshold to any temperature
probe through the Storage Management GUI or CLI.
On a PowerEdge server with maximum
configuration of 8 populated enclosures connected to the PERC hardware
controller, the user can experience a delay in response. When Server
Administrator storage commands such as Create Virtual Disk or Start
check consistency are run, the delay in response can range from 10
— 30 minutes.
BITS148893: When creating a
virtual disk on PERC S130 (software RAID) controller, if you do not
select the first option under
Assign Dedicated Hot Spare a message appears:
DHS not assigned to VD. When you create a virtual disk on a software RAID controller using
the
Create Virtual Disk wizard,
the GUI control only verifies the first available option under DHS,
leaving the other options unverified even if it is selected.
Resolution: The Dedicated Hot Spare assignment
can be performed through the following,
System >
Storage >
Controller >
Virtual Disk under the respective
virtual disk Tasks drop-down list, select Tasks
Assign/Unassign
Dedicated Hot Spare
.
BITS161852: The limitation
is observed when two enclosures are connected to two ports of PERC
H830 controller. The limitation is not observed when the enclosures
are connected in a daisy-chain configuration. In the
Create Virtual Disk Advanced Wizard screen,
enclosures and physical disks are listed together. The user must select
only the physical disks and not the enclosures when creating a virtual
disk using the
Advanced Wizard option.
BITS140465: When the user tries
to create another partial virtual disk of any RAID level, on an existing,
but degraded disk group, Storage Management does not allow the user
to perform this action. This limitation occurs because Storage Management
does not support this functionality. However, this limitation is only
observed on certain PERC 9 family of hardware controllers (PERC H330,
H830, and H730).
Workaround: The user can
create a partial virtual disk during system restart using the CTRL+R
configuration utility.
JIT-10452 (BITS236815): Occasionally, the
virtual disk creation process on PERC 9 hardware controllers may fail
on GUI and CLI. Workaround: Restart the server to resolve this issue.
BITS055347: On systems running
the ESXi 5.1 or later operating system, the “Device Name” for all
virtual disks will be displayed as a blank. This is an expected behavior
on systems running the ESXi 5.1 or later operating system.
JIT-8321 (BITS220411): Unable to create
Partial Secure virtual disk using the GUI when all the available SEDs
are selected. This operation will work if any other physical disk,
which is not a part of any virtual disk, is connected.
JIT-11205 (BITS242664): When a physical
disk, which is a part of multiple partial virtual disks, is reinserted
into the system, the status of the partial virtual disks will be displayed
on Storage Management after a short delay.
JIT-8442 (BITS221272): Few enclosure alerts such as Enclosure
power on/off and Fan removal, does not appear if the enclosure
is connected to the server using a SAS 12 Gbps HBA card. Restart
Data Manager Service to update component status.
JIT-15099 (BITS262349): NVMe Slot Occupancy Report for
PCIe SSD displays inaccurate PCIe SSD slot count. The report displays
four PCIe SSD slots instead of two PCIe SSD slots. This issue is
applicable for the Server having less than 4 NVMe slot count, like
M/FC630, M/FC830, M620 and M820 blades.
JIT-10933 (BITS240247): Storage Management does not display
the Device name on a system where there more than 300 virtual disks.
JIT-15612 (BITS264534): If a server has only software RAID
S130 controller (no PERC controllers) and the operating system is
booted through the same controller, the user will not be able to
set the Remaining Rated Write Endurance threshold using the Server
Administrator GUI.
JIT-72304: Able to assign lesser capacity physical disk as a DHS to the virtual disk created with physical disk having higher capacity.
JIT-16919 (BITS270856): On Precision 7910 running a client
operating system (for example, Windows 8.1 x64), the PERC 9.3 driver
version is displayed as outdated and a yellow bang is shown on such
hardware configurations. This issue does not cause any functionality
limitation.
JIT-43557 : In Split Mode, Slot occupancy report displays inaccurate empty slots when there are no drives connected to the backplane.
The report shows the message empty slots interchanged between controller. This issue occurs for the server with no drives
attached to the backplane in split mode only. Slot occupancy report works fine as expected for servers with a minimum of one
drive.
JIT-52091: Cryptographic erase operation might take longer time to be visible in the dropdown list for the ISE Capable SATA SSDs after
this operation is done.
On a PowerEdge server with maximum configuration of 2 populated enclosures connected to the PERC hardware controller, the
user can experience a delay in response.
Unable to create Partial Secure virtual disk using the GUI when all the available SEDs are selected. This operation will
work if any other physical disk, which is not a part of any virtual disk, is connected.
JIT-58147: In the BOSS-S1 controller properties, slot ID is displayed as "Embedded".
If the background IO is in progress, "Prepare to Remove" operation for the NVME devices might fail.
From 14G onwards, no Channel/Connector information will be displayed under “PCIe SSD Subsystem”. Enclosure/Backplane will
be directly connected to the “PCIe SSD Subsystem”. There is no change in the display of “NVMe Devices ( Arraydisk ) and
Add-On Card ( HHHL Card )”. NVMe Devices ( Arraydisk ) will be displayed under “Enclosure / Backplane” whereas Add-On Card
( HHHL Card ) will be displayed under “PCIe SSD Subsystem”.
JIT-60971 : In OMSA, the empty slots in slot-occupancy report is not displayed after "prepare to remove" operation is performed on
the servers with one or more PCIe Backplane.
JIT-61216 : Unable to create virtual disks (Raid 0, 1, 5) using Advanced Wizard if NVME add in card is present
Description: In PERC S140 advanced wizard, virtual disk creation fails if a combination of NVMe and HHHL addin cards(AIC)
are present.
This issue is observed if the PCI slot ID of the add-in card (AIC) matches with the NVMe drive slot number. However, if
only NVMe drives are used, you can successfully create the virtual disks. This is because the GUI code is unable to differentiate
the slot ID/number in Create Virtual Disks Advanced Wizard.
NOTE: This issue does not cause any data loss. The RAID-5 on S140 with NVMe drives is not supported.
Solution: To resolve this issue, you can create a virtual disk using the Create Virtual Disks Express Wizard and OM-CLI.
JIT-63561 : In Dell’s 14th generation of PowerEdge servers, while doing the "Reconfiguration" operation, "Auto Configure RAID0"
option is listed in OMSA under H730P controller's "Available tasks". It happens during RAID level migration from RAID1
to RAID0.
JIT-71918: On 14th generation of PowerEdge servers when connected with two SAS 12Gbps controllers in Slot4 & Slot5 and each controllers
are connected with separate MD1400 enclosure, both Enclosure EMMs are listed under “Connector 0” and no device is listed
under “Connector 1 ”. Slot-4 SAS 12Gbps controller is connected with two redundant EMMs which are listed in “Connector
0”. Slot-5 12Gbps controller is also connected with two redundant EMMs, but both are listed under “Connector 0”.
JIT-71919: On 14th generation of PowerEdge servers when connected with two SAS 12Gbps controller in Slot4 & Slot5 and each controllers
are connected with separate MD1400 enclosure, with two redundant cable i.e. EMM0 & EMM1, then with redundant EMM both enclosures
are listed for EMM0 & EMM1, but physical disks are not displayed for EMM1. Slot-4 SAS 12Gbps controller is connected with
two redundant EMMs – Here both EMMs are listed under “Connector 0”, and for EMM0 physical Disk is listed and for EMM1 no
physical disks are listed. Slot-5 SAS 12Gbps controller is connected with single EMM (ie.EMM1) – Here one EMM0 is listed
under “Connector 0”, and for EMM1 physical Disk are listed.
JIT-78857 : Successful Prepare to remove and reinsertion operation on a drive for 3-4 times, will result in all the drives getting
removed and inserted back in ESXi 6.5 U1 operating system.
JIT-79925 : On 13th generation of PowerEdge servers, OMSS reports for PCIe Link Speed is negotiated and maximum link speed/width shows
'0' for Slot 1 device.
JIT-76259: EMMI alert description for Dedicated hot spare assigned physical disk should contain meaningful alert description instead
of the statement,
This alert is provided for informational purposes.
JIT-72304 : Able to assign lesser capacity physical disk as a DHS to the virtual disk created with physical disk having higher capacity.
JIT-80079: If
Prepare to remove operation is executed on a Non-RAID PCIe-SSD physical disk, the bus protocol for the virtual disk associated with that
physical disk, changes to SATA from PCIe-SSD.
JIT-84544: In every refresh cycle for NVMe drives in VMware (ESXi) OS,
following warning message is displayed in the vmkernel.log.
LinuxThread: 381: sfcb-dcim: Error cloning thread: -1 (bad0117)
JIT-98301: The storage tree on the OM page disappears when
there is I/O stress on ESXi host for multiple days.
Workaround: Restart the service
manually.
JIT-90125: On Server Administrator while configuring the enclosure asset tag and name with maximum length , Server Administrator displays
all the characters completely. But in iDRAC GUI, enclosure asset tag displays the last character as truncated.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\