CentOS - May 2017 - 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...
Interestingly, I see in the origin VM, the same UUID as in the cloned 
guest. See below.

I don't know anything about rebuilding initramfs; the whole restore 
process is automatic. (There is a manual method too, but I have not been 
successful with it either.)

# blkid
/dev/mapper/centos-root: UUID="fcee6215-e97a-4a4f-9473-5115f8559683" 
TYPE="xfs"
/dev/vda2: UUID="cey71w-b81q-w1se-0Cww-X2cr-Milx-dWw15Z"
TYPE="LVM2_member"
/dev/vda1: UUID="297e2939-d6f5-431a-9813-9848368ee306"
TYPE="xfs"
/dev/mapper/centos-swap: UUID="b220b45f-ae22-4393-a74d-90b03d37c41b" 
TYPE="swap"

# cat /etc/fstab
/dev/mapper/centos-root /                       xfs defaults        0 0
UUID=297e2939-d6f5-431a-9813-9848368ee306 /boot                   
xfs     defaults        0 0
/dev/mapper/centos-swap swap                    swap defaults        0 0
10.201.40.34:/data/col1/noc-bkups-1   /mnt/dd2500-1   nfs 
auto,noatime,nolock,bg,nfsvers=3,intr,tcp,actimeo=1800 0 0

Any ideas?
> Never used mondorestore to clone a VM, have you done it successfully
before?
I have always had success in all my (numerous) restores/clones with 
CentOS 5 and 6.

I have not managed to have a fully successful (i.e. bootable) 
restore/clone of a CentOS 7 system yet (due to the above issue).

Thanks,
Nick

On Thu, May 4, 2017 at 11:43 AM, Nikolaos Milas <nmilas at noa.gr>
wrote:
> 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...
>
>
> Interestingly, I see in the origin VM, the same UUID as in the cloned
guest.
> See below.
>
> I don't know anything about rebuilding initramfs; the whole restore
process
> is automatic. (There is a manual method too, but I have not been successful
> with it either.)
In rescue mode, you should recreate initramfs. In /lib/modules you
have directories with the installed kernel versions. I guess you shoud
take note of the name of then latest one and run:

dracut -f /boot/initramfs-<kernel_version>.img <kernel_version>

replacing <kernel_version> with the noted directory name...

-- 
Marcelo

"?No ser? acaso que esta vida moderna est? teniendo m?s de moderna que de
vida?" (Mafalda)

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 something?

Thanks,
Nick