Users Guide
Table Of Contents
- Dell EMC PowerEdge Servers Troubleshooting Guide
- Contents
- Introduction
- Diagnostic indicators
- Status LED indicators
- System health and system ID indicator codes
- iDRAC Quick Sync 2 indicator codes
- iDRAC Direct LED indicator codes
- NIC indicator codes
- Power supply unit indicator codes
- Non-redundant power supply unit indicator codes
- Hard drive indicator codes
- uSATA SSD indicator codes
- Internal dual SD module indicator codes
- Running diagnostics
- Troubleshooting hardware issues
- Troubleshooting system startup failure
- Troubleshooting external connections
- Troubleshooting the video subsystem
- Troubleshooting a USB device
- Troubleshooting a serial Input Output device
- Troubleshooting a NIC
- Troubleshooting a wet system
- Troubleshooting a damaged system
- Troubleshooting the system battery
- Troubleshooting cooling problems
- Troubleshooting cooling fans
- Troubleshooting an internal USB key
- Troubleshooting a micro SD card
- Troubleshooting expansion cards
- Troubleshooting processors
- Troubleshooting a storage controller
- OMSA flagging PERC driver
- Importing or clearing foreign configurations using the foreign configuration view screen
- Importing or clearing foreign configurations using the VD mgmt menu
- RAID controller L1, L2 and L3 cache error
- PERC controllers do not support NVME PCIe drives
- 12 Gbps hard drive does not support in SAS 6ir RAID controllers
- Hard drives cannot be added to the existing RAID 10 Array
- PERC battery discharging
- PERC battery failure message is displayed in ESM log
- Creating non-raid disks for storage purpose
- Firmware or Physical disks out-of-date
- Cannot boot to Windows due to foreign configuration
- Offline or missing virtual drives with preserved cache error message
- Expanding RAID array
- LTO-4 Tape drives are not supported on PERC
- Limitations of HDD size on H310
- System logs show failure entry for a storage controller even though it is working correctly
- Troubleshooting hard drives
- Troubleshooting an optical drive
- Troubleshooting a tape backup unit
- Troubleshooting no power issues
- Troubleshooting power supply units
- Troubleshooting RAID
- RAID configuration using PERC
- RAID configuration using OpenManage Server Administrator
- RAID configuration by using Unified Server Configurator
- Downloading and installing the RAID controller log export by using PERCCLI tool on ESXi hosts on Dell’s 13th generation of PowerEdge servers
- Configuring RAID by using Lifecycle Controller
- Starting and target RAID levels for virtual disk reconfiguration and capacity expansion
- Replacing physical disks in RAID1 configuration
- Thumb rules for RAID configuration
- Reconfiguring or migrating virtual disks
- Foreign Configuration Operations
- Viewing Patrol Read report
- Check Consistency report
- Virtual disk troubleshooting
- Rebuilding of virtual disk does not work
- Rebuilding of virtual disk completes with errors
- Cannot create a virtual disk
- A virtual disk of minimum size is not visible to Windows Disk Management
- Virtual disk errors on systems running Linux
- Problems associated with using the same physical disks for both redundant and nonredundant virtual disks
- Enable the alarm on PERC 5/E adapter to alert in case of physical disk failures
- RAID controller displays multibit ECC errors
- PERC goes offline with an error message
- Reconfiguring the RAID level and virtual disks
- Lost shared storage access
- Troubleshooting memory or battery errors on the PERC controller on Dell PowerEdge servers
- Slicing
- RAID puncture
- Troubleshooting thermal issue
- Input/Output errors while reseating SAS IOM storage sled on hardware configurations
- Server management software issues
- What are the different types of iDRAC licenses
- How to activate license on iDRAC
- Can I upgrade the iDRAC license from express to enterprise and BMC to express
- How to find out missing licenses
- How to export license using iDRAC web interface
- How to set up e-mail alerts
- System time zone is not synchronized
- How to set up Auto Dedicated NIC feature
- How to configure network settings using Lifecycle Controller
- Assigning hot spare with OMSA
- Storage Health
- How do I configure RAID using operating system deployment wizard
- Foreign drivers on physical disk
- Physical disk reported as Foreign
- How to update BIOS on 13th generation PowerEdge servers
- Why am I unable to update firmware
- Which are the operating systems supported on Dell EMC PowerEdge servers
- Unable to create a partition or locate the partition and unable to install Microsoft Windows Server 2012
- JAVA support in iDRAC
- How to specify language and keyboard type
- Message Event ID - 2405
- Installing Managed System Software On Microsoft Windows Operating Systems
- Installing Managed System Software On Microsoft Windows Server and Microsoft Hyper-V Server
- Installing Systems Management Software On VMware ESXi
- Processor TEMP error
- PowerEdge T130, R230, R330, and T330 servers may report a critical error during scheduled warm reboots
- SSD is not detected
- OpenManage Essentials does not recognize the server
- Unable to connect to iDRAC port through a switch
- Lifecycle Controller is not recognizing USB in UEFI mode
- Guidance on remote desktop services
- Troubleshooting operating system issues
- How to install the operating system on a Dell PowerEdge Server
- Locating the VMware and Windows licensing
- Troubleshooting blue screen errors or BSODs
- Troubleshooting a Purple Screen of Death or PSOD
- Troubleshooting no boot issues for Windows operating systems
- No POST issues in iDRAC
- Troubleshooting a No POST situation
- Migrating to OneDrive for Business using Dell Migration Suite for SharePoint
- Windows
- Installing and reinstalling Microsoft Windows Server 2016
- FAQs
- Why are the USB keyboard and mouse not detected during the Windows Server 2008 R2 SP1 installation
- Why does the installation wizard stop responding during the Windows OS installation
- Why does Windows OS installation using Lifecycle Controller, on PowerEdge Servers fail at times with an error message
- Why does Windows Server 2008 R2 SP1 display a blank screen in UEFI mode after installation
- Symptoms
- Troubleshooting system crash at cng.sys with watchdog Error violation
- Host bus adapter mini is missing physical disks and backplane in Windows
- Converting evaluation OS version to retail OS version
- Partitions on disk selected for installation of Hyper-V server 2012
- Install Microsoft Hyper-V Server 2012 R2 with the Internal Dual SD module
- VMware
- Linux
- Installing operating system through various methods
- Getting help
● Cache Use
Hardware RAID controllers utilize cache (a temporary repository of information) for their normal operation. The normal
operation cache comprises DRAM memory, which, like system memory, retains data only when powered on.
Newer controllers utilize NVCache, which is utilized when the server is powered off. NVCache memory contains both DRAM
memory (for normal operation) and flash memory (non-volatile). The controllers battery (if operational) powers the DRAM
memory during a power loss so that the contents can be copied into the flash memory for indefinite storage.
The contents of cache can essentially be broken into three parts:
● RAID configuration and metadata - Information about the RAID arrays including configuration information, disk members, role
of disks, etc.
● Controller logs - RAID controllers maintain several log files. Dell technicians rely on the TTY log as the primary log for
troubleshooting various RAID and hard drive issues.
● RAID data - This is the actual data destined to be written to the individual hard drives. Data is written into the cache of the
controller in both Write Through and Write Back cache policy modes.
Slicing
Configuring multiple RAID arrays across the same set of disks is called Slicing.
RAID puncture
A RAID puncture is a feature of Dell PowerEdge RAID Controller (PERC) designed to allow the controller to restore the
redundancy of the array despite the loss of data caused by a double fault condition. Another name for a RAID puncture is rebuild
with errors. When the RAID controller detects a double fault and there is insufficient redundancy to recover the data in the
impacted stripe, the controller creates a puncture in that stripe and enables the rebuild to continue.
● Any condition that causes data to be inaccessible in the same stripe on more than one drive is a double fault.
● Double faults cause the loss of all data within the impacted stripe.
● All RAID punctures are double faults but all double faults are NOT RAID punctures.
Causes of RAID puncture
Without the RAID puncture feature, the array rebuild would fail, and leave the array in a degraded state. In some cases, the
failures may cause additional drives to fail, and cause the array to be in a non-functioning offline state. Puncturing an array has
no impact on the ability to boot to or access any data on the array.
RAID punctures can occur in one of two situations:
● Double Fault already exists (Data already lost).
Data error on an online drive is propagated (copied) to a rebuilding drive.
● Double Fault does not exist (Data is lost when second error occurs).
While in a degraded state, if a bad block occurs on an online drive, that LBA is RAID punctured.
This advantage of puncturing an array is keeping the system available in production till the redundancy of the array is
restored. The data in the affected stripe is lost whether the RAID puncture occurs or not. The primary disadvantage of this
88
Troubleshooting hardware issues