similar to: Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel

Any error in your host logs? On Sunday, 30 October 2016, Steven Tardy <sjt5atra at gmail.com> wrote: > > > On Oct 30, 2016, at 3:27 AM, Paul R. Ganci <ganci at nurdog.com > <javascript:;>> wrote: > > > > grub> set root=(hd0,msdos2) > > grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 > root=(hd0,msdos2)/ > > grub> 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

so, Just chroot to mountpoint: http://www.cyberciti.biz/faq/unix-linux-chroot-command-examples-usage-syntax/ chroot /mounted/path /bin/bash and then .. mkinitrd (see man page for documentation) 2016-10-30 22:57 GMT+02:00 Eero Volotinen <eero.volotinen at iki.fi>: > A bit hard to say. Try chrooting into environment and rebuilding initrd? > > -- > Eero > > 2016-10-30

> On Oct 30, 2016, at 3:27 AM, Paul R. Ganci <ganci at nurdog.com> wrote: > > grub> set root=(hd0,msdos2) > grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 root=(hd0,msdos2)/ > grub> initrd initrd-plymouth.img > grub> boot Try the initrd matching the kernel?

Hi all. I''ve got a situation with Fedora 18 on a dual Xeon E5506 box, 16GB RAM, Tyan S7002 motherboard with the latest BIOS. Because of all the issues, I''m starting to think maybe there''s something wrong with the box itself, maybe something strange going on with the BIOS or mobo resources. Although this box was in service without incident for about 2 years prior. I

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

I have a system with two CentOS 7.1 guests. When I created the VMs I did not have enough storage space in the default location /var/lib/libvirt/images so I moved the default location to a directory /home/vmimages. While this configuration is functional I regret creating a new storage pool in /home. I would like to create a separate partition to place the VM images removing them from their

Hello, I have installed the Xen 4.1.1 and a working kernel 2.6.32.43 which supports Xen on a Ubuntu Linux 10.04 LTS. However, I have never successfully booted the Hypervisor and Dom0. The screen is always black after some kernel messages rapidly go by. I think that I may pass the wrong parameters to the kernel or Hypervisor with GRUB2. Can any one share his/her working grub.cfg for GRUB2 with

On 12/22/19 12:07 PM, Rowland penny via samba wrote: >> >> Are there any suggestions to to fix the problem? >> > Cached record somewhere ? > > You seem to have done everything correctly. > Okay I discovered that any changes to my DNS are not being seeing by bind.? So exploring the Wiki

Hi All, A while ago I replaced a Samba AD on old hardware with a another AD on newer hardware. Everything went smoothly including the demotion of the old AD. However after I did some cleanup DNS records and turned off the old hardware I noticed that there still was a NS record associated with the old AD. So I went to the wiki page https://wiki.samba.org/index.php/DNS_Administration and

I updated to CentOS 4.5 yesterday and now I am finding the snmpd daemon is logging reams and reams of these messages: May 20 10:40:03 mx01 snmpd[2572]: Connection from - 127.0.0.1 May 20 10:40:03 mx01 snmpd[2572]: transport socket = 12 Is there a way to turn off this useless logging? I am getting these every 5 minutes (every time MRTG updates my MailScanner statistics). So far what I tried

I just did a fresh minimal install of centos 7 on new hardware. While playing around with window systems I removed X windows like so: >yum remove "X Window system" and then tried to re install >yum group install "X Window system" which gives this error: Maybe run: yum groups mark install (see man yum) No packages in any requested group available to install or

I have some hardware running CentOS 7 and Sernet Samba 4.7 that started out as a member server that I would like to make into a 2nd DC. However I am having trouble converting it because it seems I am not removing all the remnants of the client setup. What I thought I would have to do is this: 1.) net ads leave -U administrator 2.) Remove the machine entry on the 1st DC 3.) mv /var/lib/samba

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Hardware specs: Dell PowerEdge R410 32GB RAM DDR3 1TB RAID-1 HD (Perc H200 RAID controller) Processor: 2 - Intel XeonE5620 2.4Ghz 12M Cache Turbo HT 1066MHz SO: Debian Squeeze last update: 14/10/2010 uname -a: "Linux spo-r1-u4 2.6.32-5-xen-amd64 #1 SMP Fri Sep 17 22:00:48 UTC 2010 x86_64 GNU/Linux" At boot, xen-hypervisor is loaded

Hai, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Paul > R. Ganci via samba > Verzonden: woensdag 1 januari 2020 23:49 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Cannot remove old NS record > > On 12/22/19 12:07 PM, Rowland penny via samba wrote: > >> > >> Are there any suggestions to

On 05/28/2016 01:35 PM, Alexander Dalloz wrote: > Am 28.05.2016 um 21:03 schrieb Paul R. Ganci: >> Starting httpd: Syntax error on line 31 of >> /etc/httpd/conf.d/olddomain.conf: >> RewriteCond: bad argument line '%{REQUEST_URI}!^/test/ > > You missed a whitespace between the server variable %{REUQEST_URI} and > the value you test against. In both cases you did.

Recently my wife received an Email addressed from jdavidson4 at home.com. When she tried to reply to the original message her reply bounced with ----- The following addresses had permanent fatal errors ----- <jdavidson4 at home.com> (reason: 553 5.3.5 system config error) ----- Transcript of session follows ----- 553 5.3.5 home.com.nurdog.com. config error: mail loops back to me (MX

I have a CentOS 6.6 system running KVM with a Win 7 Pro VM. Over the weekend I was playing around with the VM trying to get it to see my Samsung Note 4. Apparently I removed the phone without removing the hardware from the VM. Now the VM will not start because Device USB 0438:6860 is not there. I tried to remove the hardware from the VM using virt-manager but that does not remove the error

I have caching-nameserver-7.3-3 installed on a Centos 4.2 system. The named.conf file which comes with the install has the following options: options { directory "/var/named"; dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; <comments snipped> }; However, when I look in /var/named/data

On 04/12/2018 08:51 AM, Kay Diederichs wrote: >> I tried running: >>> yum groups mark install "X Window system" >> and get the same message. I tried different permutations removing the >> "s" on groups. Nothing seems to bring back the yum "X Window system" >> group. Can anyone help me resolve this issue and tell me what I did wrong?