Capturing W10 on Sata , restoring on NVME = Fail to boot

[mm Ekimia]

Hi,

it seems we did not have this problem before 1.5.7 :

• Capturing on a 250G Sata SSD
• Restoring on a 1 To NVME

Fail to boot with the blue smiley screen.

Is this a scenario where windows cannot boot usually or something on what fog is doing when restoring ?

thanks

[george1421]

Can we rule out the image being at fault here (not saying it is, only wanting to discount that part).

Can you deploy a image back to a sata ssd on a different computer?

The issue I have is that sata ssd and nvme are two different technologies. Each has its own naming convention for partition layouts. This could be the conflict with the naming convention changes.

Another possibility is that the golden image doesn’t have the necessary boot time drivers for the nvme disk controller.

I’m not suggesting that its not a FOG issue, only that there may be other factors too. I know there was issues with disk expansion in 1.5.6 and was being worked on minutes before 1.5.7 was released. But those issues would not cause what you are seeing unless the disk didn’t expand and there is no room left on the drive to start windows.

[mm Ekimia]

Thanks,

TO help the previous image ( W10 1809 like this one ) can be flashed to NVME and SATA without problems.

I also think that this is a naming convention problem

[george1421]

@developers have you heard of a similar issue in the past?

I might also understand that there could be an issue with the windows boot manager since the uefi target device name might change. Let me see if I can get a screen shot of what I’m talking about.

[Sebastian Roth]

@mm-Ekimia said in Capturing W10 on Sata , restoring on NVME = Fail to boot:

the previous image ( W10 1809 like this one ) can be flashed to NVME and SATA without problems.

To me this sounds like it’s not something FOG is doing wrong in general but only it cannot handle your new image.

Please follow George’s hint on trying to deploy this image you have the blue screen issue with to a different SSD disk/computer just to see if there is a general problem with this image.

As well please post the contents of the text files d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions of that particular image you see the blue screen after deploy. You find those in /images/IMAGENAME/... on your FOG server.

@george1421 said:

@developers have you heard of a similar issue in the past?

Not that I am aware of. We use sgdisk --load-backup ... to read the partition layout from a binary backup which doesn’t include the Linux specific disk device namings. As far as I see it the change from SSD to NVMe shouldn’t play a role here. Different naming convention doesn’t matter as far as I know.

[mm Ekimia]

Just a note , I had the same problem ( SATA to NVME ) with CloneZilla , had to fiddle with Windows liveUSB BCD to update the Boot manager

[Sebastian Roth]

@mm-Ekimia From what I read between the lines I can imagine this being a UEFI vs. legacy boot issue or something.

If you still need help with this I ask you to post the information I asked for. Marking as solved for now.