search for: x86_64kdump

...rd -d -f $MKDUMPRD_ARGS" kdump_initrd="${KDUMP_BOOTDIR}/initrd-${kdump_kver}kdump.img" and at the end it runs this command if it doesn't find one: $MKDUMPRD $kdump_initrd $kdump_kver that tipically will translate in: /sbin/mkdumprd -d -f "/boot/initrd-2.6.32-642.13.1.el6.x86_64kdump.img" 2) In CentOS 7 we have systemd unit files and for kdump: /usr/lib/systemd/system/kdump.service Supposing you have just installed 3.10.0-693.21.1.el7.x86_64 The script called actually it is /usr/bin/kdumpctl See also fadump (firmware assisted dump) concepts in RHEL 7 / CentOS 7: https...

...ave just installed 2.6.32-642.13.1.el6.x86_64 kernel > > [snip] > > and at the end it runs this command if it doesn't find one: > $MKDUMPRD $kdump_initrd $kdump_kver > > that tipically will translate in: > > /sbin/mkdumprd -d -f "/boot/initrd-2.6.32-642.13.1.el6.x86_64kdump.img" > > The command line fo CentOS 6 clearly misses the kernel version to build initrd file for, so the correct command should be: /sbin/mkdumprd -d -f "/boot/initrd-2.6.32-642.13.1.el6.x86_64kdump.img" 2.6.32-642.13.1.el6.x86_64 On a test system of mine with version 6.8: #...

..., I've got CentOS 6.8 x64, updated today to the latest by 'yum update' this installed a new kernel: 2.6.32-642.4.2.el6.x86_64 in /var/log/boot.log I found these 3 lines ... No kdump initial ramdisk found. [WARNING] Rebuilding /boot/initrd-2.6.32-642.4.2.el6.x86_64kdump.img cp: cannot stat `/lib/firmware/i915/bxt_dmc_ver1.bin': No such file or directory the first two are logic to me, but the 3rd line, did there something fail at the update? Thanks, Walter

