update: when I ask a host to upload a master image I get this error which may be explaining why the ftp server isn’t working.
Populating /dev using udev: udevd[2278] error creating poll fd: function not implemented.
As the images are still being stored in /dev rather than /images.
I have left the fog u/n and p/w to the defaults of fog/password so I’ll try that.
There currently is no password entered in fog-sftp-ftp-password. should there be a default one? tftp-host is the same ip as the fog server itself we i presume is also correct.
Apologies, i didn’t realise the ftp was how fog moved the folders.
Thank you!
Update: I think it is the image creation process as when I create a new image and save to default storage node (/images) it does not create a subdirectory for the upload to save in causing the previously posted error. Is this just my sql or the svn?
If it is just me, would you be able to help solve the problem please?
Thanks
Info:
in fog settings.
fog storage nod is: fogstorage
fog storage node pass: random password that i presume sql created, should this be the defined one I entered during installation?
@Tom Elliott
Another problem that might just be me but hoped i could run it past you.
The upload master image and registrations works fine however I am now having problems with the mysql and image location. On install i left the storage node as default /images, pulled an image like I would usually however it is not creating the folder in /images and appears not to be pulling correctly as the image info shows size on client as 5.00GiB and size on server as 0.00GiB.
The only thing in the /images folder is /dev and /postdownloadscript. Hope this helps.
I have tried the install with both leaving the root mysql password blank for all instructions and creating a password and entering it on request as well.
No apology needed! I wouldn’t have a clue about half the functions that fog does on the back end.
Cpasjuste, I had the problem with clamav, I just cd’d into the directory and created the folder myself, solved the problem.
I ran the cd usr/share on the ubuntu based server. Client is windows so presumably wouldn’t have the same file structure however on inspection of our old working “non svn” fog server, it doesn’t have the fog folder within /share either so not sure there.
I somewhat understand, not exactly sure about how sh and bash interact, will go and do some reading whilst you fix the problem.
I presume when fixed, a new checkout pull from svn will be needed?
Hey all,
After listening to some previous advice I have recently installed the svn fog version to help with partition uploads.
Installed fine in a ubuntu virtual box enviroment.
Fog version: 2784
Image:
Windows 7
Multiple partitions, single harddisk, no resizable.
Error when trying to image registration.
[CODE]Starting logging:ok
Populating /dev using dev : error creating poll fd: function not implemented
Done
Initialising random number generator done
starting network
ssh-keygen
starting sshd:ok
/bin/fog.man.reg: /usr/share/fog/lib/funcs.sh: line 28: syntax error: bad for loop variable
Reboot: starting system.
[/CODE]
Thanks in advance.
UPDATE: I just ran “cd /usr/share” to discover there is no fog folder. Not sure why it wasn’t created on install?
I’ve found the instructions for how to download it but would you be able to explain “svn”.
I will open a few of the laptops and check then. I would like to hope that a bulk purchase from dell themselves, everything would be identical.
All the laptops are exactly the same model, bought at exactly the same time with all the same spec so space should be a problem. They all have the same master image on them from a previous master image, I just modified the old master to add two new partitions and then uploaded a new master.
The error is debug mode is still the same:
Then it drops out of fog and reboots.
Treat me as a fog noob please…
After recording the error I can confirm some of the details.
It doesn’t begin to image any of the partitions.
It begins with “erasing current mbr/gpt then i get, ebr signature of logical partition invalid read 0x000 required 0xAA55 error reading logical partition”.
To which it then exits fog and reboots.
Hey Tom,
It is Fog 1.2 running on Ubuntu 13.10
The image is a multiple partition single disk.
The project I am working on is to create a customer recovery partition on a laptop so there are currently 4 partitions as follows:
System Reserved F: 100GB NTFS
183GB NTFS
Back up image G: NTFS 50GB
Recovery E: NTFS 5GB
The image previous to this only had the usual system reserved and C:, therefore using a single disk resizable has worked thus far.
So after successfully pulling the new multiple partition image from the host to server, I then tried to push it to a new host to which is failed. (Call this V1)
The anomaly occurs when I pull from the host to the server but tell the image to be sector by sector. It pulls as expected ( slowly ) then pushes and overwrites as it should, problem solved. HOWEVER, when I then try and push the previously failed multiple partition image (V1) it pushes fine, windows loads.
My thoughts were it must be something to do with the overwriting of the partition table, obviously the sector by sector forces the new partition table by rewriting the hard drive sector by sector with the new image. However since (V1) will successfully push once the sector by sector has worked, therefore implementing the required partition table but does not work before.
Hopefully that all makes sense and you can shed some light on the situation.
Thanks in advance!
Hi all,
So I have had fog thrown at me by my company and told to make it work. Single partition stuff has been fine, we are just working on a faster solution using a GigE switch. However we have been unable to get any image using multiple partitions to work.
It is a windows 7 64bit image with 4 partitions. I have managed to pull the image from the master however it does not push properly (giving a typical winload.exe error) however if I do a sector by sector push first, it works and then allows the original multiple partition image to be cloned over the top, presumably because it now has the correct partition table in place with the correct sizings.
Could someone help/analyse our system to help the multiple partition image please.
Thanks.