similar to: CentOS 7 cloned VM cannot boot

Displaying 20 results from an estimated 700 matches similar to: "CentOS 7 cloned VM cannot boot"

2017 May 03
0
CentOS 7 cloned VM cannot boot
On Wed, May 3, 2017 at 11:24 AM, Nikolaos Milas <nmilas at noa.gr> wrote: > > Hello, > > I'm struggling to make a cloned CentOS 7 VM (under KVM) to work. > > The VM was cloned using mondorestore. Restore appears successful but the VM won't boot; see: > > http://iweb.noa.gr/files/centos7/supergrub2-scratchvm-20170503-04.png Does the UUID of root filesystem in
2017 May 03
3
CentOS 7 cloned VM cannot boot
On 3/5/2017 10:41 ??, Marcelo Roccasalva wrote: > Does the UUID of root filesystem in /etc/fstab match the actual UUID > as reported by blkid? And remove/etc/lvm/cache/.cache if it exists Thank you Marcelo for replying, The directory /etc/lvm/cache/ is empty. And, yes, the UUID matches: # blkid /dev/vda1: UUID="297e2939-d6f5-431a-9813-9848368ee306" TYPE="xfs"
2017 May 04
0
CentOS 7 cloned VM cannot boot
On Wed, May 3, 2017 at 4:55 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 3/5/2017 10:41 ??, Marcelo Roccasalva wrote: > >> Does the UUID of root filesystem in /etc/fstab match the actual UUID >> as reported by blkid? And remove/etc/lvm/cache/.cache if it exists > > > Thank you Marcelo for replying, > > The directory /etc/lvm/cache/ is empty. Dumb
2017 May 04
4
CentOS 7 cloned VM cannot boot
On 4/5/2017 5:56 ??, Marcelo Roccasalva wrote: > dracut -f /boot/initramfs-<kernel_version>.img <kernel_version> I did: # dracut -f /boot/initramfs-3.10.0-514.10.2.el7.x86_64.img 3.10.0-514.10.2.el7.x86_64 and it ended without reporting any error. However, when I rebooted, nothing changed ("no such device: <UUID>. Entering rescue mode..."). Am I missing
2017 May 05
2
CentOS 7 cloned VM cannot boot
On 5/5/2017 5:11 ??, Barry Brimer wrote: > Are the correct volumes referenced in your /etc/default/grub file? Thanks Barry for your feedback. Here is the output: http://iweb.noa.gr/files/centos7/scratchvm-data-20170505-01.png What can you tell from that? Cheers, Nick
2017 May 04
2
CentOS 7 cloned VM cannot boot
On 4/5/2017 5:20 ??, Marcelo Roccasalva wrote: > Dumb question: the file starts with a dot, doesn't show up in "ls" without "-a". Of course, I check with ls -la.It is empty indeed. > Even dumber question: the erroring UUID exist in the origin of > thecloned guest? I guess you have rebuilt initramfs a few times now, > so I believe it is irrelevant...
2017 May 05
0
CentOS 7 cloned VM cannot boot
On Fri, May 5, 2017 at 11:54 AM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 5/5/2017 5:11 ??, Barry Brimer wrote: > > Are the correct volumes referenced in your /etc/default/grub file? >> > > Thanks Barry for your feedback. > > Here is the output: > > http://iweb.noa.gr/files/centos7/scratchvm-data-20170505-01.png > > What can you tell from that?
2017 May 05
3
CentOS 7 cloned VM cannot boot
On Fri, May 5, 2017 at 12:52 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 5/5/2017 1:42 ??, Nikolaos Milas wrote: > > Hmm, it seems that the boot flag should be removed from /dev/vda2 >> partition? >> > > Actually, I tried this and left the boot flag only to /dev/vda1. I > rebooted and I am still getting the same error. :-( > > I was hoping we were
2017 May 04
0
CentOS 7 cloned VM cannot boot
On Thu, May 4, 2017 at 1:12 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 4/5/2017 5:56 ??, Marcelo Roccasalva wrote: > >> dracut -f /boot/initramfs-<kernel_version>.img <kernel_version> > > > I did: > > # dracut -f /boot/initramfs-3.10.0-514.10.2.el7.x86_64.img > 3.10.0-514.10.2.el7.x86_64 when you boot via supergrub2, you get this kernel
2017 May 05
0
CentOS 7 cloned VM cannot boot
On 05/05/2017 12:57, Gianluca Cecchi wrote: grub-install /dev/vda2 didn't work ? > On Fri, May 5, 2017 at 12:52 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > >> On 5/5/2017 1:42 ??, Nikolaos Milas wrote: >> >> Hmm, it seems that the boot flag should be removed from /dev/vda2 >>> partition? >>> >> Actually, I tried this and left the boot
2017 May 05
2
CentOS 7 cloned VM cannot boot
On 5/5/2017 1:19 ??, Gianluca Cecchi wrote: > Could you verify, if /dev/sda is your boot disk, with the command > > fdisk -l /dev/sda > ? It's /dev/vda in my case: # fdisk -l /dev/vda Disk /dev/vda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512
2009 Dec 09
2
Kerio Mail Server - anyone?
Hey guys, I'm trying to install the latest Kerio and it seems to want an older version of libstdc++ which I cannot find anywhere in RPM land (sorry, but I just know gmail is going to mangle this on its way out ) [root at localhost ~]# rpm --install /home/amckay/kerio-kms-6.7.3-7892.linux.i386.rpm error: Failed dependencies: libstdc++.so.5 is needed by kerio-kms-6.7.3-7892.linux.i386
2013 May 30
1
Dovecot 2.2 build rpm on Centos6
> -----Original Message----- > From: dovecot-bounces at dovecot.org [mailto:dovecot-bounces at dovecot.org] > On Behalf Of Burak G?RER > Sent: Thursday, May 30, 2013 10:34 AM > To: Nikolaos Milas > Cc: Dovecot Mailing List > Subject: Re: [Dovecot] Dovecot 2.2 build rpm on Centos6 > > On 27-05-2013 16:56, Nikolaos Milas wrote: > > On 27/5/2013 1:07 ??, Birta
2017 Aug 04
2
Problem switching from LDA to LMTP (with Postfix)
Hello, I am trying to switch from LDA to LMTP on a Postfix/Dovecot setup, but something is going wrong. I have followed the directions at: https://wiki.dovecot.org/HowTo/PostfixDovecotLMTP Here is a session from dovecot.log: Aug 4 12:19:42 vmail2 dovecot: lmtp(3152): Connect from local Aug 4 12:19:42 vmail2 dovecot: auth: ldap(imaptester at noa.gr): unknown user Aug 4 12:19:42 vmail2
2012 Feb 23
0
Transmit NOA (sss) to Dialogic IMG via SIP / Transmisión de NOA hacia Dialogic IMG por SIP
Spanish/Espa?ol: Hola a Tod at s, Estoy en la implementaci?n de una soluci?n a medida en la cual requerimos conectarnos v?a SIP a un IMG de DIalogic y salir hacia otras centrales (MSC) v?a SS7, la conexi?n entre Asterisk y el IMG es SIP, pero como requerimiento necesito enviar un NOA (Nature of Address) con valor 8 por requerimientos normativos, hasta ahora no he podido encontrar como puedo
2008 Dec 29
4
yum cannot find bittorent rpm at dag
I am trying to get the x86_64 isos of CentOS-5.2. I wish to use bittorrent. The last time that I did this I required the bittorent package from Dag's repository. I have configured /etc/yum.repos.d/DagWieers.repo thus: [dag] name=Dag Wieers RPM Repository for Red Hat Enterprise Linux #Also see URL http://dag.wieers.com/home-made/apt/
2017 Aug 04
0
Problem switching from LDA to LMTP (with Postfix)
Am 04.08.2017 um 12:06 schrieb Nikolaos Milas: > Hello, > > I am trying to switch from LDA to LMTP on a Postfix/Dovecot setup, but > something is going wrong. > > I have followed the directions at: > https://wiki.dovecot.org/HowTo/PostfixDovecotLMTP > > Here is a session from dovecot.log: > > Aug 4 12:19:42 vmail2 dovecot: lmtp(3152): Connect from local >
2017 Mar 29
5
names
Hola. Tengo un set de datos importados desde SPSS (que usa etiquetas).- Mayormente, no tengo problemas, pero en una variable puntual veo que las etiquetas de las variables "están" pero la clase del vector no me cierra y los resultados no los usan. Trato de mostrarlo: > na.omit(datos[, .(FORM, Region, Dependencia = B2a, Criterios = D4_Otros.1)]) FORM Region Dependencia Criterios
2009 Sep 22
1
mboot.c32 and FreeBSD
Hi, I'm trying to get FreeBSD 7.2 booting using mboot module from syslinux 3.82. Unfortunately it doesn't seem to work. Here is my pxelinux config: === 8< === label freebsd72-i386-mboot kernel mboot.c32 append /kernels/freebsd/7.2/i386/boot/kernel/kernel single --- /kernels/freebsd/7.2/i386/boot/mfsroot === 8< === Here is the error message I get on boot: === 8< ===
2007 Dec 02
3
rsync hangs when accessing through SSH (Leopard OS X)
To preface, I'm running Leopard OSX and am using rsync version 2.6.9 protocol version 29. Whenever I attempt to sync (using rsync obviously) a folder on my local drive to my web server (netfirms.com is my web host) using SSH, the process hangs. I have to force kill it in order to continue using Terminal. I can connect to my server space using SSH just fine by itself, and I ran