No Image file found that would match the partition

[msi]

@george1421 said in No Image file found that would match the partition:

Can you confirm on your storage node 10.134.200.230, that all of the files for image win_10.1709 exist?

It works for other Dell Desktop. One different is that this PC has SSD instead of HDD. When I created the image, the pc had HDD.

[george1421]

@msi To add a bit more complexity here, not only do you have a SSD, but its a NVMe drive which has a different disk structure than say a SATA SSD.

Just for clarity the screen shot you posted of the directory came from the noted storage node and not the FOG master server?

Can you post the output of cat /images/Win_10.1709/d1.partitions

Also something just noted, is this 5050 in uefi mode or bios (legacy) mode?

[msi]

@george1421 said in No Image file found that would match the partition:

Just for clarity the screen shot you posted of the directory came from the noted storage node and not the FOG master server?

Yes, From the storage node.

Can you post the output of cat /images/Win_10.1709/d1.partitions

Also something just noted, is this 5050 in uefi mode or bios (legacy) mode?
UEFI

[Quazz]

Try formatting the disk first.

I’m going to assume it was unable to deploy the partition tables and thereforer could not match an image file to it (as there was nothing to match to).

I could be way off, but it should be simple enough to find out.

[Sebastian Roth]

@msi As George already mentioned we see Using Disk: /dev/nvme0n1 in the picture and d1.partitions says /dev/sda. Please schedule the deploy task as debug and after the error when it drops you back to the command shell run gdisk -l /dev/nvme0n1 and post a picture here.

[msi]

@sebastian-roth

[Sebastian Roth]

@msi Looks like you keyed in the command too early. Hit ENTER a couple of times after the error till you get to a real command shell…

[msi]

@sebastian-roth

With raid on from the bios ATA

[george1421]

@msi what does the output of lsblk ?

[msi]

@george1421 gives blank response.

[george1421]

@msi Well I think you found the issue. You do have a hard drive in that computer

[george1421]

@msi Just for clarity this is a dell computer booted in uefi mode, with a disk mode of raid-on?

[msi]

@george1421 Yes.

[george1421]

@msi There is a know issue with the linux kernel (Not FOG) booting in uefi mode with disk mode in raid-on. If you switch to ahci mode then linux (FOS) will see the disk. Leave your current debug task running, just manually reboot the target computer, update the firmware with ahci mode, then boot back into fog imaging. Then run the lsblk command again. This time you should see your disk. You can either leave in ahci mode or switch back after imaging.

[msi]

@george1421 You’re right. You want me to deploy now?

[george1421]

@msi I would surely try. The disks can now be viewed.

[msi]

@george1421 Same problem.