No Image file found that would match the partition
-
@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 -
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.
-
@msi As George already mentioned we see
Using Disk: /dev/nvme0n1in the picture andd1.partitionssays/dev/sda. Please schedule the deploy task as debug and after the error when it drops you back to the command shell rungdisk -l /dev/nvme0n1and post a picture here. -
-
@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…
-
With raid on from the bios ATA
-
@msi what does the output of
lsblk? -
@george1421 gives blank response.
-
@msi Well I think you found the issue. You do have a hard drive in that computer
-
@msi Just for clarity this is a
dellcomputer booted in uefi mode, with a disk mode of raid-on? -
@george1421 Yes.
-
@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.
-
@george1421 You’re right. You want me to deploy now?
-
@msi I would surely try. The disks can now be viewed.
-
@george1421 Same problem.
