@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.

@franck25 So we were very close in my early posts. I’m glad you now have a solution!!!

@jrm Enabling HTTPS means that you need to recompile the iPXE binaries as well to add your local CA certificate. We added that functionality to FOG in 1.5.5 and fixed it in 1.5.6. I am sorry but we can’t put much effort into backporting those changes to 1.5.2 as we have way too much to do with current changes and requests. Let me suggest you look into the current version of the iPXE compile script that comes with FOG 1.5.6. Maybe download and try this: https://github.com/FOGProject/fogproject/blob/master/utils/FOGiPXE/buildipxe.sh But as well you probably need to adjust apache configs manually.

@MFuchs135 Please run the following commands and post a picture of that here: sudo -i cd /home/user/FOG-Imaging-Server/tmp ls -al cat binaries1.5.6.zip.sha256

@Qweeqweg the change from using an account named “fog” to an account named “fogproject” is recent. in spite of directions, people kept creating and using an account named “fog” as their user account when setting up the server.

Hi George and thank for your attention ;-) We get the error each time computer should reboot or shutdown if we mark the option in the deploy/capture task and yes, you are right, we even get the error executing ‘reboot’ command at FOS. It’s exactly the same issue that @sudburr describes here: HP ProBook x360 11 G1 EE Notebook PC succeeds but fails at exit But, as it was an old thread, i’ve opened a new one. This is the error I get: https://ibb.co/mhYpyG1 Which is exactly the same as @sudburr’s video. I think it’s still online. I have tried all options i could, but i’m getting out of ideas Thanks!

@Sebastian-Roth ok done ;) https://forums.fogproject.org/topic/13329/1-5-6-small-local-disk-and-the-rest-unallocated

@jemerson93 said in Assistance with unattend script: I also no longer need to have separate unattend scripts for Windows 7 and Windows 10 MBR and Windows 10 GPT. Excellent!! There are a few new options in Win10 unattend file but you can bypass them and as you found you can make the unattend file almost universal. That’s one less bit you have to constantly manage.

@Sebastian-Roth Upgraded to 1.5.6 as you suggested. It seems to be a bit faster, but i need to do the corrections on the server with the same values. Now i’m experiencing another issue posted as https://forums.fogproject.org/topic/13328/fog-snapins-not-ordered-on-launching-time

Hi Sebastian, With all of the other posts I had up, this was related to my unattend script and completely unrelated to FOG. This is resolved! Thank you for the help.

Thanks for the reply, and no worries about losing track. You’re doing great work, and I appreciate you supporting the community. :) I’ll try out some different options and see if I can get one to work better, and let you know if I need any more help on this one. I posted another question in which @fry_p mentioned your name to see if you’d have any thoughts there. If you have some time, maybe you can help determine what’s up there too. :)

@Sebastian-Roth Alright, good to know for the future. Since I didn’t have a clear fix, I blew up the VM and am starting from scratch. There were only two images anyway.

@Quazz Thanks for the help. I really appreciate.

@george1421 Well, potentially that was a resize bug in the inits if you’re using an NVME drive. Could also be the mount failing for some reason? Just some ideas.

An issue was found in 1.5.6 that calls for an early next release to fix that. Find the details here if you run into problems with FTP connections on kernel updates or storage nodes in 1.5.6: https://github.com/FOGProject/fogproject/issues/311

Thank you all for your responses. Thye have been very useful. I’ve been able to do it using a real machine. It was indeed a Virtualbox problem.

Thank you @george1421 for giving me such a complete answer. My greatest concern was looking as if I had attempted something like a cold boot attack, but if something onboard such as IME is going to show logs then I really wouldn’t bother. It’s not worth finding out if they care to distinguish, so thanks for your advice. In regards to potentially angering people like yourself, I’m grateful you were still fair to me! I didn’t take any steps that were contrary to IT’s mandate, we are after all a team. Maybe they will approve the request. :) FOG was a means to satisfy a curiosity (NDI) but will prove to be much more useful and fun with my own half-broken Desktops. Have a good one!