@Sebastian-Roth said in Error on image upload:

@Zourous Would you mind doing the test I suggested (10 times in row to see if USB key is always sdb)?

I tried it 10 times and it was the same each time. I even tried an 11th time with another stick and it was the same. I’m guessing you could probably replicate this on a similar set-up.

@Sebastian-Roth said in Dell Latitude 3540:

@Zourous said in Dell Latitude 3540:

I’m on 1.5.5

Well then you might want to upgrade to 1.5.10 or manually download newer iPXE binaries here: https://github.com/FOGProject/fogproject/tree/master/packages/tftp

I tried to updater to 1.5.10 but ran into new issues so decided to try a newer IPXE binaries as you stated.

This I’m glad to say this worked, so thank you Sebastian.

@Sebastian-Roth said in Dell Latitude 3540:

@jgibson60 @Zourous As for a quick test you can rename the files. Make sure you remember the correct names to restore those later on.

May I ask which version of FOG you two use?

Hi @Sebastian-Roth, I’m on 1.5.5

I’ve just tried all the different efi files available and none of them work for this model.

@Tom-Elliott said in Dell Latitude 3540:

@Zourous The file is already available as part of the base install.

We build:
snp.efi
snponly.efi
ipxe.efi
realtek.efi

Probably a few others, but it’s already in the tftp folder

Not knowing the proper way to do this I’ve renamed ipxe.efi to old and realtek.efi to ipxe.efi and then rebooted the server. Unfortunately it is the same result. Any other ideas please? I could have over 100 of these to image in the coming weeks so quite a big problem for me.

By some chance, I have just googled Dell Latitude 3540 on FOG and have ended up here. I can confirm I have the exact same issue. Where do you get the realtek.efi and where do you put it please?

@george1421 Many thanks that was along the lines that I was thinking but you’ve confirmed my thoughts are correct. I’ll go ahead now and set it up. Thanks again.

Hi George, thanks it was option 2 that fits what I need the best. Just wanted to know in theory that it works. I only need the internet connection to get fog updated on install really. I also wasn’t sure what static address to use for the Fog server if it’s just the server plus another PC. My home wifi uses a class C address and would hand the server an address to use for the internet access. At the same time the Fog server needs to be a DHCP for the one PC that is going to connect to it. I wasn’t sure if this type of configuration with two DHCP’s in use would cause issues.

Is this possible? I would like to have the Fog server on one PC and then image another PC. They would just be connected by a single network cable. The Fog server would have internet access through wireless on my home set-up.

@Sebastian-Roth said in Error on image upload:

@Zourous Did you notice the fixed init files I posted yesterday? See below.

Yes, I’ve just tried them. On a debug test it still shows as before when you type in parted -l /dev/sda, but on the upload I can’t see any issues like in the original screenshot I posted. Thanks for all your efforts.

@Zourous said in Error on image upload:

@Zourous said:

I noticed this and used a tool to take the extra USB partition away again from the image

I am not sure I get this. Which tool did you use to “take away” the USB partition? Do you mean you removed the partition from the USB key before actually uploading or after upload finished?

About the “doesn’t resize”… We need more information on this! Partition layout (d1.partitions from the image directory) and so on.

I just used a tool outside of Windows to remove the inserted USB partition that had made it’s way onto the main image. By doing this I assume it has messed something up and that the partitions are not recalculated when I try to upload the image again because it seems to not shrink the image to the size of the data before upload or then resize it after deployment. Here is the d1.partitions file

label: dos
label-id: 0x86308630
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1024000, type=7, bootable
/dev/sda2 : start=     1026048, size=   249043631, type=7

I noticed there is a d1.fixed_size_partitions file and I tried taking the :2 out of this, but this didn’t solve it.

I think I found the fix on another thread. I just need to run chkdsk / f and it corrects it for the next upload

@Zourous said:

I noticed this and used a tool to take the extra USB partition away again from the image

I am not sure I get this. Which tool did you use to “take away” the USB partition? Do you mean you removed the partition from the USB key before actually uploading or after upload finished?

About the “doesn’t resize”… We need more information on this! Partition layout (d1.partitions from the image directory) and so on.

I just used a tool outside of Windows to remove the inserted USB partition that had made it’s way onto the main image. By doing this I assume it has messed something up and that the partitions are not recalculated when I try to upload the image again because it seems to not shrink the image to the size of the data before upload or then resize it after deployment. Here is the d1.partitions file

label: dos
label-id: 0x86308630
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=     1024000, type=7, bootable
/dev/sda2 : start=     1026048, size=   249043631, type=7

I noticed there is a d1.fixed_size_partitions file and I tried taking the :2 out of this, but this didn’t solve it.