<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 178: Cannot boot from a cloned Linux with KVM</title><link href="https://sourceforge.net/p/clonezilla/support-requests/178/" rel="alternate"/><link href="https://sourceforge.net/p/clonezilla/support-requests/178/feed.atom" rel="self"/><id>https://sourceforge.net/p/clonezilla/support-requests/178/</id><updated>2024-05-31T13:04:20.461000Z</updated><subtitle>Recent changes to 178: Cannot boot from a cloned Linux with KVM</subtitle><entry><title>#178 Cannot boot from a cloned Linux with KVM</title><link href="https://sourceforge.net/p/clonezilla/support-requests/178/?limit=25#883d" rel="alternate"/><published>2024-05-31T13:04:20.461000Z</published><updated>2024-05-31T13:04:20.461000Z</updated><author><name>Steven Shiau</name><uri>https://sourceforge.net/u/steven_shiau/</uri></author><id>https://sourceforge.net56ed6fbcdb4011b5d294e0fe10fba7de102d7f9e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;No, the way you mount LV is not really correct.&lt;br/&gt;
You can try:&lt;br/&gt;
1. sudo -i&lt;br/&gt;
2. ocs-lvm2-start&lt;br/&gt;
3. lvscan &lt;br/&gt;
With the results, you should be able to find the LV device name, say, it's /dev/r100/root, then you can :&lt;br/&gt;
mount /dev/r100/root /mnt&lt;br/&gt;
Your files should be in /mnt/ now.&lt;/p&gt;
&lt;p&gt;Steven&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#178 Cannot boot from a cloned Linux with KVM</title><link href="https://sourceforge.net/p/clonezilla/support-requests/178/?limit=25#d42d" rel="alternate"/><published>2024-05-21T00:39:45.489000Z</published><updated>2024-05-21T00:39:45.489000Z</updated><author><name>Steven Shiau</name><uri>https://sourceforge.net/u/steven_shiau/</uri></author><id>https://sourceforge.net16367b066761145663c4925c573fef79fc8da51a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;From the photo you posted (https://sourceforge.net/p/clonezilla/support-requests/_discuss/thread/c7f8a3e25d/71fe/9f73/attachment/RescueMode_2024-05-07.PNG), it seems your data are in /dev/sda2 and /dev/mapper/r100-root. Therefore you can mount them and copy files.&lt;br/&gt;
As for restoring the image to another type of VM, well, it might let you boot and enter the system you have restored.&lt;/p&gt;
&lt;p&gt;Steven&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#178 Cannot boot from a cloned Linux with KVM</title><link href="https://sourceforge.net/p/clonezilla/support-requests/178/?limit=25#4ac6" rel="alternate"/><published>2024-05-20T05:20:06.767000Z</published><updated>2024-05-20T05:20:06.767000Z</updated><author><name>Steven Shiau</name><uri>https://sourceforge.net/u/steven_shiau/</uri></author><id>https://sourceforge.net5e9710dc09f127968896f37e7fc98f2b85833469</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;So any progress there?&lt;br/&gt;
It occurred to me that maybe you can try to restore the image to a VM on different type of software, e.g., virtualbox or VMWare workstation.&lt;/p&gt;
&lt;p&gt;Steven&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#178 Cannot boot from a cloned Linux with KVM</title><link href="https://sourceforge.net/p/clonezilla/support-requests/178/?limit=25#18a1" rel="alternate"/><published>2024-05-18T10:00:28.253000Z</published><updated>2024-05-18T10:00:28.253000Z</updated><author><name>Steven Shiau</name><uri>https://sourceforge.net/u/steven_shiau/</uri></author><id>https://sourceforge.net53550174dc70e0e4d1c8818ce55adab3abff2475</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Did ou try to mount the device you have? If the cloning finished, and the cloned OS failed to boot, it's only a matter of booting issue. Your data still exist and you should be able to mount and copy them.&lt;br/&gt;
BTW, you have two posts, and I suggest you focus on one of them.&lt;/p&gt;
&lt;p&gt;Steven&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#178 Cannot boot from a cloned Linux with KVM</title><link href="https://sourceforge.net/p/clonezilla/support-requests/178/?limit=25#a8e6" rel="alternate"/><published>2024-05-17T21:35:56.066000Z</published><updated>2024-05-17T21:35:56.066000Z</updated><author><name>Steven Shiau</name><uri>https://sourceforge.net/u/steven_shiau/</uri></author><id>https://sourceforge.nete793f254b03fb51e396406ea2736601b610501d2</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I am currently traveling, so I will be  online sometimes.&lt;br/&gt;
Your case looks like is only the booting issue since you mentioned your system entered rescue mode. As I mentioned, have you used Rocky Linux rescue mode to recreate the initrd?&lt;br/&gt;
It should be something like:&lt;br/&gt;
&lt;a href="https://www.cjcheema.com/2019/06/17/how-to-recover-or-rebuild-initramfs-in-centos-7-linux/" rel="nofollow"&gt;https://www.cjcheema.com/2019/06/17/how-to-recover-or-rebuild-initramfs-in-centos-7-linux/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Steven&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#178 Cannot boot from a cloned Linux with KVM</title><link href="https://sourceforge.net/p/clonezilla/support-requests/178/?limit=25#71fe" rel="alternate"/><published>2024-05-05T06:19:52.230000Z</published><updated>2024-05-05T06:19:52.230000Z</updated><author><name>Steven Shiau</name><uri>https://sourceforge.net/u/steven_shiau/</uri></author><id>https://sourceforge.net6a834bba12ea43c1867aaeb3af2028bf9d5c1278</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Have you tried the latest one, e.g., 3.1.2-22 or 20240408-noble:&lt;br/&gt;
&lt;a href="https://clonezilla.org/downloads.php" rel="nofollow"&gt;https://clonezilla.org/downloads.php&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;BTW, maybe you can try update the initrd using the Rocky Linux rescue disk to do that. Just google "rocky linux rescue disk" and you should find some info.&lt;/p&gt;
&lt;p&gt;Steven&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#178 Cannot boot from a cloned Linux with KVM</title><link href="https://sourceforge.net/p/clonezilla/support-requests/178/?limit=25#d2e5" rel="alternate"/><published>2024-04-30T17:58:21.904000Z</published><updated>2024-04-30T17:58:21.904000Z</updated><author><name>Mike Faynberg</name><uri>https://sourceforge.net/u/mf-hsq/</uri></author><id>https://sourceforge.net2b72ea38b2bf807d515beebf2864b84190655f8a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I would also like to add one more symptom (looks strange to me at least). When I insert the clone disk while the system is running - being booted from the source disk - the system does not even see it. Should it be like this?&lt;br/&gt;
Thank you!&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Cannot boot from a cloned Linux with KVM</title><link href="https://sourceforge.net/p/clonezilla/support-requests/178/" rel="alternate"/><published>2024-04-25T19:27:14.144000Z</published><updated>2024-04-25T19:27:14.144000Z</updated><author><name>Mike Faynberg</name><uri>https://sourceforge.net/u/mf-hsq/</uri></author><id>https://sourceforge.netc355e6e7a8a3c675a25f006bbd18f222f7fd5b9a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I was trying to boot the system replacing the system disk with the newly made clone (using Clonezilla ver. 3.1.2-9-amd64) - and it failed miserably taking me into the emergency mode. The system Is Rocky Linux (which serves as a KVM-based virtual host for a secondary OS). I would like to understand what could go wrong and whether I need to do any changes to that clone in order to make it bootable - and how to make those changes.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>