...8 x64, updated today to the latest by 'yum update' >> this installed a new kernel: 2.6.32-642.4.2.el6.x86_64 >> >> in /var/log/boot.log I found these 3 lines ... >> >> No kdump initial ramdisk found. [WARNING] >> Rebuilding /boot/initrd-2.6.32-642.4.2.el6.x86_64kdump.img >> cp: cannot stat `/lib/firmware/i915/bxt_dmc_ver1.bin': No such file >> or directory >> >> the first two are logic to me, but the 3rd line, did there something >> fail at the update? >> >> Thanks, >> Walter >> > > 'stat'...

...1024 28. Jan 10:31 grub2 -rw-r--r--. 1 root root 40142116 15. Dez 2015 initramfs-0-rescue-34946d7b5edb0946bfb52c0f6cae67af.img -rw------- 1 root root 50402914 6. Dez 09:23 initramfs-3.10.0-693.11.1.el7.x86_64.img -rw------- 1 root root 18149718 6. Dez 09:24 initramfs-3.10.0-693.11.1.el7.x86_64kdump.img -rw------- 1 root root 50405879 5. Jan 09:02 initramfs-3.10.0-693.11.6.el7.x86_64.img -rw------- 1 root root 18150336 5. Jan 09:04 initramfs-3.10.0-693.11.6.el7.x86_64kdump.img -rw------- 1 root root 50402830 28. Jan 10:31 initramfs-3.10.0-693.17.1.el7.x86_64.img -rw------- 1 root roo...

...gianluca.cecchi at gmail.com> > Sent Time: 2019-03-28 16:59:19 (Thursday) > [...] > The command line fo CentOS 6 clearly misses the kernel version to build > initrd file for, so the correct command should be: > > /sbin/mkdumprd -d -f > "/boot/initrd-2.6.32-642.13.1.el6.x86_64kdump.img" 2.6.32-642.13.1.el6.x86_64 > I test it and it works for me, although prints some harmless warnings. Thanks

On 03/12/15 09:40, Bernard Lheureux wrote: > On 12/03/2015 10:29 AM, Duncan Brown wrote: > initramfs is missing... > check if /boot/initramfs-{kernelversion}.img is correctly there, if not > do a "yum reinstall kernel-{version}" and it should be ok ! You might want to also check there is enough diskspace for the initrd to be built and hosted in the right place.. --

...oot 33 Aug 15 11:27 grub2 -rw-rw-r--. 1 root root 57630181 Aug 15 07:46 initramfs-0-rescue-94f9d612ea4e4d2497d367334416d88b.img -rw-r--r--. 1 root root 30853341 Aug 15 16:48 initramfs-3.10.0-327.28.2.el7.x86_64.img -rw-r--r--. 1 root root 19329078 Aug 15 11:55 initramfs-3.10.0-327.28.2.el7.x86_64kdump.img -rw-r--r--. 1 root root 30855404 Sep 12 11:04 initramfs-3.10.0-327.28.3.el7.x86_64.img -rw-r--r--. 1 root root 19329625 Sep 12 11:06 initramfs-3.10.0-327.28.3.el7.x86_64kdump.img -rw-r--r--. 1 root root 30852186 Aug 15 16:48 initramfs-3.10.0-327.el7.x86_64.img -rw-r--r--. 1 root root 1921703...

...02:21 grub2 -rw-r--r--. 1 root root 40655493 Apr 3 2015 initramfs-0-rescue-6494b5d98adc4f66b0cf4c19a0f6ab66.img -rw-------. 1 root root 29666884 Oct 13 01:25 initramfs-3.10.0-327.36.2.el7.x86_64.img -rw-------. 1 root root 18119089 Oct 13 02:20 initramfs-3.10.0-327.36.2.el7.x86_64kdump.img -rw-r--r--. 1 root root 10190975 Dec 19 2015 initrd-plymouth.img -rw-r--r--. 1 root root 252739 Oct 10 23:20 symvers-3.10.0-327.36.2.el7.x86_64.gz -rw-------. 1 root root 2965270 Oct 10 23:18 System.map-3.10.0-327.36.2.el7.x86_64 -rwxr-xr-x. 1 root root 4902656...

Hi Jim, Thanks for this. I looked into what you said, and once happy I ran the command you gave. It appeared to work as it did not come up with any errors, and the output from efibootmgr showed 1) Centos had been added as an option and 2) it was the first in the boot sequence. However, when I rebooted the laptop went straight into Win8, and after rebooting back into KDE Live, the option is

...release 7.1.1503 (Core) /dev/sda1 mounted on / ><fs> ls /boot/ .vmlinuz-3.10.0-229.el7.x86_64.hmac System.map-3.10.0-229.el7.x86_64 config-3.10.0-229.el7.x86_64 grub grub2 initramfs-0-rescue-c898899928d341b58ae4d02802d19340.img initramfs-3.10.0-229.el7.x86_64.img initramfs-3.10.0-229.el7.x86_64kdump.img initrd-plymouth.img ldlinux.sys mbr.bin symvers-3.10.0-229.el7.x86_64.gz syslinux.cfg vmlinuz-0-rescue-c898899928d341b58ae4d02802d19340 vmlinuz-3.10.0-229.el7.x86_64 ><fs> cat /boot/syslinux.cfg DEFAULT linux LABEL linux SAY Booting the kernel KERNEL /boot/v...

...pdate' >>>> this installed a new kernel: 2.6.32-642.4.2.el6.x86_64 >>>> >>>> in /var/log/boot.log I found these 3 lines ... >>>> >>>> No kdump initial ramdisk found. [WARNING] >>>> Rebuilding /boot/initrd-2.6.32-642.4.2.el6.x86_64kdump.img >>>> cp: cannot stat `/lib/firmware/i915/bxt_dmc_ver1.bin': No such file >>>> or directory >>>> >>>> the first two are logic to me, but the 3rd line, did there something >>>> fail at the update? >>>> >>>> Th...

...nted Mounting filesystems: mount: special device /dev/drbd0 does not exist [FAILED] Starting acpi daemon: [ OK ] Starting HAL daemon: [ OK ] Starting lm_sensors: loading module ipmi-si adm1021 coretem[ OK ]0 Retrigger failed udev events [ OK ] Rebuilding /boot/initrd-2.6.32-573.22.1.el6.x86_64kdump.img Warning: There might not be enough space to save a vmcore. The size of UUID=2288bad6-ceb0-4984-bf3d-c57666603495 should be greater than 49416020 kilo bytes. Starting DRBD resources: [ d(main) s(main) n(main) ]. Starting BackupPC: 2016-05-03 09:57:14 Can't create a test hard...

