Dell PowerEdge T640 EMC Boot Optimized Server Storage-S1 Users Guide - Page 30

Controller replacement, Controller failure, Unable to boot to M.2 drive installed in slot 1

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

Page 30 highlights

Controller replacement Issue: Controller's UEFI configuration utility menu entry not appearing. Probable Cause: This is either a firmware or a hardware fault. Corrective Action Flash the latest firmware on the BOSS adapter. If the problem persists, shutdown the server and unplug the BOSS-S1 adapter. Plug the BOSS-S1 adapter into the PCIe slot. Boot the system and check the UEFI configuration utility menu again. If the issue persists, see Controller Failure. NOTE: Ensure that the system is completely disconnected from all power sources before making any hardware changes. Controller failure Issue: BOSS-S1 device is not presented to system. Probable Cause: Hardware fault on the card. Corrective Action: Replace the BOSS-S1 adapter. Unable to boot to M.2 drive installed in slot 1 Issue: When two unconfigured bootable M.2 drives are inserted into the BOSS-S1 device, only the slot 0 drive may be used as a boot drive. Probable Cause: Working as designed, BIOS only allows booting from the first listed boot device, in this case, slot 0 per peripheral controller. This only occurs in legacy BIOS boot mode. Corrective Action: Remove the drive from slot 1 and install it in slot 0. CLI reports unsupported features Issue: Several commands, options, or other features listed by the CLI state that they are unsupported when run. Probable Cause: CLI shows the same information on all Marvell products, but only implements the functions which are pertinent to that platform or system. Corrective Action: Use supported features. Failure to install ESXi on RAID 1 Issue: Attempting to install ESXi on a RAID 1 results in an invalid partition table error. Probable Cause: If an unconfigured physical disk containing an ESXi partition is used in a virtual disk, any attempts to install a partition of ESXi on this virtual disk will raise an error due to failure to clear out the previous partition. Corrective Action: Delete the existing RAID 1, run erase physical disk on both drives, re-create the RAID 1 with quick initialization ON, then attempt to reinstall ESXi on the virtual disk. System not responding Issue Systems with ESXi OS stops responding. Corrective Action: Ensure that the latest version of ESXi OS is installed. 30 Troubleshooting

  • 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
Controller replacement
Issue:
Controller's UEFI configuration utility menu entry not appearing.
Probable Cause:
This is either a firmware or a hardware fault.
Corrective Action:
•
Flash the latest firmware on the BOSS adapter.
•
If the problem persists, shutdown the server and unplug the BOSS-S1 adapter.
•
Plug the BOSS-S1 adapter into the PCIe slot.
•
Boot the system and check the UEFI configuration utility menu again.
If the issue persists, see
Controller Failure.
NOTE:
Ensure that the system is completely disconnected from all power sources before making any hardware changes.
Controller failure
Issue:
BOSS-S1 device is not presented to system.
Probable Cause:
Hardware fault on the card.
Corrective Action:
Replace the BOSS-S1 adapter.
Unable to boot to M.2 drive installed in slot 1
Issue:
When two unconfigured bootable M.2 drives are inserted into the BOSS-S1 device, only the slot 0 drive may be
used as a boot drive.
Probable Cause:
Working as designed, BIOS only allows booting from the first listed boot device, in this case, slot 0 per peripheral
controller. This only occurs in legacy BIOS boot mode.
Corrective Action:
Remove the drive from slot 1 and install it in slot 0.
CLI reports unsupported features
Issue:
Several commands, options, or other features listed by the CLI state that they are unsupported when run.
Probable Cause:
CLI shows the same information on all Marvell products, but only implements the functions which are pertinent to
that platform or system.
Corrective Action:
Use supported features.
Failure to install ESXi on RAID 1
Issue:
Attempting to install ESXi on a RAID 1 results in an invalid partition table error.
Probable Cause:
If an unconfigured physical disk containing an ESXi partition is used in a virtual disk, any attempts to install a
partition of ESXi on this virtual disk will raise an error due to failure to clear out the previous partition.
Corrective Action:
Delete the existing RAID 1, run
erase physical disk
on both drives, re-create the RAID 1 with quick
initialization ON, then attempt to reinstall ESXi on the virtual disk.
System not responding
Issue
Systems with ESXi OS stops responding.
Corrective Action:
Ensure that the latest version of ESXi OS is installed.
30
Troubleshooting