Thank you for the responses. We found that manually creating the directory the new image was going to and granting rights to that folder corrected the issue.
Posts made by Scott B
-
RE: FogFTP: Login Failed
-
FogFTP: Login Failed
We started getting an error while trying to upload an image. It says [I]FogFTP: Login Failed, Host: <serverip>, User: fog, Password: <password>.[/I]
The password it shows is the correct password. Nothing has changed on that server as far as I know. We have a local “fog” user as well as the fog user within the fog maintenance GUI, not sure which its asking about. Both passwords are the same though. Downloading of images, registration, ect works fine.
-
No DHCP - Really Strange
One a few PCs we have troubles with PC’s taking their image, some do, some don’t. When the ones that fail after booting iPXE and then the FOG menu it seems they will not get an IP from PXE after a reboot. Not sure why, they just got one and are able to get one in windows. It’s like once something goes wrong, it won’t get an IP again. It just gets no offers were received.
-
Using a Tom Elliott Kernel
If I want to use a different kernel how do I go about that? I downloaded “Kernel.TomElliott.3.14.2.64” from the Fog Project page, but I don’t know what to do with it from there.
-
RE: DHCP/BOOTP: Reply not for us
[quote=“Tom Elliott, post: 29500, member: 7271”]All those with DHCP/BOOTP reply not for us/ignoring fragmented packet messages.
A few questions:
Are you using Windows DHCP Server, and if so is option 66 set? Could you possibly try setting the bootp options as well?
Is your next-server setup and/or setup properly?[/quote]
It’s currently a Novell NetWare DHCP server. Option 66 is set.
-
RE: DHCP/BOOTP: Reply not for us
[quote=“Tom Elliott, post: 29445, member: 7271”]Can you give me the P/N or specific model type of DC5800 you have? Maybe mine are different, but I know everything works on them.[/quote]
It seems to only be hit and miss as well. We do have other 5800s that do image, which is really strange. The model is AJ411AV.
-
RE: DHCP/BOOTP: Reply not for us
[quote=“Tom Elliott, post: 29410, member: 7271”]How long does it just “hang”
We have HP DC5800’s as well and everything just works.[/quote]
A good 1m30s - 2m before going to a black screen with just a blinking cursor in the lower left corner.
-
RE: DHCP/BOOTP: Reply not for us
[quote=“Tom Elliott, post: 29394, member: 7271”]Scott,
Can you update your installation to the latest (1.1.0) and see if it helps you out at all? Also, the last I heard with others having similar issues a “reinstall” of FOG corrected the issue for them, though I don’t know what’s causing it in the first place.[/quote]
Updated to FOG 1.1.0 but it didn’t seem to make a difference. Now when I have a PC that does pick up an IP address (HP dc5800) I get the screen below where it just hangs.
[ATTACH]910[/ATTACH]
[url=“/_imported_xf_attachments/0/910_Fig2.jpeg?:”]Fig2.jpeg[/url]
-
DHCP/BOOTP: Reply not for us
What does it mean when you try to image a host and get the message “DHCP/BOOTP: Reply not for us”. I see this at what seems like random when I try to do a quick image. Doesn’t seem to be a specific type of machine either. Eventually I just end up with a black screen and I have to power cycle the PC. Also, something that’s weird is sometimes our PCs just won’t pickup a DHCP address via PXE. Windows works fine. Again, seems like random.
[ATTACH]906[/ATTACH]
[url=“/_imported_xf_attachments/0/906_dhcp1.JPG?:”]dhcp1.JPG[/url]
-
RE: Can't get a HP machine to work upload or download an image.
[quote=“Tom Elliott, post: 29220, member: 7271”]Scott your issue looks to be the first partition does not have the boot flag set on it[/quote]
How does that get set? That was for the 6000.
-
RE: Can't get a HP machine to work upload or download an image.
[quote=“Tom Elliott, post: 29168, member: 7271”][code]gdisk -l /dev/sda[/code]
What’s the output?[/quote]Not hijacking but I have the same issues on two of my HP models. 4000 Pro and 6000 Pro desktops. Below are screen shots of what I’m seeing and getting. Out put from the above command is in the last shot.
[ATTACH=full]899[/ATTACH][ATTACH=full]900[/ATTACH][ATTACH=full]901[/ATTACH][ATTACH=full]902[/ATTACH]
[url=“/_imported_xf_attachments/0/899_Fig1 (800x600).jpg?:”]Fig1 (800x600).jpg[/url][url=“/_imported_xf_attachments/0/900_Fig2 (800x600).jpg?:”]Fig2 (800x600).jpg[/url][url=“/_imported_xf_attachments/0/901_Fig3 (800x600).jpg?:”]Fig3 (800x600).jpg[/url][url=“/_imported_xf_attachments/0/902_Fig4 (800x600).jpg?:”]Fig4 (800x600).jpg[/url]
-
RE: FOG 1.0.1 and older NICs
[quote=“Junkhacker, post: 29161, member: 21583”]if you run
[FONT=Consolas]tftp x.x.x.x get default.ipxe[/FONT]
does it download the file?[/quote]I see what I did. When updating the tftboot files I accidentally moved default.ipxe. Thanks!
-
RE: FOG 1.0.1 and older NICs
[quote=“Scott B, post: 29026, member: 15315”]You were correct, but I still see the issue after performing the step listed. Same error.[/quote]
I’m seeing it on other machines now as well.
-
RE: PXE Files
[quote=“Junkhacker, post: 29036, member: 21583”]depending on when and where you got them, they are potentially different builds of the ipxe compiled from the source code. tom put a lot of work into troubleshooting the issue, and wolfbane8653 did a lot of testing. in the end, we helped the developers of ipxe find a bug in their code. if you have not updated to the latest version of undionly.kpxe, i recommend that you try it.[/quote]
Currently using files from [url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/[/url]. You guys are great with all the FOG development, we do appreciate the work!
-
PXE Files
While testing and troubleshooting I’ve been trying different PXE files, but other then just being a different name, what makes one different then another? How do I know which one I should use other then just a shot in the dark or trial and error?
ipxe.kkpxe
ipxe.kpxe
ipxe.krn
ipxe.pxe
pxelinux.0.old
snponly.efi
undionly.kkpxe
undionly.kpxe
undionly.kpxe.INTEL
undionly.pxe
vesamenu.c32 -
RE: FOG 1.0.1 and older NICs
[quote=“Tom Elliott, post: 29025, member: 7271”]okay,
I’ll be willing to be you have a folder called:
[code]/var/lib/tftpboot[/code] and for whatever reason a fix for this would be:
[code]ln -s /tftpboot/default.ipxe /var/lib/tftpboot/default.ipxe[/code][/quote]You were correct, but I still see the issue after performing the step listed. Same error.
-
RE: FOG 1.0.1 and older NICs
Attached. Did this using both undionly.kpxe.INTEL and undionly.kpxe from code - Revision 1774.
[url=“/_imported_xf_attachments/0/880_error1 (800x534).jpg?:”]error1 (800x534).jpg[/url]
-
RE: FOG 1.0.1 and older NICs
[quote=“Junkhacker, post: 28914, member: 21583”]please update to the latest version in the svn trunk. we believe we may have the issue finally fixed.
details: [url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/page-3#post-28887[/url][/quote]Doing so gives me an error about failed connecting to ipxe.com.
-
RE: FOG 1.0.1 and older NICs
Right now I am using undionly.kkpxe from [url]https://mastacontrola.com/ipxe/latest-DEFAULT-TEST[/url] dated June 1, 2014 and it works with the PCs below. Its not working on a HP d530, endless boot loop.
[LIST]
[]HP dc4000
[]HP dc5700
[]HP dc5800
[]HP dc6000
[]HP dc7700
[]DakTek Discovery 61
[*]DakTek Discovery 81
[/LIST] -
RE: FOG 1.0.1 and older NICs
[quote=“Tom Elliott, post: 28701, member: 7271”]
Weird that you’re having issues with HP DC6000’s as I’ve got about 250 of them and they all, from what I’ve found, work fine with 1.x.x.[/quote]Which pxe boot file are you using?