Hitachi Compute Blade 2000, User Manual

Page: 1872 / 1927

1821
14 14
When
You
N
eed H
elp
If the memory dump file does not exist in the default location
after memory dump is collected, the location may be
changed from the default. Check the registry using the
following items.
Key:
HKEY_LOCAL_MACHINE¥System\CurrentControlSet\ Contr
ol\CrashControl
Name: DumpFile
Memory dump for Linux
This subsection describes how to collect memory dump with kdump of Red Hat
Enterprise Linux (RHEL) 6/RHEL 5.
See Using Parameters to Stop the System at Hardware
Failure, Useful Settings for Red Hat Enterprise Linux in
Chapter 13 for memory dump settings.

Triggering memory dump
For an OS failure such as kernel panic, memory dump is automatically collected. When
the system hangs up, issuing NMI allows the memory dump to be collected.
To issue NMI, select
NMI from Power and Reset menu of Remote console application,
or click Server Operation tab > Power and LEDs and click NMI button. See Connect
the Remote Console in Chapter 3, or Server Blade Setup in Chapter 5 for details.

Collecting memory dump
The following screen is displayed during memory dump collection.
Example of RHEL 6
The memory dump is completed when
100%
is displayed at the bottom.
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32447
Kernel command line: cgroup_disable=memory console=ttyS1,115200 mce=0
nmi_watchdog=0
no_timer_check nr_cpus=1 pcie_aspm=off reset_devices
….
Creating Block Devices
kjournald starting. Commit interval 5 seconds
EXT3-fs (sdb2): using internal journal
EXT3-fs (sdb2): mounted filesystem with ordered data mode
Checking for memory holes :
[ 0 %]