Server 1 and server 2 are installed at the same ESX-server with the same infrastructure and same settings.
The test PC were always the same.
Server 1 and server 2 are installed at the same ESX-server with the same infrastructure and same settings.
The test PC were always the same.
Tried upgrading the kernel, tried older versions and the kernel from the other FOG installation.
It is the same piece of hardware, so can it be a problem with network or hard drives even if it works with the other FOG installation?
The error is the same at both installations but on the older one the deploy and the image process works even though.
The point is, that both systems standing in the same environment, at the same switch etc.
It makes no sense at all for the moment.
I looked into my pxelinux.cfg and all entries are with a trailing slah at the end. So this is not the problem
[ATTACH=full]378[/ATTACH]
Also the entry in the FOG Configuration is /fog/ as base directory.
[B]I remember, that the old FOG server has the same error but continues with making image, deploying etc. The new FOG server displays the error and does nothing or aborts.[/B]
[url=“/_imported_xf_attachments/0/378_tftp.PNG?:”]tftp.PNG[/url]
I think it is a hash for the pass instead of displaying the real password.
The wrong pass was the same problem for me but not showing in the error you got.
Nice to know, that the problem is solved now
[quote=“altitudehack, post: 14115, member: 23”]Hey Sebastian. Thanks for linking to the other thread. What was the solution? Using a different FOG server? What is the difference between the two?[/quote]
No solution until now.
The second server does not work until now, installed out of SVN from 12. July. I have done everything like the first machine, configuration etc.
I tried to change the kernel, downgrade, upgrade, reinstall, nothing seems to work until now!
[quote=“robjoh, post: 14109, member: 2831”]No luck. I do not have any idea what causes this.
What is really strange is that older models, which I know for certain work on another FOG server, does not work on this FOG server.
I think our solution here will be a full FOG server reinstall. :eek:[/quote]
I tried to reinstall FOG several times. Does not fix the problems.
The crux is that we tried everything with the same hardware to image and on the one machine it works without problems and on the othder machine (new installed FOG 0.33 on Ubuntu LTS 12.04.2 x64) it does not work and we get the error mentioned above.
I do not understand what has changed, also tried to change the kernel, downgrade, upgrade, changed the kernel with the one from our old, working install, no positive effects.
Had nearly the same problem here:
[url]http://fogproject.org/forum/threads/host-registration-hdparm-ioctl-0x304-failed-inappropriate-ioctl-for-device.4494/[/url]
No solution until now.
Tried to update or degrade the kernel, tested all SATA modes and it is remarkable that on the same computer with different FOG versions and different Ubuntu version I got one time no problems and the other I got that error.
[quote=“robjoh, post: 14104, member: 2831”]Same problem here with HP ProBook 6475b. Boot Options set to UEFI Hybrid with CSM and Clear SecureBoot Keys.
It does however work on some 6475b-machines.[/quote]
I would say it is a problem with the actual version of FOG or with the Linux version used. Which version do you used at your ProBook?
Where is the problem to not using Multiple partition, single disk?
It is the option working allmost everytime for me.
Do you want to shrink all to online one partition without the 100mb partition?
Hello,
we have a problem at the “Full register host” option. When we try to register a host the error message “hdparm: ioctl 0x304 failed: Inappropriate ioctl for device” appears.
It is a 0.33 Beta out of SVN from 12. July build on a Ubuntu LTS 12.04.2 x64.
We tried changing from IDE to AHCI and just new installed the FOG.
We also have a 0.33 Beta at an Ubuntu Server 12.10, working without problems, also build from the SVN but a short time ago
We always used the same computers to try, so it is no problem with the computer. HP Compaq 8200.
Regards
Sebastian
[quote=“Kevin, post: 11146, member: 3”]translate.google.com[/quote]
I know the Google Translator, but if she is able to speak and write english she also can do it, right?
I thought this forum is international and English is THE international language.
Almost everybody speaks English. I also do not write in German just because I am an native German speaker.
[QUOTE]Hello,
I work on a sony vaio vpcz with 2 hard disk 64gb in raid 0. When i want to upload an image, it loads bzimage “hard disk done”, Then i have the error "unable to move /images/dev/xxxxxxxx to images/“image name”. It’s not the first time i load an image, so i don’t think it’s an error permission. In the image management i am in “multiple partitions image - all disk”. If i put “multiple partitions image - single disk”, i have an error message “device not found”. Can you help me
Thank you[/QUOTE]
I have nearly the same problem and postet in another topic, I try to figure out how to fix the error but at the moment I can not understand why it still is not working.
When I try to upload an image to an NFS share mounted from an Synology everything works ok until:
Image uploaded
Task complete!
* Unable to move /volume1/images/dev/% to /volume1/images/%
FTP Host: 192.168.%.%, Error: ftp_rename(): /volume1/images/dev/*: No such file or directory
%=placeholder
FOG writes the data into the /dev/-folder but can not move it to the /images folder, is that right?
The folder is there with the .img-files in it. I also tried to make an directory with the name of the image but the message is always the same.
Sorry, but can you write it in english, I think that the most people do not speak your language…
Hello,
I want to use an NFS or CIFS share to store the images on the Synology.
I tried to mount it and share it but I get the error message: exportfs: /images/dev does not support NFS export
I also read that it is not possible to share an shared and mounted directory.
Is there another way to use an NAS to store the images because FOG runs on a ESX server without harddisks?
Same error here. Changed the password from the user fog (linux user fog) to the password from the linux user fog and now the problem is solved.
I did not find a solution. Now the speed slows down at ~ 15%. With FOG and Clonezilla the same. The network is not responsible, I also changed switches etc. and Macrium Reflect is done in about 15 minutes for one PC.