What do you mean? Wouldn't the kernel version always be the actual running version of the kernel that was booted? Ben On 3/26/19 6:16 PM, wuzhouhui wrote: >> -----Original Messages----- >> From: "Benjamin Hauger" <hauger at noao.edu> >> Sent Time: 2019-03-27 00:15:21 (Wednesday) >> To: centos at centos.org >> Cc: >> Subject: Re: [CentOS]

...; I've got CentOS 6.8 x64, updated today to the latest by 'yum update' > this installed a new kernel: 2.6.32-642.4.2.el6.x86_64 > > in /var/log/boot.log I found these 3 lines ... > > No kdump initial ramdisk found. [WARNING] > Rebuilding /boot/initrd-2.6.32-642.4.2.el6.x86_64kdump.img > cp: cannot stat `/lib/firmware/i915/bxt_dmc_ver1.bin': No such file or > directory > > the first two are logic to me, but the 3rd line, did there something > fail at the update? > > Thanks, > Walter > > > > > _______________________________________...

...the latest by 'yum update' >>> this installed a new kernel: 2.6.32-642.4.2.el6.x86_64 >>> >>> in /var/log/boot.log I found these 3 lines ... >>> >>> No kdump initial ramdisk found. [WARNING] >>> Rebuilding /boot/initrd-2.6.32-642.4.2.el6.x86_64kdump.img >>> cp: cannot stat `/lib/firmware/i915/bxt_dmc_ver1.bin': No such file >>> or directory >>> >>> the first two are logic to me, but the 3rd line, did there something >>> fail at the update? >>> >>> Thanks, >>> Walter...

...gt;> this installed a new kernel: 2.6.32-642.4.2.el6.x86_64 >>>>> >>>>> in /var/log/boot.log I found these 3 lines ... >>>>> >>>>> No kdump initial ramdisk found. [WARNING] >>>>> Rebuilding /boot/initrd-2.6.32-642.4.2.el6.x86_64kdump.img >>>>> cp: cannot stat `/lib/firmware/i915/bxt_dmc_ver1.bin': No such file >>>>> or directory >>>>> >>>>> the first two are logic to me, but the 3rd line, did there something >>>>> fail at the update? >>>>...

...-. 1 root root 40655493 Apr 3 2015 > initramfs-0-rescue-6494b5d98adc4f66b0cf4c19a0f6ab66.img > -rw-------. 1 root root 29666884 Oct 13 01:25 > initramfs-3.10.0-327.36.2.el7.x86_64.img > -rw-------. 1 root root 18119089 Oct 13 02:20 > initramfs-3.10.0-327.36.2.el7.x86_64kdump.img > -rw-r--r--. 1 root root 10190975 Dec 19 2015 initrd-plymouth.img > -rw-r--r--. 1 root root 252739 Oct 10 23:20 > symvers-3.10.0-327.36.2.el7.x86_64.gz > -rw-------. 1 root root 2965270 Oct 10 23:18 > System.map-3.10.0-327.36.2.el7.x86_64 > -rwxr-xr-x...

...device /dev/drbd0 does not exist > [FAILED] > Starting acpi daemon: [ OK ] > Starting HAL daemon: [ OK ] > Starting lm_sensors: loading module ipmi-si adm1021 coretem[ OK ]0 > Retrigger failed udev events [ OK ] > > > > Rebuilding /boot/initrd-2.6.32-573.22.1.el6.x86_64kdump.img > Warning: There might not be enough space to save a vmcore. > The size of UUID=2288bad6-ceb0-4984-bf3d-c57666603495 should be greater than 49416020 kilo bytes. > > > Starting DRBD resources: [ d(main) s(main) n(main) ]. > > > > > Starting BackupPC: 2016-0...

On 5/3/2016 2:52 PM, Clint Dilks wrote: > Are you using SE Linux? If so does the context for /dev/drbd0 match on > both systems ? afaik, this has nothing to do with the drbd slave. I reboot the master, replication resumes just fine, but the /data filesystem doesn't get automounted til I manually mount it. -- john r pierce, recycling bits in santa cruz