[SOLVED] Can not download Kernel - 2.6.35.7 PS (and other problems) - im a n00b
-
Hi
Thanks for the speedy reply.
Technically, it freezes at about 60mb on the 2nd partition.
I have a static ip on “wired connection 1”
I have set the address, netmask, gateway and dns server (theres only 1)
Cheers
-
[quote=“flex, post: 4691, member: 1530”]Hi
Thanks for the speedy reply.
Technically, it freezes at about 60mb on the 2nd partition.
I have a static ip on “wired connection 1”
I have set the address, netmask, gateway and dns server (theres only 1)
Cheers[/quote]
It makes it through the initial 100Mb windows partition then croaks on the second one. You had no problems uploading the image though? -
Yup, assume so. Image uploaded almost perfectly. It would freeze every 10 seconds for about 5 seconds but the switch would keep flashing so it must have been transferring.
Im curious, is there a way of restarting the tftp service? Or restarting fog without rebooting ubuntu? i manage a nagios server and there is a restart switch for that.
Many thanks
-
try this command sudo /etc/init.d/atftpd restart
-
paul@FOGServer:~$ sudo /etc/init.d/atftpd restart
sudo: /etc/init.d/atftpd: command not foundi did a search for atftpd now . using apt-file search atftpd
it found it within /etc/init.d so i did:
cd /etc/init.d
I then ran atftpd restart and i got this:
root@FOGServer:/etc/init.d# atftpd restart
The program ‘atftpd’ is currently not installed. You can install it by typing:
apt-get install atftpdI guess it deleted itself or something. Im going to try to install and see what happens.
(as you can tell, i’m pretty useless when it comes to ubuntu )
-
well… i dont think that went well…:
root@FOGServer:/etc/init.d# apt-get install atftpd
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages will be REMOVED
tftpd-hpa
The following NEW packages will be installed
atftpd
0 upgraded, 1 newly installed, 1 to remove and 42 not upgraded.
Need to get 62.0 kB of archives.
After this operation, 46.1 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 [url]http://gb.archive.ubuntu.com/ubuntu/[/url] precise/universe atftpd i386 0.7.dfsg-11 [62.0 kB]
Fetched 62.0 kB in 0s (523 kB/s)
Preconfiguring packages …
(Reading database … 193528 files and directories currently installed.)
Removing tftpd-hpa …
tftpd-hpa stop/waiting
dpkg: error processing tftpd-hpa (–remove):
subprocess installed post-removal script returned error exit status 1
No apport report written because MaxReports has already been reached
Processing triggers for ureadahead …
ureadahead will be reprofiled on next reboot
Processing triggers for man-db …
Errors were encountered while processing:
tftpd-hpa
E: Sub-process /usr/bin/dpkg returned an error code (1) -
did you do updates on ubuntu before you installed fog?
sudo apt-get update && sudo apt-get upgrade -
ah. no. I did it from ubuntu desktop. I’ll do now.
-
I have also seen that I needed to change the tftp password to match my own. I’ve left it as password. so i did that. additionally the FOG_PXE_IMAGE_DNSADDRESS was pointing to 127.0.0.1 (itself) I changed it to the fog servers ip (which is still itself)
Doing these changes still failed.
-
I do my ubuntu install, then do all my updates and upgrade, then I set my static IP address. From there I make sure I still have an internet connection and go get the fog_x.xx.tar.gz file. From there I create my install directory just like the user guide says to, then unzip and install
-
About your kernel issues, I am not sure why you cannot download the kernel you wanted using the fog GUI interface. If you can download it from source forge, the kernel lives in the /tftpboot/fog/kernel directory. the default kernel is bzImage, rename that to bzImageold. rename your new kernel bzImage and move it to that directory and that may or may not help with your crash on image deploy.
-
fog_rookie, you are a genius. Yup. tftp is working once again after the update. It failed first, then when I went to restart, it showed, “partial upgrade” and it upgraded tftp.
I now have a screenshot of where it freezes.
[ATTACH=full]137[/ATTACH]
[url=“/_imported_xf_attachments/0/137_20120712_082800.jpg?:”]20120712_082800.jpg[/url]
-
it only took it 2 seconds to fail there. How big is the hard drive on the machine you are trying to push this image to?
I see its a 297.99 GB partition it is trying to restore. And the only time I have seen FOG fail this quick was when I was trying to push an 80 GB image onto a 40 GB hard drive. -
Nope. both 320gb. I opened up both cases and doublechecked.
Looks like the tftp server is still playing up. I rebooted and still issues.
I tried re-imaging the pc and it didnt like the tftp password so the job was not started. I reset it to the default one and restarted ubuntu. I tried restarting the job, but now the tftp issue is back!! - Doh!
I just connected up another machine and set it to dns.
The ip’s are
router = 192.168.0.1 (1)
my fog server = 192.168.0.254 (254)gateway = 1
DNS = 1
DHCP = 254this machine happily connects to the internet.
-
try restarting the tftp again using that ‘sudo /etc/init.d/atftpd restart’ command, since you reset the password back. I am about to call it a night here. Hope i have helped at least a little bit.
-
Thnaks Fog_Rookie! You have been most helpful.
I had to do sudo /etc/init.d/tftpd-hpa restart to get it back up and running again. I’m re-uploading the other hp8100. This time with the older kernel. Maybe it was a problem with that.
-
Good luck. If I helped in any way shape or form please hit the like button
-
What version of Ubuntu are you using for your server? It sounds like you may be using 12.04 because of the tftpd-hpa issues, which is a common problem with 12.04 and documented on these forums.
I hope your deploy goes well with the different kernel.
-
Hi Chad.
Yes it is 12.0.4!! - Hmmn… Is there a way of downgrading? - I’ll research the known issues and weigh up the cost. I now know a lot more about fog and could probably rebuild the whole thing in about 1 hour. Might be worth it!
-
Oh BTW. After restarting the server one more time and manually starting tftp-hpa, all worked like clockwork