Can't upload Dell Latitude 3440 image
-
No luck yet.
Have tried 4.0 kernel (32 bit and 64 bit). As with all 32 bit kernels, I get a kernel panic that says to use the init= option in the kernel.
I have also set the DHCP 67 option to undionly.kkpxe. Does this need to be set somewhere in FOG also?
-
[quote=“Scott Adams, post: 46817, member: 29589”]No luck yet.
Have tried 4.0 kernel (32 bit and 64 bit). As with all 32 bit kernels, I get a kernel panic that says to use the init= option in the kernel.
I have also set the DHCP 67 option to undionly.kkpxe. Does this need to be set somewhere in FOG also?[/quote]
If you’re serving out the bootfile and next-server via Windows DHPC, you don’t need to change anything on the FOG machine. I think 1.2.0 had some strange going on with kernel updates/changes. I’m not sure that it named the files properly (but I may be wrong), let me find some code to do it manually… found it.
[url]http://fogproject.org/forum/posts/46336/[/url]
[quote=“Tom Elliott, post: 46336, member: 7271”]The kernel that you’re using is 64 bit? The four FOG logos at the top tell me you’re not using a 3.14.2 kernel.
That said, there are newer kernels.
On your FOG Server can you run:
[code]wget -O /var/www/html/fog/service/ipxe/bzImage http://downloads.sourceforge.net/project/freeghost/KernelList/bzImage
wget -O /var/www/html/fog/service/ipxe/bzImage32 http://downloads.sourceforge.net/project/freeghost/KernelList/bzImage32[/code][/quote]Firstly, see the path of those wget commands? /var/www/html/fog/service/ipxe/ file name ??
On ubuntu, it’ll be /var/www/fog/service/ipxe (the paths above are for Fedora).
Secondly, Backup your old ones using cp to <filename>.old before you execute those commands. This way, if something doesn’t go right, you can just cp the <filename>.old to <filename> and you will be back where you started.
-
DHCP options 66 and 67 are set for the scope correctly.
I have downloaded and tried both 4.0.0 and 4.0.0 (32 bit). I rename them from bzImage to 4_0_0 and 4_0_0_32 and am manually using that as the kernel in the host configuration. During the PXE process, it does read the correct kernel, followed by init.xz. However, still hanging on Using Hard Disk /dev/sda
-
This post is deleted! -
This is on upload?
-
Yes sir. On Upload. We are able to upload other images (we just did an Optiplex 360 yesterday). But, we have been unable to upload one for our new Latitude 3440s.
-
As I doubt you’re in the office now,
Contact me via Conversation. If you can, please give me a gmail account we can chat through. I think I know what the problem is.
-
Can someone maybe pinpoint what the solution was here? I too, am not able to capture dell 3440 image. Everything works fine, looks like the image capture completes, then computer reboots. However the image file is empty, showing no data, and the dev folder / mac address has the image in it still? any ideas, I had no issues with dell 3440 on my old FOG 0.32 server on 2.8.8 kernel. I have tried most things above!
-
Can someone maybe pinpoint what the solution was here? I too, am not able to capture dell 3440 image. Everything works fine, looks like the image capture completes, then computer reboots. However the image file is empty, showing no data, and the dev folder / mac address has the image in it still? any ideas, I had no issues with dell 3440 on my old FOG 0.32 server on 2.8.8 kernel. I have tried most things above!
-
@pizzutoitalia
This is the error I get at the end of imaging! Says image copied successfull then this below:Error returned: Type 2, File /var/www/html/fog/lib/fog/fogftp.class.php. Line 107, Message: ftp_login(): Login incorrect., Host: 192.168.1.1 Username :fog *reattempting to update database …Failed.
-
@pizzutoitalia It has been a while, but from what I remember (at least in our environment) our 3440s were using a hybrid drive. I had to write 0s to the drive before loading Windows 7.
My current environment is:
Ubuntu 14.04
SVN 7717
Kernel: 4.5.3
Boot file: undionly.kpxeTurned off secure boot and UEFI.
-
@pizzutoitalia said in Can't upload Dell Latitude 3440 image:
Message: ftp_login(): Login incorrect
That line tells me that it’s FTP related, likely credentials.
This article helps greater than 90% of folks with your problem:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP -
@Wayne-Workman
This has to do with editing the storage node in the FOG GUI. I changed the eth0 to eth1 in storage node, to make the bandwidth monitor on front page work, since then I have not been able to capture images (however the bandwidth monitor works great for deployment). Before that, I captured many images fine. It would appear my problem is that I left the fog SQL password blank, and when editing the storage node via gui, its does not let you save it with a blank password. Upon checking .fogsettings, I found that the password field has " " not ’ '. I have changed it back, and its still not working! Perrhaps I should start over again with a fresh install of ubuntu and fog? I seem to have different passwords everywhere now as I have started trying to resolve this! -
@pizzutoitalia Please do the simple FTP test in that article and see if it works?
-
@Wayne-Workman
I did the test, perhaps I wasn’t clear. I can login to ftp with username fog and password as password, I originally had everything working without a password, however it wants a password now. However I’m not sure where to update the password for FOG ftp in settings. I have edited the .fogsettings in opt/fog and the name and password field were blank. I have updated them to reflect the FOG / Password combo, however the error remains upon trying to capture image.
I have Ubuntu 14.04 with Trunk 7827Cliffnotes: Everything was working until I update the storage node settings via config yesterday. Now I need to understand where to tell fog that I now have a sql password as opposed to blank like it was.
-
@pizzutoitalia You’d set the mysql password inside
/opt/fog/.fogsettingsand then re-run your installer. You’ll see three fields for it. host, username, and password. In most scenarios the user should be root, and password blank.Also - if the MySQL credentials that are set were not good, you wouldn’t even be able to use the web interface at all, whatsoever.
Check what username/password is set in the web interface’s storage management area.
-
@Wayne-Workman
That did Wayne, thanks again for the help. Updating passwords between storage node in gui, and .fogsettings, so they match, was the final answer.
