Unable to upload image
-
Thank you Tom for your help!
I think I installed the DHCP server. I believe I just did whatever the standard default install is. I would like the DHCP server to be on the same machine as the FOG server (Is that ok?), and that’s how I’ve been treating it. I’m not sure if I’ve set up my dhcpd.conf (on the FOG server) correctly, but I’ve added the following:
[INDENT=1]option tftp-server-name “10.1.50.1”;[/INDENT]
[INDENT=1]option bootfile-name “prelinux.0”;[/INDENT]Additionally, should I need to change any other options within that file, for example (subnet, option domain-name-servers, etc)? I’m sorry for not mentioning this earlier, but could a problem be occurring because the two Windows machines are both on two networks. One of the networks is the same as the FOG server, and the other is separate from the FOG server.
-
[code]option bootfile-name “prelinux.0”;[/code]
Should read:
[code]option bootfile-name “pxelinux.0”;[/code]You need to replace the letter r with an x.
-
Oh my goodness, I can’t believe I did that! Unfortunately, I’m still getting the same error after making that change and restarting the dhcp server.
-
It’s all good. One issue at a time.
I’m assuming that both the FOG server and the client (the one your trying to upload from) is on the same subnet? Are they behind a switch or a router?
-
I’ve got a little bit of a test if you don’t mind me trying something out.
-
They are both on the same subnet and behind a switch. And I’m game for a test.
-
Try putting these values into your fog’s dhcpd.conf file:
Essentially create a new dhcpd.conf file, and don’t forget to restart the dhcpd service.
[code]use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 10.1.50.1subnet 10.1.50.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
range dyncamic-bootp 10.1.50.2 10.1.50.254;
default-lease-time 21600;
max-lease-time 43200;
option domain-name-servers 10.1.50.1; <-- USE YOUR REAL DNS SERVER IP ADDRESS
option routers 10.1.50.1; <-- USE YOUR REAL NETWORK GATEWAY FOR THIS SUBNET
filename “pxelinux.0”;
}[/code]I hope this helps you out.
One you’re done editing, don’t forget to restart the dhcp service.
For ubuntu it should be:
[code]sudo service isc-dhcp-service restart[/code] -
Things are happening!
[EDIT]
Not good things anymore
-
So it’s, hopefully, working?
-
I was in the middle of recording what I think was an error when all of a sudden the screen looked like [URL=‘http://ak0.picdn.net/shutterstock/videos/529198/preview/stock-footage-television-static-noise-audio-included-black-white.jpg’]this[/URL]. I’m going to try to reproduce it.
-
This post is deleted! -
I don’t see the picture, I’m assuming meant to put in, but no worries,
Just describe what the error message says.
-
So I was able to PXE boot on the Win 7 machine and it produced the following output seen in “2.png” attached below. After a few moments, the screen displayed static that can be seen in “3.png”.
I believed it to be frozen in this state (3.png), but as I was typing this the VM restarted and looks to be functioning again. I’m not sure what happened, but the task is still listed in “Task Management” for all active tasks as “queued” and there is a new empty directory in /images/dev on the FOG server whose name is the same as the MAC address of the machine whose image was to be uploaded.
[EDIT]
Found this post, [url]http://fogproject.org/forum/threads/no-chip-hp-compaq-6910p.202/[/url] ,that may be pertinent. I’m reading through it now myself.[url=“/_imported_xf_attachments/0/450_2.png?:”]2.png[/url][url=“/_imported_xf_attachments/0/451_3.png?:”]3.png[/url]
-
It’s not the error that’s giving you the issue.
Download my kernel:
[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]
Copy it to your FOG Server with the following commands: (ON THE FOG SERVER TERMINAL OR CONSOLE)
[code]sudo cp /tftpboot/fog/kernel/bzImage /tftpboot/fog/kernel/bzImage.orig
cd /tftpboot/fog/kernel/
sudo wget --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage[/code]Then try uploading again. You may have to recreate the task.
-
Ahh okay, I’ll do that tomorrow or whenever is next possible for me. My FOG server is unable to be connected to the internet, so I’ll need to do some extra work to get the kernel onto the machine.
Thanks so much for the help so far! I didn’t expect such quality help from forums this quickly, but you’ve been great!
-
Okay,
I’m sorry about that. The “scribbly screen” as I like to call it, just means it can’t process the kms (kernel mode setting) properly. It should be creating the image though.
-
Hello,
I’m finally able to get started on this again, and hopefully get it working. I’m going to put the kernel you linked above on the FOG server. Just to check, is this a 12.04 64 bit ubuntu kernel?
-
No,
It’s the tftpboot/fog/kernel/bzImage kernel.
-
I’ve put the kernel in /tftpboot/fog/kernel/ then I restarted the FOG server and tried to boot from PXE (Onboard Network Controller). Thats when I receive the errors:
[INDENT=1]tps65010: no chip?[/INDENT]
[INDENT=1]acpiphp_ibm: imb_acpiphp_init: acpi_walk_namespace failed[/INDENT]
[INDENT=1]LocalTalk card not found; 220 = ff, 240 = ff[/INDENT]
[INDENT=1]wistron_btns: System unkown[/INDENT]
[INDENT=1]acer_wmi: No or unsupported WMI interface, unable to load[/INDENT]
[INDENT=1]acerhdf: unkown (unsupported) BIOS version Dell Inc./OptiPlex 96/A14, please report, aborting![/INDENT]
[INDENT=1]Accounting clusters…[/INDENT]
[INDENT=1]…[/INDENT]
[INDENT=1]Cluster accounting failed at 2031117 (0x1efe0d): missing cluster in $Bitmap[/INDENT]
[INDENT=1]…[/INDENT]
[INDENT=1]Filesystem check failed! Totally 25936 cluster accounting mismatches.[/INDENT]
[INDENT=1]ERROR: NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE![/INDENT]
[INDENT=1] [/INDENT]
I’ve been looking around for solutions on what to do, but none have been successful. Do you have any ideas? -
Try following the instructions:
NTFS is inconsistent. Run chkdsk /f on Windows then reboot it TWICE!
Delete the task you’ve created. Then Boot the system and perform chkdsk /f, reboot the system twice after this has happened. They recreate the task and try again.
