1. Installed FC25 in Dell Latitude 5490 laptop.
2. Do required configurations.
3. using clonezilla clone to harddisk
4. install image in new machine
5. try to boot. Failed to boot.

Hi gurukap,

Could you provide detail concerning the "failed to boot" part ...

- are these systems BIOS or UEFI based ? Are both the same in this regard ?

- do you even get to the GRUB screen (or whatever boot loader you use) ?

- what error messages are you getting at what stage of startup ?


... Let's start there.

Cheers.

Hi Rickkkk,

Please find the comments bellow -

- are these systems BIOS or UEFI based ? Are both the same in this regard ?
>>Both are Dell Latitude 5490 laptop only ( http://topics-cdn.dell.com/pdf/latit...nual_en-us.pdf )
- do you even get to the GRUB screen (or whatever boot loader you use) ?
- what error messages are you getting at what stage of startup ?
>>After cloning, when we restart the machine it says no bootable disk found. but when we try to load FC25 manually we can see the image and its partitions.

Regards, Uday

Hi Rickkkk,
Can you please help with this?
Regards,
Uday

Post output from bootinfoscript made from any live Linux boot on the not booting laptop and someone may be able to identify a solution.

If you make the image with dd it should work. Clonezilla images are only partial images that need to be restored to a drive before they will boot.

Uday - sorry - been MIA for a couple of days .. almost weeks ..

Clonezilla works best to restore an image made with it to the same machine / hard disk from which it was taken.

In trying to restore your image to another machine of the same type, my guess is you're possibly running into a UUID issue. Your bootable image from Machine 1 may be expecting to boot from a partition with a specific UUID. Since the UUID of the partition on Machine 2 (perhaps even the partitioning scheme altogether) will necessarily be different, your boot loader will be looking for a boot partition UUID which doesn't exist on that machine.

If this is indeed your only problem, you should be able to modify the boot parameters to identify the proper UUIDs. To do this, you would have to boot live into Machine 2 and run lsblk -f to note down the UUIDs of its disk partitions. Then, edit your bootloader's parameters accordingly.

If this still does not fix the problem, further troubleshooting will be required.

Let us know if this helps or if you need more guidance.

Hi Rickk,

Thanks for the inputs...will try and let you know.

-Uday