similar to: info wanted about meaning of boot messages ...

On 25.08.2016 20:24, ken wrote: > On 08/25/2016 12:08 PM, Walter H. wrote: >> Hello, >> >> 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] >>

On Thu, August 25, 2016 23:21, ken wrote: > On 08/25/2016 02:42 PM, Walter H. wrote: >> On 25.08.2016 20:24, ken wrote: >>> On 08/25/2016 12:08 PM, Walter H. wrote: >>>> Hello, >>>> >>>> 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

On 08/25/2016 02:42 PM, Walter H. wrote: > On 25.08.2016 20:24, ken wrote: >> On 08/25/2016 12:08 PM, Walter H. wrote: >>> Hello, >>> >>> 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 ...

On 08/26/2016 12:02 AM, Walter H. wrote: > On Thu, August 25, 2016 23:21, ken wrote: >> On 08/25/2016 02:42 PM, Walter H. wrote: >>> On 25.08.2016 20:24, ken wrote: >>>> On 08/25/2016 12:08 PM, Walter H. wrote: >>>>> Hello, >>>>> >>>>> I've got CentOS 6.8 x64, updated today to the latest by 'yum update'

On 08/25/2016 12:08 PM, Walter H. wrote: > Hello, > > 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

On Thu, Mar 28, 2019 at 6:55 AM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote: > > -----Original Messages----- > > From: "Benjamin Hauger" <hauger at noao.edu> > > Sent Time: 2019-03-28 01:31:40 (Thursday) > > To: wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn>, centos at centos.org > > Cc: > > Subject: Re: [CentOS] How to specify

> -----Original Messages----- > From: "Gianluca Cecchi" <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"

On Thu, Mar 28, 2019 at 9:24 AM Gianluca Cecchi <gianluca.cecchi at gmail.com> wrote: > > > 1) In CentOS 6 we have the classical SysV service > file: /etc/rc.d/init.d/kdump > > Supposing you have 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

On 10/30/2016 12:26 PM, Paul R. Ganci wrote: > <snip>I am thinking of putting the CentOS iso out and then booting the > VM into it just to poke around the file system. Otherwise my other > option is to just clone a twin VM on another server and then just > change the networking IPs/hostname. Anybody have any other ideas as to > how to debug this problem? So I booted off

Thank you for the quick response. > Strange way to do this, as libguestfs can do all this. Sorry to ask this (I'm a newly graduated engineer and I new to the virtualization world), but how can libguestfs do all of the above?, do you mean it can create all the partitions inside a new lvm volume or a new raw image?? > Did you copy the syslinux.cfg file into the guest? The error message

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]

On 5/4/2016 12:41 AM, Patrick Begou wrote: > > Any messages in /var/log/boot.log ? indeed, it appears it tries to mount local file systems BEFORE drbd is started. because /data isn't mounted, backuppc can't start either. so do I have to edit the chkconfig priorities in /etc/init.d and recreate the rc3.d S** and K** scripts so drbd starts earlier? ugh. # cat ore

Hello CentOS users, in the recent time I keep getting the logwatch warnings from my 2 dedicated servers running CentOS 7.4.1708. I guess because of the numerous kernel updates (because of Spectre+Meltdown) in the near past? Could someone please suggest me, which files in my /boot partition would be safe to delete? I would like to avoid the situation of having to boot the rescue partiton etc.

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.. --

All of the following is still under the Centos 7 KDE Live CD: If I mount /dev/sda2 on /media and have a look, this is the valid EFI filesystem, including the Fedora and Centos entries. If I try to mount /dev/sda6 on /media it looks to be a valid /boot filesystem. If I mount /dev/sda6 as /boot and mount /dev/sda2 as /boot/efi before running Jim's efibootmgr command will I fix the problem

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

I have a KVM vm running CentOS-6.8 on a host also running CentOS-6.8. This instance is used for occasional development projects which require segregation. Thus it is seldom accessed. At some point in the recent past this guest developed an issue with starting. Specifically these messages were found in the system log files: /var/log/messages-20170312:Mar 10 16:31:06 vhost04 kernel: dracut:

A bit hard to say. Try chrooting into environment and rebuilding initrd? -- Eero 2016-10-30 22:53 GMT+02:00 Paul R. Ganci <ganci at nurdog.com>: > On 10/30/2016 12:26 PM, Paul R. Ganci wrote: > >> <snip>I am thinking of putting the CentOS iso out and then booting the VM >> into it just to poke around the file system. Otherwise my other option is >> to just

On 4 May 2016 09:11, "John R Pierce" <pierce at hogranch.com> wrote: > > On 5/4/2016 12:41 AM, Patrick Begou wrote: >> >> >> Any messages in /var/log/boot.log ? > > > indeed, it appears it tries to mount local file systems BEFORE drbd is started. because /data isn't mounted, backuppc can't start either. > > so do I have to edit the

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