Categories

• Announcements

  Get the latest news on what's happening.
  168
  Topics
  706
  Posts

  T

  @Tom-Elliott said in Ubuntu is FOG's enemy: apt-get -y remove unattended-upgrades This saved my bacon, thank you very much, first command failed but second one worked, i have also run the unattended-upgrades command, once again thank you.
• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  1970
  Topics
  15833
  Posts

  

  @george1421 After having a chat session with @jeremyvdv which we had to cut short I discovered somethings. I asked him to post the output of the kernel parameters from a debug session. cat /proc/cmdline loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 web=http://10.16.3.129/fog/ consoleblank=0 rootfstype=ext4 mac=00:00:00:00:00:00 ftp=10.1.5.8 storage=10.1.5.8:/volume1/images2/dev/ storageip=10.1.5.8 osid=5 irqpoll hostname=LP0045 chkdsk=0 img=test10 imgType=n imgPartitionType=all imgid=5 imgFormat=5 PIGZ_COMP=-10 hostearly=1 pct=5 ignorepg=1 isdebug=yes type=up Where we can see the storage path for NFS is 10.1.5.8:/volume1/images2/dev but looking on the nas via FTP there is no reference to /volume1/images2 its just /images2, yet there is data in /images2/dev/<mac_address> directory. So NFS is working and FTP is not. If we looked at what he posted as a screen shot of the nas storage node We can see that he is clearly calling out /volume1/images2 When he connected via ftp to the nas the path was /images2/dev/<mac_address> like we see from the top picture here. So what I’m thinking is that we leave storage path at /volume1/images2 and set the FTP path to /images2 then it should work. I think NFS is looking at it form the filesystem view where ftp is looking at the path from a logical view. They technically point to the same location, just how they get there is via two different paths.
• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  9466
  Topics
  93480
  Posts

  

  @Beyondlimitation said in PXE Client tries to find wrong file: By the way, if i copy “undionly.kpxe”, paste it in directory “/tftpboot” and rename it to “undionly.kpxe.0” pxe boot successfully works While I see you have it sorted out, requiring the boot file to end in a “.0” was a requirement of DNSMASQ before 2.76 (as well as syslinux). With 2.76 and later its just the file name. The “.0” requirement was removed since that is a bios related thing. What version of dnsmasq are you running (i.e. dnsmasq -v)
• Developers

  Report bugs, request features, or get the latest progress.

  General

  Feature Request

  Bug Reports
  2049
  Topics
  19294
  Posts

  J

  Excellent George, I will give that a try. Thanks for the feedback!