Dell PowerEdge T440 EMC Boot Optimized Server Storage-S1 Users Guide - Page 29

Character limitation while naming a virtual disk

Get Dell PowerEdge T440 PDF manuals and user guides View all Dell PowerEdge T440 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 29 highlights

Corrective Action: These events can be safely ignored as there is no functionality loss. Character limitation while naming a virtual disk Issue: Limitation in the number of characters while creating a virtual disk name Corrective Action: It is recommended that you use maximum of 10 characters while naming the virtual disk. VMFS datastore is disabled on the 14th generation of PowerEdge systems that are shipped with VMware ESXi installed on BOSS-S1 Issue: Installation of ESXi on a BOSS-S1 device does not have VMFS datastore enabled by default, and disables VMFS if you use a custom image for installation. This issue occurs when using ESXi version 6.5.x or later on the BOSS-S1 card. Corrective Action: When you have VMware ESXi installed on BOSS-S1, it is recommended that you use the BOSS-S1 device only as a boot device and disable VMFS if you are installing a custom image. For more information, see https:// kb.vmware.com/s/article/2004582 and https://kb.vmware.com/s/article/2145210. NOTE: The scratch partition is created and configured during VMware ESXi installation in addition to boot support on BOSS-S1. Physical disk not visible to operating system Issue: Probable Cause: One or both physical disks are not appearing for use by an operating system. A physical disk will not be presented to the operating system in the following scenarios: • There is RAID metadata on the physical disk and no RAID metadata on the controller. • The BOSS-S1 controller has RAID metadata on it and the physical disk does not have the RAID metadata on it. Corrective Action: If the RAID metadata is on the controller, follow the steps listed in Clear Controller Configuration. If the RAID metadata is on the physical disk, follow the steps specified in Erase physical disk. Alternatively, if you want to keep the RAID drive, refer to Virtual Disk Not visible to Operating System Virtual disk not visible to operating system Issue: In RAID mode a virtual disk is not appearing for use by an operating system. Probable Cause: Virtual disks will not be presented to the system if they are not native to the controller. Corrective Action: Import the virtual disk via HII as specified in section Virtual Disk Import. Drive replacement Issue: An installed drive is not listed in the BOSS-S1 configuration utility. OpenManage reports Physical disk offline state. Probable Cause: Drive is either in failure state or has corrupted firmware. Corrective Action: Reseat drive to ensure drive is inserted correctly. If error persists, attempt to update drive firmware using DUP. If error is still present, replace erroneous drive. Troubleshooting 29

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
Corrective Action:
These events can be safely ignored as there is no functionality loss.
Character limitation while naming a virtual disk
Issue:
Limitation in the number of characters while creating a virtual disk name
Corrective Action:
It is recommended that you use maximum of 10 characters while naming the virtual disk.
VMFS datastore is disabled on the 14th generation
of PowerEdge systems that are shipped with
VMware ESXi installed on BOSS-S1
Issue:
Installation of ESXi on a BOSS-S1 device does not have VMFS datastore enabled by default, and disables VMFS if
you use a custom image for installation. This issue occurs when using ESXi version 6.5.x or later on the BOSS-S1
card.
Corrective Action:
When you have VMware ESXi installed on BOSS-S1, it is recommended that you use the BOSS-S1 device only as
a boot device and disable VMFS if you are installing a custom image. For more information, see
https://
kb.vmware.com/s/article/2004582
and
.
NOTE:
The scratch partition is created and configured during VMware ESXi installation in addition
to boot support on BOSS-S1.
Physical disk not visible to operating system
Issue:
One or both physical disks are not appearing for use by an operating system.
Probable Cause:
A physical disk will not be presented to the operating system in the following scenarios:
•
There is RAID metadata on the physical disk and no RAID metadata on the controller.
•
The BOSS-S1 controller has RAID metadata on it and the physical disk does not have the RAID metadata on it.
Corrective Action:
If the RAID metadata is on the controller, follow the steps listed in
Clear Controller Configuration
.
If the RAID metadata is on the physical disk, follow the steps specified in
Erase physical disk
.
Alternatively, if you want to keep the RAID drive, refer to
Virtual Disk Not visible to Operating System
Virtual disk not visible to operating system
Issue:
In RAID mode a virtual disk is not appearing for use by an operating system.
Probable Cause:
Virtual disks will not be presented to the system if they are not native to the controller.
Corrective Action:
Import the virtual disk via HII as specified in section
Virtual Disk Import
.
Drive replacement
Issue:
An installed drive is not listed in the BOSS-S1 configuration utility.
OpenManage reports
Physical disk offline
state.
Probable Cause:
Drive is either in failure state or has corrupted firmware.
Corrective Action:
Reseat drive to ensure drive is inserted correctly. If error persists, attempt to update drive firmware using DUP. If
error is still present, replace erroneous drive.
Troubleshooting
29