Host registration: hdparm: ioctl 0x304 failed: Inappropriate ioctl for device
-
Tom, I think you’re on to something here. I will have my colleague reset his switches and other devices.
About this pxelinux.cfg/default - I edited this file before when I changed ip-address. All seems fine there.We well try going trough switches etc. and post back later. Thanks
-
I hope this helps you. I only, yesterday, learned about this all. Good Luck!
-
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]
-
There are a few options that you should look into other than configuration. I just know, for my setup, if I don’t have the trailing slash, it causes the same type of issue. The other things to look into would be the Network itself. Make sure that the path to the router/switch is relative free of collisions and/or broadcasts. Things that seem to affect the network adversely are Devices that use broadcast messages to communicate such as Apple’s Bonjour service (iPads, iPhones, iPods, Airplay) especially if they’re setup to communicate wireless to another endpoint. Also check your kernel and make sure it’s not a driver issue. If fog can’t recognize your network card, it would also give this issue. I would almost point out that it could be the hard drive setup as well. Though the kernel’s I use seem to be able to work on AHCI mode, maybe the kernel you’re using can’t recognize it. Does the system recognize a hard-drive (/dev/sda, /dev/hda, etc…)?
Also, start small to help in troubleshooting. Try just emplacing a single router or switch to the host you’re trying to image and the fog server. This will help you troubleshoot whether it’s a network issue, or a driver issue.
Thank you,
-
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.
-
What, else, have you tried? Have you tried alternative kernels? Have you tried debug mode to see if you can find an issue specific to network or hard drives? It isn’t just going to be configuration. There are many different things that could be the cause of the problem.
-
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.
-
Yes it could be the network. Not necessarily a network driver issue, but something is preventing the system from communicating with the FOG Server. On your alternate system, these aren’t occuring.
-
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.
-
so you have two tftp servers running on the same network?
-
Not at the same time, I shut down the one server and started the other one.
-
Hello everybody.
Tom Elliott did the trick: [url]http://fogproject.org/forum/threads/kernel-cannot-open-proc-partitions.5487/#post-14450[/url]
-
Sorry all,
I forgot to read that you guys were having the issue with FOG 0.33b. I posted all of this information on FOG 0.33 Bugs forum as well.
