Latest FOG 0.33b
-
I tested it again and maked a screenshoot and there I see /dev/sda1. How I wrote in my post number 830, something goes wrong at the first time, but after starting the deploy again. Partclone and fog then works fine.
-
Alright,
Found the issue. Needed to wipe out the MBR/GPT structures which is now implemented.
r1194 released should correct this issue.Thank you,
-
[quote=“Tom Elliott, post: 22525, member: 7271”]Alright,
Found the issue. Needed to wipe out the MBR/GPT structures which is now implemented.
r1194 released should correct this issue.Thank you,[/quote]
I updated to new revision, same problem. After starting the task again, all works fine then.
-
[quote=“Albatros, post: 22521, member: 16710”]Edit:
Forgot to mention that at upload, fog shows me something with “unary operator expected” in file fog.upload at line 258, 262, 266.[/quote]I found this issue and already fixed it. It’s because of the variable call in the script. Sorry I forgot to wrap them in double quotes.
r1195 released should fix that issue.
-
[quote=“Albatros, post: 22526, member: 16710”]I updated to new revision, same problem. After starting the task again, all works fine then.[/quote]
Did you restart the system after updating. If not, it’s still using the old/bad init.gz
-
I updated to revision 1195,restarted the system and overwrote the init.gz with that from the subversion directory.
Sorry same problem. -
Can you do me a favor Albatros,
I’ve seen on a couple instances where the installfog.sh doesn’t update all the files appropriately, for some reason.
Can you try directly copying my init.gz to your /tftpboot/fog/images folder, reboot the client and try again?
-
I deleted the init.gz from /tftpboot/fog/images/ directory and placed there your init.gz. Same problem
.
I am now away, see you later -
If you get a chance, can you try re-uploading the image, then deploy?
I’m thinking the MBR checking got screwed up somewhere and this is why it’d doing a double deploy issue. I’m not seeing the issue anymore.
-
Anyone Here handy with debugging scripts?
-
Hey tom how you been. I can take a look and ask around and see if I can find any issues with it
-
If you’re up-to-date on the revision (current 1195) then please take a look in src/buildroot/package/fog/scripts/bin/fog.download
There’s some bug in there I’m unable to track down. I’m guessing it’s between the MBR parts and the Partclone parts, but I just can’t see it.
-
A couple of bugs in fog configuration, pxe boot menu page, under advanced configuration options.
- textarea box not being populated with FOG_PXE_ADVANCED setting from globalSetting table.
- FOG_PXE_ADVANCED, only written to pxemenu, not saved to globalSetting table as well.
I’ve also increased the size of the text area.
Relevant for us as we have several other entries in the boot menu, dell diags etc.
fixed in the attached file.
[url=“/_imported_xf_attachments/0/538_FOGConfigurationPage.class.zip?:”]FOGConfigurationPage.class.zip[/url]
-
Ok I am looking into it now.
-
I will definitely take a look. I am preparing to go to the hospital for a CT Scan and possibly biopsy, so I’ll be out for a couple hours probably.
When I get back, so long as I’m not drugged too badly, I’ll try to correct this.
-
ok good luck man take care.
-
Hope all OK, been through similar myself.
-
Alright so I’m a work horse.
r1196 released. I made some more changes to init.gz though I doubt they’ll work so will need more debugging I’m sure.
FOG Configuration page now saves the PXE Advanced, though slightly different than how jbsclm recommended, it’s ultimately the same.
Thank you,
I’ll see you all later.
-
r1197 released to fix a typo i made for the advanced Text info stuff.
It should display if there’s information to pull from FOG_PXE_ADVANCED
If not, it works like we’re used to.
-
I’m still using FOG 0.32. I really miss two features: in image manager i’d like to know the date of when latest upload of the image was done. Knowing the date of when it was created is of no use, I think. Could this be implemented? In the client manager i’d like to know when each host had the latest deploy. Deploying a lot of notebooks now and then it not done by deploying a whole group as I deploy a machine when an employer come to my office with problems. It is quite hard to keep track of who I have to get in contact with as it it long time since last deploy. If the latest deploy date could easily be displayed in the host list that would be nice. Any thoughts about this?
