Account Links: Cart | Your Account | Logout

Skip to content

Red Hat Knowledgebase

Red Hat Knowledgebase Search:

Updated Within the Last:

New Solutions within the last day New Solutions within the last week New Solutions within the last month

Browse by topics:


Click to View a Topic
Red Hat Enterprise Linux > s390 > Issue <<  16 of 23 >>

Solution Tools:


Email a Solution Postcard Printer version Submit a comment on this answer Update notifications Request an answer Back

Article Reference

Article ID: 12542
Last update: 10-30-08
Issue:
What do I need to do to use dumpconf on System z?
Resolution:

First, locate a supported dump device.

Next, manually bring the disk online:

chccwdev -e 0.0.f000

Clear the disk of fs labels, lvm formatting, mdadm formatting, etc. This is important to prevent the disk from being automatically used for something other than as dump device.

Examples:

tune2fs -L '' /dev/dasdd1
pvremove /dev/dasdd1
mdadm --zero-superblock

Prepare the disk for use as a dump device:

zipl -d /dev/dasdd1

Edit /etc/sysconfig/dumpconf and uncomment these parameters and fill in info for the device:

ON_PANIC=dump
DUMP_TYPE=ccw
DEVICE=0.0.f000

Configure to the system to include the new disk on boot up:

Edit /etc/modprobe.conf to include the new disk in the dasd list:

options dasd_mod dasd=201,f000

Then, run mkinitrd and zipl to enter the changes into the boot configuration:

cd /boot
mkinitrd -v -f initrd-2.6.18-53.el5.img `uname -r`
zipl -V

Enable the dumpconf service to start at boot up and to start now:

chkconfig dumpconf on
service dumpconf start

Reboot to verify the boot configuration changes.


How well did this entry answer your question?


good wrong incomplete out of date
Red Hat Enterprise Linux > s390 > Issue <<   16  of  23  >>