@Arrowhead-IT @Sebastian-Roth @george1421

Ok, il will upgrade to trunk to test

Thanks for ur help, i will try to set up the first solution and i come back to say you whats up
i’ll try to capture with wireshark before i do this modifications

Regards

Hi @george1421, @Sebastian-Roth, @Tom-Elliott

For information, the root cause of the problem seems to be the original partitioning from DELL.
I’ve based my master image on the pre-installed “out of box” Windows 10. Not a good idea…

So i have done a clean install of Windows 10 from a Microsoft ISO, partitioned the disk in two volumes (plus the recovery partition and EFI boot partition automatically created) so we have a and D:, and done again the image process and it worked like a charm!

Thanks team!

@Junkhacker

Ok i’ll try to snapshot my fog vm before upgrade, then try to upgrade.

Seeing that the early uses it generated more problems than I already was in , I preferred board on version 1.2 . I do not remember exactly , but it was impossible to automatically inventory a machine, it had to be done manually , and after it was impossible to launch any task.

I finally found the problem…
After the reboot, the old filezilla server restarted with windows, and bypass the built-in ftp server …

@Wayne-Workman
Yeah i replaced x.X.X.X with IP but it doesn’t work…

i reseted the nfs share on windows server and it works !

@george1421
Hi George,
Thanks for your reply.
I had no infos in the apache logs, so i think you right there was a redirection.
So, i just uninstalled manually fog (mv /var/www/fog to fog.bak & /opt/fog to opt.bak), uninstall mysql with apt-get purge mysql-* and reinstall completly fog from the git dir.
Now it works.
Arnaud

Hello Everyone,

I face a new issue and prefer to update this thread, because it’s very related to it…
I used that trick to switch between “raid on” and “AHCI” during more than one year right now, and it worked well but…

Now we got NVMe SSDs in our new DELL computers, which need to be configured in “Raid ON” as “Sata Operation” to boot on Windows. Do you think that “GetHardDisk” error will be fixed in next versions ?

I can easily reproduce the problem and provide you as many as infos, logs… if needed
I use Fog 1.4 and latest kernel.

Thanks in advance for your work!
Arnaud

Hi @george1421, @Sebastian-Roth, @Tom-Elliott

For information, the root cause of the problem seems to be the original partitioning from DELL.
I’ve based my master image on the pre-installed “out of box” Windows 10. Not a good idea…

So i have done a clean install of Windows 10 from a Microsoft ISO, partitioned the disk in two volumes (plus the recovery partition and EFI boot partition automatically created) so we have a and D:, and done again the image process and it worked like a charm!

Thanks team!

Hi @Sebastian-Roth !
I think the concerned partition is more the drive, because the first partition is the one contains the EFI bootfiles, and the second one the recover (or maybe the opposite)

I’ll try it! But since we works with full flash disks, the concept of defragmentation doesn’t exist anymore, they call it “optimization”. Anyway, i don’t know what’s the difference ^^

I’ll feedback you as soon as possible, i’m away from the company this week.

Arnaud

Hi @cmyron . I had the same issue until i upgraded the kernel version to 4.5.0
Maybe you can try it as well?

EDIT: Same problem without fastboot
I really don’t understand, i had the same computer model, a Latitude 7285 few weeks ago, i’ve did the same partitioning and didn’t get that issue when imaging. The only difference is that the hardware on my current 7285 seems to have been upgraded, with a NVMe PCIe SSD and AMD Chipset controller, versus the previous version which has a SATA SSD and Intel Chipset.

EDIT2: I just received 10 laptops more, the exact same model & configuration.
I tried to image the pre-installed DELL Windows from one of them directly with FOG , and it worked well! There is only one partition for system & datas, which has 230gb. Do you have an idea of what is causing the problem in my partitioning?

@Tom-Elliott
Hey Tom,
Fastboot is turned on, i didn’t know that it could be a problem!
I’ll try this morning to reimage without it
For info, here is the partitioning of the concerned machine

@george1421

Hi George,
Thank you for your reply.
Unfortunately, i got no computers with the same configuration
The Windows 10 version is 1803

Hi Fog Community,

First, i wanna wish you an happy new year and say THANK YOU! I’ve been using FOG since 2 years right now, it’s very efficient and fast to deploy, adapted for professional usages!

I’m posting this because i encounter a little issue when trying to upload my last DELL 7285 master image;
The process is failing at the resizing step, here is what i get:

Updating $BadClust file …
Updating $Bitmap file …
ERROR(34): Could not map attribute 0x80 in inode (miss the number): Numerical result out of range

I tried to do a chkdsk /r /f on the disk before imaging;
and change the compression level from 6 to 0, and type from Partclone Gzip to Partimage but the issue stills the same.

I found this https://forums.fogproject.org/assets/uploads/files/1468447170744-gparted_details_bad.htm?v=b3tf0ilfkio which seems to be the same problem, but it’s like an attached document to a thread that i can’t find

The FOG version is 1.4.4, the kernel is updated.
The machine concerned is a DELL Latitude 7285 running Windows 10.

Thank you in advance for your precious help
Arnaud

EDIT : it looks like to be an issue related to the disk type “nvme”, i’ll try to update my fog server in 1.5.5
EDIT2: i’ve just updated our FOG instance in 1.5.5 with the kernel 4.5.0 x64, the problem stills present

printscreen related:

@george1421 Thank you very much for your time George. I’ll try today and back to you asap

Hey George
Thanks for your help
Yeah i’m sure that’s due to the wrong files specified in my entry configuration, but i don’t know the equivalent file to boot via UEFI, as well i haven’t find anything about it on Internet
I’ll have a look to your topic
Thank you

Hey Guys,

I’m trying to do something “tricky” with our FOG install.
I’ve already customized our PXE boot menu to use isos like dban, live debian…

New project: Using Windows 10 ISO in UEFI!

So i added the PXE boot menu entry like that:

kernel http://${fog-ip}/fog/boot/wimboot
initrd http://${fog-ip}/w10x64/boot/bcd BCD
initrd http://${fog-ip}/w10x64/boot/boot.sdi boot.sdi
initrd -n boot.wim http://${fog-ip}/w10x64/sources/boot.wim boot.wim
boot

Then i configured the DHCP to load ipxe.efi (option 67), and the computer to boot on PXE Uefi

Everything loads Well, but the Windows installation doesn’t find the hard drive, because i think the windows 10 installation is loaded in bios mode (like screen resolution is bad, dell logo isn’t displayed in the loading…)
I think it’s due to the PXE entry configuration, i don’t really know how to configure it to load bootmgr.efi in the ISO…

Thank in advance for your help
Arnaud

Edit: if it can helps, here are the interesting files available in the Win10 iso;
w10x64/efi/boot/bootx64.efi
w10x64/boot/bcd
w10x64/boot/boot.sdi
w10x64/bootmgr
w10x64/bootmgr.efi
w10x64/sources/manyregularfileslikeineverywindowsisohahaha(including boot.wim)