Posts made by Sebastian Roth

@sourcaffeine Is the fog-client actually installed on the machine and running?? Check in the Windows service management. You should see FOGService running.

@processor Please post the contents of the text files d1.partitions and d1.minimum.partitions from that image.

@processor said in Wrong Image Size indicated in the image manager.:

still saying a 500GB hd is too small whereas there is only 80GB of data

Maybe I have missed that in the earlier discussion. Has it always been this exact error?? Can you please post a picture of that error on screen??

@jhalbert said in Dell Precision Tower 3420:

2 sata raid 0

RAID detection is not as easy. @george1421 might be able to help you here.

@pdit Maybe our link detection is failing on this particular NIC. But I kind of doubt this as we simply use standard Linux tools and information from the kernel to figure this out. Really sounds like a spanning tree issue. Different NICs might behave in different ways here.

@sourcaffeine Please take a look at the log on the client (C:\fog.log or C:\Program Files (x86)\FOG\fog.log) and post here.

@virtualdxs You can actually give it a try already! Would be great if you’d join in as tester to help us bring it forward.

git clone https://github.com/FOGProject/fogproject/
cd fogproject
git checkout working-1.6
cd bin
./installfog.sh

@george1421 We skip some of the checks for single partition setups. See here for example: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.upload#L108

@processor Beside what I posted about the mentioned d1.fixed_size_partitions will still be created on upload/capture and seems like we don’t skip the tests for single partition setups on deploy. Therefore it won’t do the resizing on deploy for you. Quick fix as suggested by @Junkhacker, delete that file from your /images/… directory and it should expand.

Many thanks for George who kept asking the right questions to nail this down. I’ll see if it makes sense to add the check skipping for single partition setups on deployment as well.

@klaus-jauk In FOG groups are not like you might be used from other software. It’s more like a tool to push out settings to a group of hosts but it’s mostly not a persistent settings thing where you store information for the whole group. For AD settings, if you set those through the group you’ll see that the values will be shown in the group AD settings as long as you don’t change a value for any of the single hosts. When you do this the value from the group AD settings will disappear.

This is the concept of FOG groups. Search the forums for “persistent group” and you’ll find a lot of information on this.

I see that it’s a bit unfortunate in the case you describe where you register a new host and join that to the group. But on the other hand you’ll still have all the values set for all the other group members. You just don’t see it in the group AD settings view anymore.

@luis-acacio Current Volume Size and New Volume Size are very close together. Is this correct? Is your Windows partition (sda4) only 12870 MB in the first place? I can imagine this being a problem. Wonder that shrinking it does even work!??!

Edit: Possibly the small size is just because there was another issue initially that prevented FOG from expanding the partition after capture and now you are kind of stuck with the small partition. Please boot up Windows 10 and try to expand that partition to it’s full size. Then try capture again.

@kafluke Multicast deployment?

@russel0901 Please post a picture of the ARP timeout on screen. And I may ask you to NOT mask the IP or other information because it can give valuable information on finding the solution.

@chvys10matt Usually we have the file name written like this bzImage32 (upper case I). Please double check the file name on your FOG server as it makes a huge difference in the Linux world.

@Fernando-Gietz Is the one to ask here.

@AdrianW Well that’s interesting. We don’t remove drivers from the kernel usually, at least not by intention to cut out user’s hardware. I think the only time we removed a driver so far was when we saw it conflicting with another one.

I can’t find much information about RTL8167 and linux drivers on the web. It’s really strange. Do you still have your 1.2.0 FOG server around? Could you boot into a debug session and run readlink -f /sys/class/net/eth0/device/driver (make sure you have the correct network interface ethX in the command. Possibly run ip a s beforehand to see which interfaces you have.

@Solo509 Best if you take a picture of the exact error on screen and post here.

From what you wrote so far I would imagine that iPXE is not having the right driver for your USB-to-Ethernet or USB-C adapter. Which iPXE binary do you use? undionly.kpxe, ipxe.efi, snponly.efi, intel.kpxe, realtek.kpxe?? Take a look at /tftpboot/ on your FOG server to see all the different ones you can try.

@george1421 Nice work George!!

@Aysientor Searching the Ubuntu package database it seems to me that you need to install a package called mono-4.0-service (see here).

Edit: That should actually be installed as a dependency when installing mono-complete as suggested in the wiki article.

@jmason Hehe, good find! Definitely something we did no consider when implementing the random nvme fix. The code was only made to try and sort nmve disks when the image type is set to “All Disks”.

As of now I can’t see how we can possibly detect this situation where you want to specify it should only capture and deploy the Windows disk (for example). The algorithm used for “All Disk” is that we save the disk size information along with the image and push out the image to the correct sized disk.

If we stick to that logic we’d need to change from specifying /dev/nvme0n1 and instead add a field to the host configuration where you can put in a certain disk size to detect and use. But this would fail again if you’d have two identical sized disks as it would deploy to a random one again (either overwriting Linux or Windows).

@george1421 @Tom-Elliott I think I have put this off for way too long as I expected it to be complicated to handle in all cases (fresh install as well as updates). But seems like this is fairly easy to accomplish: https://github.com/FOGProject/fogproject/compare/dev-branch...rename-account

It’s still not finished yet but the basis is done and locking down the account won’t be much work I hope as I have done all the research and testing before.

Highly appreciate any comments you guys have on this. I have greped the whole code to make sure I don’t miss anywhere to change the name or handle the new name.