Latest FOG 0.33b
-
[quote=“Tom Elliott, post: 22173, member: 7271”]r1162 released. Should resize SDR disks after imaging completes. It wasn’t before and I’m sorry I missed that part.
Spelling issues have been addressed as well.[/quote]
with this release new pc inventory (quick inventory from grub fog menu) dont’ work.
pc says: No Host found for mac address xx:xx:xx:xx:xx (is normal… is a new pc!!) 2 times, one at start of inventory and another at end of inventoryno errors in error.log pf apache.
here access.log:
172.24.77.119 - - [30/Jan/2014:12:43:15 +0100] “POST /fog/service/auto.register.php HTTP/1.1” 200 318 “-” “Wget”
172.24.77.119 - - [30/Jan/2014:12:43:23 +0100] “POST /fog/service/inventory.php HTTP/1.1” 200 318 “-” “Wget”i cannot find another errors…
-
Hey Tom,
Updated to new revision and tested windows xp upload/download (single partition). After I downloaded the image to the client and started the os I get a blue screen something with unmountable boot volume.
The upload with the newest revision works fine but something goes wrong with the download. I switched to a older revision and the download and starting the os works fine, looks like that the error occurs with revision 1142 and newer.Good luck by finding and fixing the problem,
Lukas -
Albatros,
You updated to r1162 and are still getting the same issue?
I forgot to add a resize for single disk resize, and corrected that.
You state it only happens on deploy after 1142? I didn’t change the source in a way to modify windows, just the methods it uses for the files. Basically, I just separated the Upload/Download/Checkin Bits so they’re on their own files for easier troubleshooting/debugging.
-
I’m seeing the same thing on r1162, namely xp single partition resizable, failing on the reboot after deployment with unmountable boot volume.
A quick check with fdisk in debug mode suggests that it still isn’t resizing after deployment, as sda1 is much smaller than before the upload and deploy.
xp multi seems to work OK. -
Alright, that leads me down a good path to troubleshoot.
-
Can you guys try with 1163.
I may have made a change without realizing, but I’ve tested resize for this and all seems to work fine. Then again, I could be wrong.
-
r1164 released.
Only main change between both is ntfsresize performs specifically for win7 (different) than win xp.
-
1163 seems to fail the same.
I’m not recreating the image tho.
Getting key message on screen, as per screenshot, I only mention this in passing, I assume it is some debug stuff.
Will try 1164…[url=“/_imported_xf_attachments/0/528_r1163.png?:”]r1163.png[/url]
-
No the key is because I’ve added openssh to the init.gz, this way I can edit the fog scripts from a debug window and send the updates to myself.
-
Sorry, still getting the unmountable boot device, after the deployment at r1164
As I say tho, I haven’t recreated the image, I can try that if you want. -
If you’d be so kind,
I can’t seem to replicate this issue myself.
-
Still the same after uploading a new image.
On the upload I see the resize message after partclone finishes.
The system then reboots OK.
After deploying the image it fails with unmountable boot device.
I haven’t seen the resize on deploy, but it goes through very quickly to the reboot.
Any chance of putting a wait before the reboot?
I’m using virtual box, my hdd is virtual size 30Gb, actual size 9.3Gb.
Will have to go now, but can continue tomorrow evening if needed. -
I’ve just, for me, added a 10 second wait time to the scripts and will do more debugging tonight.
Hopefully I’ll get this narrowed down.
The upload tasks seems to report “Can’t have partition outside of disk.” error even with changing the positioning of the mbr backup, so I don’t think this is an MBR issue, I think it’s more an issue with the partitioning scheme itself.
I think you’re right that it’s not resizing on the deploy, though my disks are coming up full 50GB, while the image device size on resizable is only 4.7GB.
I don’t know what else to look into, but I’ll work at it until I get this narrowed down.
-
think i found a bug in the gui you can’t turn off directoy cleaner or green fog from service management page (all other modules seem ok)
-
r1169 released address the service issues. Also modifies how the services are generated. It’s done from a loop now, rather than the old, individualized method which was just cumbersome.
-
r1170 released.
Neatly to end the night even
Just adds comments to the service files. A minor change in ServiceConfigurationPage.
-
progress bar show dev size when needs to be “space in use” otherwise percent and figures are off… % is correct but total/of size is isn’t
[IMG]http://s28.postimg.org/w4rme1bn1/image.jpg[/IMG]
also just an aesthetics, could the progress bar be set to the width of the header? looks odd being wider
-
[quote=“Tom Elliott, post: 22317, member: 7271”]r1170 released.
Neatly to end the night even
Just adds comments to the service files. A minor change in ServiceConfigurationPage.[/quote]
with this (and previous) release new pc inventory (quick or full inventory from grub fog menu) dont’ work.
pc says: No Host found for mac address xx:xx:xx:xx:xx (is normal… is a new pc!!) 2 times, one at start of inventory and another at end of inventoryno errors in error.log of apache.
here access.log:
172.24.77.119 - - [30/Jan/2014:12:43:15 +0100] “POST /fog/service/auto.register.php HTTP/1.1” 200 318 “-” “Wget”
172.24.77.119 - - [30/Jan/2014:12:43:23 +0100] “POST /fog/service/inventory.php HTTP/1.1” 200 318 “-” “Wget”i cannot find another errors…
i deleted all fog dir /opt/fog/* and reinstalled: no works.
So at the moment i cannot add another pc to inventory.
i used on pc1: dd|netcat xxx.xxx.xxx.xxx 10000 pc2: netcal -l -p 10000 >/dev/sda for the moment to clone pc… is my only way, the inventory don’t work.
Tryed also to delete the db and www root and install the last test release: don’t work.
please fix this problem… is urgent
-
Don’t delete /opt/fog,
delete the Web directory. For ubuntu it’s:
/var/www/fogFor redhat it’s usually:
/var/www/html/fog -
I’ve tried, full inventory, quick inventory, inventory deployment and had no issues so far.
