Deploy on sata disk image captured on nvme disk

[lebrun78]

Hello,
Fog is able to deploy an image captured on an nvme disk to a machine with a sata disk.
But on restart, the fstab is not good and the machine remains stuck in the busy box.
Do you have any advice to solve this problem?

[george1421]

@lebrun78 I take it the target OS is linux? If that is the case, I’m pretty sure that FOS Linux doesn’t mess with the fstab file. The other issue is even if it did via a post install script, may systems use grub and grub would need to rebuild the initramfs file. Its pretty complicated to explain, other than I don’t think it will work nvme to sata, or sata image to nvme because of the initramfs file.

[Sebastian Roth]

@lebrun78 said in Deploy on sata disk image captured on nvme disk:

But on restart, the fstab is not good and the machine remains stuck in the busy box.

This was mostly an issue back when device names (e.g. /dev/sda1) were used in fstab. Pretty much all modern distros use UUIDs instead. Please let us know the Linux OS you use and post contents of /etc/fstab of the original system.

@george1421 said:

… grub would need to rebuild the initramfs file …

Sure GRUB can be an issue. But from the sounds of this topic I would think this is beyond GRUB already and maybe fixing the fstab isn’t too much trouble anymore (either before capturing or through postscripts (chrooting to the cloned Linux OS).

[lebrun78]

@sebastian-roth
Hello Sebastian,
The distrib is ubuntu 20.04.
I tried to edit the fstab from

/dev/nvme0n1p2   / 		ext3    errors=remount-ro    0 1
/dev/nvme0n1p3  /lereste     ext2    defaults        1 2

to

/dev/sda2   / 		ext3    errors=remount-ro    0 1
#/dev/nvme0n1p3  /lereste     ext2    defaults        1 2

It was not enough.
Boot repair did the job but it is a complex process difficult to reproduce.

[Sebastian Roth]

@lebrun78 said in Deploy on sata disk image captured on nvme disk:

It was not enough.
Boot repair did the job but it is a complex process difficult to reproduce.

If you need further help with this, then we need more information

[lebrun78]

@sebastian-roth
Here is the photo of the error I get on first boot.:(

Il have no raid configuration neither on source or destination machine.
So I don’t understant why I get errors with mdadm files.

If I edit the /etc/fstab file, I always have the error “ALERT! /dev/nvme0n1p2 does not exist”