I also sent a pull request the the official partclone developer so hopefully this will be fixed as well.
EDIT: Done… https://github.com/Thomas-Tsai/partclone/commit/c0629e1a8e73dbdd165d7ac102b8bc9f6f44dac7
I also sent a pull request the the official partclone developer so hopefully this will be fixed as well.
EDIT: Done… https://github.com/Thomas-Tsai/partclone/commit/c0629e1a8e73dbdd165d7ac102b8bc9f6f44dac7
@kyl Could just be a PATH issue then. Try /bin/touch
instead of touch
on your next test.
@K-Hays said:
>>Start PXE over IPv4
This is way before any kernel options and even before iPXE binaries are being loaded. To me it seems like it does not get an IP via DHCP. Wonder if it does send a DHCP discovery request at all?!
The only thing that can help is wireshark/tcpdump I suppose. Are you aware on how to use those tools? Please take a packet dump and upload here to the forum.
@Abuelika Sorry for taking a while to get onto this. Too many other things going on at the moment. I tried your d1.mbr now and it worked like a charm. Then I looked at the pictures you posted more closely again and I am sure I see what’s wrong here. See the message printed in red:
GPT PMBR size mismatch (234441647 != 61279343) will be corrected by w(rite).
When I first saw this I thought FOG is doing something wrong but then I noticed the second number being smaller than the first and so I tried your d1.mbr on a smaller destination disk and that failed with the exact same error (just different number). You cannot deploy a non-resizable image to a smaller destination disk!
So what you have to do is create a new image in the FOG web UI, e.g. name it MASTERMACOS2017_RESIZABLE
and set Image Type
to “Single Disk - Resizable”. Do not delete your other image yet. Keep this as a backup for now just in case something is going wrong with the resizable image. Now set your master Mac machine to use this newly created MASTERMACOS2017_RESIZABLE
image and schedule an upload task. Let it do it’s job. Then configure the machine you wanted to deploy to use the new resizable image as well and do the deploy. You might want to keep the debug kernel options for now just in case it runs into an error again.
Please let us know how it went and post a picture in case you run into an issue.
@artac There is one step in the installer that should clean up the external repository stuff we used in earlier versions of Ubuntu (“Adjusting repository …” in the last picture you posted). Seems like this did not work on your system as those packages were upgraded to PHP 8.0 already.
I just pushed a change to github (dev-branch 1.5.9.94) to hopefully take care of this. Can you please pull that latest change from github and run the FOG installer again?
Hope we can get your web gui up again as well. Please see my signature on where to find the apache error logs. Valuable information will be in there…
Ahh, now I see. Give me a bit of time with this and I am sure I’ll comes up with a solution to this. Though it might sound like a good idea to set the NVME drive to 512 I don’t think this is wise to do. I have a bit of free time tomorrow and will dive into this more deeply…
@plegrand No manual adjustment of /opt/fog/.fogsettings
needed. The latest dev-branch FOG installer script should take care of this! Please give it a try and let us know if it doesn’t work as expected.
Do i have to run “installfog.sh” once debian upgraded?
Technically it should work without running the installer again but as I said the installer will take care of adjusting .fogsettings file and I suggest you run it.
Sorry @ITSolutions but I have to vote against what you are saying about upgrading. Sure not every FOG trunk version is working perfectly but upgrading (from pretty much any version between 1.2.0 and current) is supported and ideally should work.
@MadsMagnus At some point in time one of the linux distos changed their default web root from /var/www to /var/www/html. To keep things as close to the distro default and make FOG work pretty much the same on all systems the installer adds the symlink. It’s not perfect I know! Somewhere on my todo list back in my mind I have this. I’d love to get rid of the link but there are still too many other important things to fix.
Probably best to delete the FOG web stuff completely and re-run the installer. If you still have issues to access the web gui you’ll find the paths to the apache error logs in the signature below my message. In there you should see what’s going wrong.
Thanks to @P-Schnoeckel I’ll have a chance to debug this issue on an iMac myself. He arranged to send me one of their machines at no cost. Thanks heaps for this!
Will keep you all posted about what I find…
@tomslick Please run the command sudo df -h
and post the output here in the forums.
@Wayne-Workman said:
So, if you start 10 at once, each successive one that starts runs a bit slower.
This slowness does not speed up if bandwidth is freed up by other hosts completing.
Unicast is just the wrong “tool” to send out lots of identical data to many clients… Sorry, couldn’t hold it back.
@Cris13 From the things you posted it seems you have the exact same issue than others using the same NIC model. The issue is specific to that NIC. I have spend hours of work over weeks to look into this and digging through the iPXE and Linux kernel code - source code of both drivers are very similar to some extend but only the iPXE code seems to have the issue.
I was unable to work on this in the last weeks but I still hope we can somehow figure this out and make it work again. It’s just a matter of finding the right needle in the hay stack (more than 8500 lines of C code). Are you keen to get into this. I can give you instructions on how to compile and debug iPXE.
Just for reference:
http://forum.ipxe.org/showthread.php?tid=8296
https://forums.fogproject.org/topic/10261/macos-update-broke-ipxe
https://forums.fogproject.org/topic/10289/boot-from-usb-problem
https://forums.fogproject.org/topic/10043/netboot-problem-new-mac
https://forums.fogproject.org/topic/9269/imac-27-ipxe-boot
https://forums.fogproject.org/topic/9278/fog-1-3-0-pb-with-mac-netboot
https://forums.fogproject.org/topic/10810/multicast-error-with-fog-usb-new-imac
https://forums.fogproject.org/topic/10879/ipxe-boot-with-imac-late-2013
@george1421 said in Is there a way to make FOG compatible with LUKS encryption?:
I’ll start digging into the kernel modules and what needs to be added to the inits to support LUKS. I did it once, so I’m guessing I can repeat the process.
Thanks heaps, that’d be great!
I suppose I need to write a tutorial to that the content doesn’t get lost with time.
Not sure if it’s worth it as I plan to add this stuff to the official configs.
@ITSolutions Thanks a lot for responding to my rather stroppy comment! I am absolutely with you there. Doing a fresh install is always a good idea I reckon. But as we have a lot of users who are kind of new to the linux world I doubt that most of them can handle that kind of advanced administrative tasks that you just outlined in your last post. Easy stuff for people like you and me but…
@Christopher-Drew Are you still active in the forums? Would be great to actually have people around who can test things when I get to work on a fix.
@ultralivre Ok, DHCP seems to work now. Question: Is 192.168.122.190 your FOG server IP?
Please run the following commands on your FOG server console (Linux shell) and post results here:
sudo -i
apt install net-tools
ls -al /tftpboot
ps ax | grep -e inet -e tftp
netstat -antup | grep -e inet -e tftp -e ":69"
@prestop I think I already told you that I can tell you the disk size if you upload the d1.mbr
file to the forum… Or just run fdisk -l /images/MMHOptiplex7020/d1.mbr
and post the full output here…
@aknisly said in Linux FOG Client, Hostname Changer not working:
If I hadn’t been able to get what I wanted with that, I’d be happy to help with the fog-client and the HostnameChanger module, but as it is, unfortunately, I’m pressed to move on to other priorities.
Thanks for being open and honest. Good you were not afronted by my last reply.
I would be happy to make some notes in the wiki (which is still the first place I check) if that is an option. Apparently self-registering an account is disabled?
We work on updating and moving all the contents from the wiki to https://docs.fogproject.org and you are very welcome to help us. Please send me a private message with your github account name and we’ll permit you to the fog-docs repo.