search for: supergrub2

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 I booted with CentOS 7 disk in troubleshooting mode (where the virtual disk was automatically mounted without issues) and I tried to repair: http://iweb.noa.gr/files/centos7/el7-rescue-scratchvm-20170502-01.png Also: # grub2-mkconfig -o /boot/grub2/grub.cfg ... /usr/s...

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

...ror. :-( > > I was hoping we were close to a solution... > > > Nick > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > what do you get when you boot the VM (I imagine with supergrub2 you described) and run this lspci lspci -kn in particular in respect with scsi devices ad kernel modules used eg in a VM of mine under oVirt [root at ractorshe ~]# lspci 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PII...

...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 /etc/fstab match the actual UUID as reported by blkid? And remove /etc/lvm/cache/.cache if it exists Marcelo "?No ser? acaso que esta vida moderna est? teniendo m?s de moderna que de vida?" (Mafalda)

...a.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 version (uname -r)? every kernel has it own initramfs where some binaries, libraries, modules and configuration files get copied from the running VM, so you need to boot from a newly created initramfs (which you find in grub2.conf) -- Marcelo "?No ser? acaso que esta vi...

...ere close to a solution... >> >> >> Nick >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > what do you get when you boot the VM (I imagine with supergrub2 you > described) and run this > > lspci > lspci -kn > > in particular in respect with scsi devices ad kernel modules used > eg in a VM of mine under oVirt > > [root at ractorshe ~]# lspci > 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) &g...

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