kdump can not mount /var/crash

Latest response

I try to get kdump functional but when I trigger a kernel crash the kdump kernel begins to start but is not successful
It can not mount /var/crash
I have a /boot on mdraid 1 and lvm volumes on top of mdraid 10.
Can kdump cope with this? What can I do to get kdump working?

Markus,
more Information below

My kdump config is this

ext4 UUID=1fdc97df-b096-4e25-ac30-09bc6162098a
path /var/crash
core_collector makedumpfile -l --message-level 1 -d 31
extra_modules raid10
default shell

[root@h1408060 ~]# df -h
Filesystem                       Size  Used Avail Use% Mounted on
/dev/mapper/lvm.h1408060-wurzel  3,0G  818M  2,2G  28% /
devtmpfs                         1,4G     0  1,4G   0% /dev
tmpfs                            1,4G     0  1,4G   0% /dev/shm
tmpfs                            1,4G  8,4M  1,4G   1% /run
tmpfs                            1,4G     0  1,4G   0% /sys/fs/cgroup
/dev/mapper/lvm.h1408060-home    506M   26M  480M   6% /home
/dev/mapper/lvm.h1408060-var    1018M   57M  962M   6% /var
/dev/mapper/lvm.h1408060-tmp    1018M   42M  977M   5% /tmp
/dev/mapper/lvm.h1408060-log    1018M   35M  984M   4% /var/log
/dev/mapper/lvm.h1408060-audit   506M   29M  477M   6% /var/log/audit
/dev/md0                         509M  100M  410M  20% /boot

...
systemd-fsck[291]: fsck: error 2 (No such file or directory) while executing fsck.ext2 for /dev/disk/by-uuid/d33394fe-b204-4ffc-b08b-31bd27bb50aa
[  OK  ] Started File System Check on /dev/disk/by-uuid/d3339...b-31bd27bb50aa.
systemd-fsck[292]: fsck.ext4: No such file or directory while trying to open /dev/mapper/lvm.h1408060-kdump
[  OK  ] Started File System Check on /dev/mapper/lvm.h1408060-kdump.
systemd-fsck[292]: Possibly non-existent device?
         Mounting /var/crash...
[FAILED] Failed to mount /var/crash.
See 'systemctl status var-crash.mount' for details.
[DEPEND] Dependency failed for Local File Systems.
[    5.151633] md: bind<vda1>
[    5.190479] md: bind<vda2>
[    5.397817] md: bind<vdb2>
[    5.410237] md: bind<vdb1>
[    5.721567] md: bind<vdc1>
[    5.735550] md: bind<vdc2>
[    5.933484] md: bind<vdd1>
[    5.958760] md: raid1 personality registered for level 1
[    5.965081] md/raid1:md0: active with 4 out of 4 mirrors
[    5.970797] md0: detected capacity change from 0 to 536805376
[    5.979078] md: bind<vdd2>
[    5.998457] md: raid10 personality registered for level 10
[    6.005599] md/raid10:md1: active with 4 out of 4 devices
[    6.011659] created bitmap (1 pages) for device md1
[    6.016856] md1: bitmap initialized from disk: read 1 pages, set 0 of 304 bits
[    6.057821] md1: detected capacity change from 0 to 20381171712
[   11.039016]  md0: unknown partition table
[   11.120371]  md1: unknown partition table
[   12.298111] bio: create slab <bio-1> at 1
[   13.215367] EXT4-fs (dm-2): recovery complete
[   13.217125] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: stripe=256,data=ordered
[   14.732572] SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
[   14.748605] XFS (dm-1): Mounting Filesystem
[   15.018780] XFS (dm-1): Starting recovery (logdev: internal)
[   15.253904] XFS (dm-1): Ending recovery (logdev: internal)
MF

Responses