Thank you for the reply. I am all set now. Seeing the fogproject user had me confused. I wasn’t aware of the username change.
Thanks again for the help.

@george1421 Awesome! Thank you, George!

So this can get marked as resolved. Everything worked as expected except when you update the nodes the GUI did not show the new version until after we updated the Master. All the issues we had with 1.5.4 were resolved with 1.5.6. Very happy with this update.

GUI is super fast!
The freezing on formating MBR/GPT on start of imaging is back to only a few seconds. Replication seems to be acting normal again.

Thanks for the help.

At this point I’m not sure if we’ll have the opportunity to test this, as we may have identified some other issues with our specific setup, we’re looking into some possible changes into how we manage our printers. But I’m sure we’ll have a need to use this method in the future.

@Sebastian-Roth
Gparted fixed it with the “check” command, running what appeared to be the same commands I entered at terminal.

I’ll try to capture it again after I’m more confident the box is ok.

thanks guys

@jconway1006 What do you mean by doesn’t halt?? Just take a picture with a camera the moment you see the message on screen.

@bnorwood Sorry for my late reply…

Please try the last command again exactly as I posted:

ls -1 /sys/class/net/ | grep -v lo | xargs -n1 -I{} bash -c 'echo -n {} :" " ; basename `readlink -f /sys/class/net/{}/device/driver`'

In the picture I see that the first quote before the echo a back tick was used instead of a single quote.

Edit: I just saw the kernel version and I can imagine you still have one of the old kernels that had the Hyper-V slowness problem in it. Please update the kernel (FOG web UI -> FOG Configuration -> Kernel Update) and see if that makes a difference.

@Sebastian-Roth

Yeah I would rather not re-build my DB from scratch if at all possible. I have fewer hosts now than when I started with FOG but it’s still a large number. I am in the process of setting up another FOG server to do a fresh install and go from there. I do need to clean some things up in there so it may be the time to do this. I did run through the Troubleshoot MySQL Database Maintenance Commands and didn’t get real far with it. I"ll look at that once more before I bite the bullet on starting over.

I’ll post back to the other thread I started. Hopefully I can figure something out without having to re-do the entire DB…

Thanks for all of your help! I know you guys put in a ton of time with FOG and it’s very appreciated!!

Cheers!

Joe

@phishphan Issue here is that you have a second recovery partition (type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC) as fifth partition. FOG is not able to move that partition around and therefore cannot actually shrink your layout to fit on the smaller disk.

Let’s do the maths. sda5 starts at sector 974862336 and is at least 1908736 sectors in size: (974862336 sectors + 1908736 sectors) * 512 bytes sector size = 500106788864 bytes ~ 465.76 GBytes

That’s about the size of disk you need to be able to deploy this particular disk layout to it. In case you would remove the fifth partition (not saying you should as I don’t know your setup enough) the maths would be: (1161216 + 330329656) * 512 ~ 158.07 GBytes

@tandersb If you want to debug the issue, the best advice on debugging I can provide is here: https://forums.fogproject.org/post/124470 This is a fog admin that is trying to use a qnap and is getting a similar result.

@kenneth-sisco I know it took you a long way to get here, but its great when you can pinpoint the root of the error and fix it knowing that its not just some random crud that may reappear when it will hurt the most.

@Quazz ok.

It’s okay, I managed to solve the mistake. I placed myself in the root folder

cd /root vim.curlrc

Once I got in, I went in.

proxy=http://nom_or_ip_address_of_proxy:port/

then register and restart the installation of Fog

Great! Let’s mark this one as solved. In short, the issue for the kernel update was related to the permissions on the /var/www/fog/service/ipxe folder, which was a confirmed bug in version 1.4.4.

I’ll move the other issue to a new thread. Cheers!

@Sebastian-Roth Very thanks Sebastian for answer and link

@Sebastian-Roth The password error solved the capture issue. I have successfully captured the image. Thanks for the help! I will start another thread on the Hyper-V slowness issue.

@Sebastian-Roth yes, can be closed thanks.

FOG needs to be able to resolve the name you defined as a host name in fog to the target system using DNS. So if you can open a command prompt and ping Win10_AT and it works then you have everything setup and fog should resolve and show these systems as up. The only other thing is FOG doesn’t use the icmp ping command to check status but FOG tries to connect to udp port 445 on the target computer. So you need to make sure that udp port 445 is enabled in the target computer’s firewall.

So to restate this in list form:

The hosts to be able to be resolved by name by DNS The host have udp port 445 open in the windows firewall.

This is only informational (green or red mark in the host list) and does not impact the function of fog if you choose to ignore it.

@JerJer said in Trouble with booting to windows:

@george1421 the computer names are nifferent from fog names. Would they all have to be changed manually?

If you want the fog errors clear when you list the hosts then you need to have the fog name match the real system name and fog will need to be able to find the systems using dns lookups.

@ErwinBullen said in Imaging from Storage node fails:

I tried to mount and extract the image, but do not get beyond this error

Sorry for that. Please try this:

mkdir -p /mnt/images mount -t nfs 192.168.100.32:/images /mnt/images zcat /mnt/images/B-Blok-v18-v4/d1p2.img | partclone.ntfs --restore --restore_raw_file --ignore_crc -N -f 1 -s - -O /tmp/d1p2_deployed.img

Hint: Again make sure you do this on a system where you have enough space in /tmp or where ever else you have enough room to dump the extracted image for testing. Maybe best to mount an empty extra disk in /mnt/test/ and write the output file there.

As well please run ls -alR /images on your storage node and post output here.