• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. lperoma
    3. Posts
    L
    • Profile
    • Following 0
    • Followers 0
    • Topics 9
    • Posts 40
    • Best 3
    • Controversial 0
    • Groups 0

    Posts made by lperoma

    • RE: Update to working-1.6 fails with mysql: unrecognized service

      @Tom-Elliott Success. I switched to single-user with init 1, and installing systemd-sysv worked fine.

      As this is a machine upgraded from debian 11, maybe it wasn’t using systemd. Installation of 1.6 worked no problem Thanks,

      posted in Linux Problems
      L
      lperoma
    • RE: Update to working-1.6 fails with mysql: unrecognized service

      @JJ-Fullmer

      mariadb -V
      mariadb Ver 15.1 Distrib 10.11.6-MariaDB, for debian-linux-gnu (x86_64) using EditLine wrapper

      posted in Linux Problems
      L
      lperoma
    • RE: Kernel Panic - not syncing, unable to mount root

      @bwilli78 my dell machine was wrongly identified as 32bit and sent bzimage32. You can: 1) update to dev-branch 1629 I should help. Or 2) send bzimage to 32bit machines. (Because they are wrongly identified).

      This could be your issue. I don’t see FOG sending bzimage32 anyway. Just a gut feeling. May be wrong.

      posted in FOG Problems
      L
      lperoma
    • RE: Kernel Panic - not syncing, unable to mount root

      Is your machine trying to boot bzimage32 ? send a picture if you can.

      posted in FOG Problems
      L
      lperoma
    • RE: Attempting to join domain: The parameter is incorrect, code = 87

      This worked for me :

      Domain name: subdomain.domain.tld
      OU: OU=Computers,DC=SUBDOMAIN,DC=DOMAIN,DC=TLD
      AD DEFAULT USER: adminuser
      Domain Password: supersecret
      Name Change/AD Join Forced reboot?: cheked

      Not sure if I was doing anything wrong, I tried too many things, but this now works. Thanks.

      posted in FOG Problems
      L
      lperoma
    • RE: Chainloading failed, hit 's' for the iPXE shell

      I have the impression this issue has something to do with DHCP server in the gateway competing with proxydhcp in the fog server.

      I have updated DHCP settings in Unifi to allow / block DHCP traffic (DHCP Guarding). I have included FOG’s dhcppxory address and seems to be working ok now.

      posted in FOG Problems
      L
      lperoma
    • RE: Update to working-1.6 fails with mysql: unrecognized service

      I have created links in /etc/init.d for mysql and mysqld -> mariadb.

      Installation seems to progress now a little better, I’ve updated the schema, but still get these errors:

      * Setting up and starting MySQL..........................System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
mysql.service points to "mariadb" which is not a valid unit name: Invalid cross-device link
mysqld.service points to "mariadb" which is not a valid unit name: Invalid cross-device link
OK
* Testing connection to database..........................OK
* Setting up MySQL user and database......................Skipped
* Backing up user reports................................Done
* Stopping web service...................................OK
* Setting up Apache and PHP files.........................OK
* Testing and removing symbolic links if found............OK
* Backing up old data.....................................OK
* Copying new files to web folder.........................OK
* Creating config file....................................OK
* Creating redirection index file........................Skipped
* Downloading kernel, init and fog-client binaries.......Done
* Copying binaries to destination paths....................OK
* Enabling apache2 and php services on boot...............OK
* Creating SSL Certificate................................OK
* Creating auth pub key and cert..........................OK
* Resetting SSL Permissions...............................OK
* Setting up Apache virtual host (normal).................OK
* Configuring PHP FPM.....................................Done
* Starting and checking status of web services............OK
* Changing permissions on apache log files................OK
* Backing up database.....................................Done

* You still need to install/update your database schema.
  This can be done by opening a web browser and going to:

    http://192.168.0.21/fog/management

* Press [Enter] key when database is updated/installed.

* Update fogstorage database password.....................OK
* Granting access to fogstorage database user.............Skipped
* Setting up storage......................................OK
* Setting up and starting DHCP Server.....................Skipped
* Configuring default PXE file............................OK
* Setting up and starting TFTP Server.....................OK
* Setting up and starting VSFTP Server....................OK
* Setting up FOG Snapins..................................OK
* Setting up FOG Snapins..................................OK
* Setting up FOG Services.................................OK
* Setting up and starting NFS Server......................OK
* Configuring UDPCast.....................................OK
* Building UDPCast binaries...............................OK
* Installing UDPCast......................................OK
* Installing FOG System Scripts...........................Failed!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! The installer was not able to run all the way to the end as something has caused it to fail. The following few lines are from the error log file which might help us figure out what’s wrong. Please add this information when reporting an error. !!
!! As well you might want to take a look at the full error log in /root/fogproject/bin/error_logs/fog_error_1.6.0-beta.2141.log !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

install -m 644 udp-receiver.1 udp-receiver.1 /usr/local/share/man/man1
install -m 644 rateGovernor.h /usr/local/include/udpcast
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
root@fogserver:/root/fogproject#

      FOG seems to run ok for the moment, despite install errors. Is it OK to use ?

      posted in Linux Problems
      L
      lperoma
    • Update to working-1.6 fails with mysql: unrecognized service

      Update to working-1.6 fails with mysql: unrecognized service

      System: Debian 12, upgrading from 1.5.10.1629.

      See: fog_error_1.6.0-beta.2141.log

      * Setting up and starting MySQL..........................System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
mysql.service points to "mariadb" which is not a valid unit name: Invalid cross-device link
mysqld.service points to "mariadb" which is not a valid unit name: Invalid cross-device link
Failed!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! The installer was not able to run all the way to the end as something has caused it to fail. The following few lines are from the error log file which might help us figure out what’s wrong. Please add this information when reporting an error. !!
!! As well you might want to take a look at the full error log in /root/fogproject/bin/error_logs/fog_error_1.6.0-beta.2141.log !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

ii  vsftpd        3.0.3-13+tb2    amd64       lightweight, efficient FTP server written for security
ii  wget          1.21.3-1tb2     amd64       retrieves files from the web
ii  zlib1g:amd64  1:1.2.13.dfsg-1 amd64       compression library - runtime
New password: Retype new password: passwd: password updated successfully
mysql: unrecognized service

      I suspect a mariadb / mysql naming issue. I really do not know where to start so going back to 1.5.10.1629 backup.

      Any ideas ?

      posted in Linux Problems
      L
      lperoma
    • Attempting to join domain: The parameter is incorrect, code = 87

      Mornign all.

      I am running out of ideas here, this was working back in version 1.5.10.10 I believe I had, while on 1622 & 1629 isn’t.

      I have populated the fields as best I know:

      AD DEFAULT DOMAINNAME : MYSUBDOMAIN, and also tried MYCOMPANYSUBDOMAIN.MYCOMPANYDOMAIN.COM

      AD DEFAULT OU: empty, and also tried OU=Computers,DC=MYCOMPANYSUBDOMAIN,DC=MYCOMPANYDOMAIN,DC=COM

      AD DEFAULT USER: user , also tried MYCOMPANYSUBDOMAIN\user

      AD DEFAULT PASSWORD: thesecretpassword

      AD DEFAULT PASSWORD LEGACY: empty , also tried thesecretpassword

      ENFORCE HOST CHANGES : checked.

      I am pretty sure this user can join the domain, because as this was not working, I created a PS script as a snapin, that just works and joins domain.

      What am I doing wrong ?

      --------------------------------------------------------
----------------------HostnameChanger--------------------
--------------------------------------------------------
27/10/2024 10:53:27 Client-Info Client Version: 0.13.0
27/10/2024 10:53:27 Client-Info Client OS: Windows
27/10/2024 10:53:27 Client-Info Server Version: 1.5.10.1629
27/10/2024 10:53:27 Middleware::Response Success
27/10/2024 10:53:27 HostnameChanger Checking Hostname
27/10/2024 10:53:27 HostnameChanger Hostname is correct
27/10/2024 10:53:27 HostnameChanger Attempting to join domain
27/10/2024 10:53:29 HostnameChanger The parameter is incorrect, code = 87
--------------------------------------------------------
      posted in FOG Problems
      L
      lperoma
    • RE: Could not mount /dev/sda3: Metadata kept in Windows cache, refused to mount.

      @george1421 This is correct. It works fine. Thanks,

      posted in FOG Problems
      L
      lperoma
    • RE: Could not mount /dev/sda3: Metadata kept in Windows cache, refused to mount.

      OK, looks like Disable Fast Startup in Windows solved the issue. Sorry for the noise.

      posted in FOG Problems
      L
      lperoma
    • Could not mount /dev/sda3: Metadata kept in Windows cache, refused to mount.

      morning all.

      This is a brand new “bare” windows 10 ltsc installation, EFI. Nothing strange about it. File system is clean and de fragmented. All tests pass.

      Trying to capture an initial image, but unable due error. Any hint ?

      FOG 1.5.1629 dev-branch, FOS kernel 6.1.89 (my VM does not boot with latest kernel as per known issue)

      Any hint ? Thanks a lot.

      Init Version: 20240905
* Could not mount /dev/sda3 (/bin/fog.upload->beginUpload)
   Args Passed:
      Reason: The disk contains an unclean file system (0, 0).
      Metadata kept in Windows cache, refused to mount.
      posted in FOG Problems
      L
      lperoma
    • RE: PXE Boot Error - "Kernel Panic" Issue "XZ decompressor ran out of memory"

      @Tom-Elliott Updating now to latest dev-branch and will report next week.

      posted in FOG Problems
      L
      lperoma
    • RE: Chainloading failed, hit 's' for the iPXE shell

      @george1421 Thanks so much.

      A couple of notes for clarity.

      Network: 192.168.0.0/255.255.252.0 -> /22 (not /23), thus the client is in the same subnet.

      Fog server: 192.168.0.21
      dnsmasq server: 192.168.0.40

      dnsmasq server (LXC CT) has a copy of /tftpboot from fog server. I wanted to run dnsmasq without interfering FOG. I hope this answers Qs 1-2-3.

      re. Q4, I have no idea, further more, sometimes the same clients boots fine, some other times, it doesnt.

      posted in FOG Problems
      L
      lperoma
    • RE: Chainloading failed, hit 's' for the iPXE shell

      @george1421 output2.pcap output.pcap

      there you go.

      output.pcap is a successful boot.
      output2.pcap is a bad boot that required ‘hit s’ and then ‘autoboot’

      Thanks for checking this

      posted in FOG Problems
      L
      lperoma
    • RE: Chainloading failed, hit 's' for the iPXE shell

      @george1421 Ubiquiti UDM pro.

      I removed the TFTP / netowrk boot options from it as it can only send one pxe file, and these days there’s a good mix of BIOS & EFI, so I had to install dnsmasq in a dhcpproxy config, which seems to be working away nicely.

      This is a successful boot of a BIOS machine and this is the conversation with the dhcpproxy:

      2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 vendor class: PXEClient:Arch:00000:UNDI:002001
2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 user class: iPXE
2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 PXE(eth0) 52:54:00:92:d1:4a proxy
2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 tags: BIOS, eth0
2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 bootfile name: undionly.kpxe
2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 next server: 192.168.0.21
2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 broadcast response
2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 sent size:  1 option: 53 message-type  2
2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 sent size:  4 option: 54 server-identifier  192.168.0.40
2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 sent size: 17 option: 97 client-machine-id  00:d0:37:b8:0d:ce:18:53:49:a0:87:9c:05:d0...
2024-10-16T10:20:06+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 sent size: 50 option: 43 vendor-encap  06:01:03:08:07:80:00:01:c0:a8:00:28:09:0e...
2024-10-16T10:20:07+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:20:07+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 vendor class: PXEClient:Arch:00000:UNDI:002001
2024-10-16T10:20:07+0000 proxydhcp dnsmasq-dhcp[1288]: 3246548343 user class: iPXE
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 vendor class: PXEClient
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 user class: iPXE
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 PXE(eth0) 192.168.3.79 52:54:00:92:d1:4a undionly.kpxe
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 tags: eth0
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 bootfile name: undionly.kpxe
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 next server: 192.168.0.40
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 broadcast response
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 sent size:  1 option: 53 message-type  5
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 sent size:  4 option: 54 server-identifier  192.168.0.40
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 sent size: 17 option: 97 client-machine-id  00:d0:37:b8:0d:ce:18:53:49:a0:87:9c:05:d0...
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 0 sent size: 28 option: 43 vendor-encap  47:04:80:00:00:00:0a:13:01:42:6f:6f:74:69...
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-tftp[1288]: sent /tftpboot/undionly.kpxe to 192.168.3.79
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 vendor class: PXEClient
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 user class: iPXE
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 PXE(eth0) 52:54:00:92:d1:4a proxy
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 tags: eth0
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 bootfile name: undionly.kpxe
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 next server: 192.168.0.21
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 broadcast response
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 sent size:  1 option: 53 message-type  2
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 sent size:  4 option: 54 server-identifier  192.168.0.40
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 sent size: 17 option: 97 client-machine-id  00:d0:37:b8:0d:ce:18:53:49:a0:87:9c:05:d0...
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 sent size: 50 option: 43 vendor-encap  06:01:03:08:07:80:00:01:c0:a8:00:28:09:0e...
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 vendor class: PXEClient
2024-10-16T10:20:24+0000 proxydhcp dnsmasq-dhcp[1288]: 1516823406 user class: iPXE

      This is a conversation of the failing PXE boot on another BIOS machine:

      2024-10-16T10:48:48+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:48:48+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 vendor class: PXEClient:Arch:00000:UNDI:002001
2024-10-16T10:48:48+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 PXE(eth0) 2c:44:fd:14:dd:f6 proxy
2024-10-16T10:48:48+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 tags: BIOS, eth0
2024-10-16T10:48:48+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 bootfile name: undionly.kpxe
2024-10-16T10:48:48+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 next server: 192.168.0.21
2024-10-16T10:48:48+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 broadcast response
2024-10-16T10:48:48+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 sent size:  1 option: 53 message-type  2
2024-10-16T10:48:48+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 sent size:  4 option: 54 server-identifier  192.168.0.40
2024-10-16T10:48:48+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
2024-10-16T10:48:48+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 sent size: 17 option: 97 client-machine-id  00:74:5b:5b:52:eb:1a:0b:93:db:13:37:77:0b...
2024-10-16T10:48:48+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 sent size: 50 option: 43 vendor-encap  06:01:03:08:07:80:00:01:c0:a8:00:28:09:0e...
2024-10-16T10:48:56+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:48:56+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 vendor class: PXEClient:Arch:00000:UNDI:002001
2024-10-16T10:48:59+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:48:59+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 vendor class: PXEClient:Arch:00000:UNDI:002001
2024-10-16T10:48:59+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 PXE(eth0) 192.168.2.47 2c:44:fd:14:dd:f6 undionly.kpxe
2024-10-16T10:48:59+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 tags: BIOS, eth0
2024-10-16T10:48:59+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 bootfile name: undionly.kpxe
2024-10-16T10:48:59+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 next server: 192.168.0.40
2024-10-16T10:48:59+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 sent size:  1 option: 53 message-type  5
2024-10-16T10:48:59+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 sent size:  4 option: 54 server-identifier  192.168.0.40
2024-10-16T10:48:59+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
2024-10-16T10:48:59+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 sent size: 17 option: 97 client-machine-id  00:74:5b:5b:52:eb:1a:0b:93:db:13:37:77:0b...
2024-10-16T10:48:59+0000 proxydhcp dnsmasq-dhcp[1288]: 4279557622 sent size: 28 option: 43 vendor-encap  47:04:80:00:00:00:0a:13:01:42:6f:6f:74:69...
2024-10-16T10:49:00+0000 proxydhcp dnsmasq-tftp[1288]: error 0 TFTP Aborted received from 192.168.2.47
2024-10-16T10:49:00+0000 proxydhcp dnsmasq-tftp[1288]: sent /tftpboot/undionly.kpxe to 192.168.2.47
2024-10-16T10:49:00+0000 proxydhcp dnsmasq-tftp[1288]: sent /tftpboot/undionly.kpxe to 192.168.2.47
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 vendor class: PXEClient:Arch:00000:UNDI:002001
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 user class: iPXE
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 PXE(eth0) 2c:44:fd:14:dd:f6 proxy
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 tags: BIOS, eth0
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 bootfile name: undionly.kpxe
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 next server: 192.168.0.21
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 broadcast response
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 sent size:  1 option: 53 message-type  2
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 sent size:  4 option: 54 server-identifier  192.168.0.40
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 sent size: 17 option: 97 client-machine-id  00:74:5b:5b:52:eb:1a:0b:93:db:13:37:77:0b...
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 sent size: 50 option: 43 vendor-encap  06:01:03:08:07:80:00:01:c0:a8:00:28:09:0e...
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 vendor class: PXEClient:Arch:00000:UNDI:002001
2024-10-16T10:49:07+0000 proxydhcp dnsmasq-dhcp[1288]: 4202889309 user class: iPXE

      Connection timed out (https://ipxe.org/4c126835)
      Chainloading failed,

      hit ‘s’ for the iPXE shell; reboot in 18 seconds_

      enter ‘autoboot’ and then …

      
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 vendor class: PXEClient:Arch:00000:UNDI:002001
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 user class: iPXE
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 PXE(eth0) 2c:44:fd:14:dd:f6 proxy
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 tags: BIOS, eth0
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 bootfile name: undionly.kpxe
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 next server: 192.168.0.21
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 broadcast response
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 sent size:  1 option: 53 message-type  2
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 sent size:  4 option: 54 server-identifier  192.168.0.40
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 sent size: 17 option: 97 client-machine-id  00:74:5b:5b:52:eb:1a:0b:93:db:13:37:77:0b...
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 sent size: 50 option: 43 vendor-encap  06:01:03:08:07:80:00:01:c0:a8:00:28:09:0e...
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 vendor class: PXEClient:Arch:00000:UNDI:002001
2024-10-16T10:50:03+0000 proxydhcp dnsmasq-dhcp[1288]: 1083364685 user class: iPXE
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 vendor class: PXEClient
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 user class: iPXE
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 PXE(eth0) 192.168.2.47 2c:44:fd:14:dd:f6 undionly.kpxe
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 tags: eth0
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 bootfile name: undionly.kpxe
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 next server: 192.168.0.40
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 broadcast response
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 sent size:  1 option: 53 message-type  5
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 sent size:  4 option: 54 server-identifier  192.168.0.40
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 sent size: 17 option: 97 client-machine-id  00:74:5b:5b:52:eb:1a:0b:93:db:13:37:77:0b...
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-dhcp[1288]: 0 sent size: 28 option: 43 vendor-encap  47:04:80:00:00:00:0a:13:01:42:6f:6f:74:69...
2024-10-16T10:50:04+0000 proxydhcp dnsmasq-tftp[1288]: sent /tftpboot/undionly.kpxe to 192.168.2.47
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 vendor class: PXEClient
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 user class: iPXE
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 PXE(eth0) 2c:44:fd:14:dd:f6 proxy
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 tags: eth0
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 bootfile name: undionly.kpxe
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 next server: 192.168.0.21
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 broadcast response
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 sent size:  1 option: 53 message-type  2
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 sent size:  4 option: 54 server-identifier  192.168.0.40
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 sent size:  9 option: 60 vendor-class  50:58:45:43:6c:69:65:6e:74
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 sent size: 17 option: 97 client-machine-id  00:74:5b:5b:52:eb:1a:0b:93:db:13:37:77:0b...
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 sent size: 50 option: 43 vendor-encap  06:01:03:08:07:80:00:01:c0:a8:00:28:09:0e...
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 available DHCP subnet: 192.168.0.0/255.255.252.0
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 vendor class: PXEClient
2024-10-16T10:50:05+0000 proxydhcp dnsmasq-dhcp[1288]: 2900218228 user class: iPXE

      I wonder if the line :

      2024-10-16T10:49:00+0000 proxydhcp dnsmasq-tftp[1288]: error 0 TFTP Aborted received from 192.168.2.47

      is the culprit of the problem, or else something else.

      posted in FOG Problems
      L
      lperoma
    • RE: Chainloading failed, hit 's' for the iPXE shell

      @george1421 I will give it a try.

      However what does not make sense is 192.168.3.253 is my gateway (and DHCP server). No TFTP there, I wonder if this is a default “try to TFTP the gateway when everything else fails”.

      Infrastructure has RSTP, but I wonder how could this affect an endpoint, there only one connection to it.

      I have dnsmasq on 192.168.0.40, and Fog on 192.168.0.21.

      Do you want me to chain into dnsmaq or fog ?

      Thanks,

      posted in FOG Problems
      L
      lperoma
    • Chainloading failed, hit 's' for the iPXE shell

      Afternoon guys, another small glitch. undionly.kpxe, fog 1.5.10.1662.

      This is a

      System Manufacturer Hewlett-Packard
      System Product HP Pro3500 Series
      System Version
      System Type Type: Desktop
      BIOS Vendor AMI
      BIOS Version 8.16
      BIOS Date 07/17/2013
      Motherboard Manufacturer Foxconn
      Motherboard Product Name 2ABF
      Motherboard Version 3.20
      Motherboard Serial Number
      Motherboard Asset Tag
      CPU Manufacturer Intel® Corporation
      CPU Version Intel® Pentium® CPU G2030 @ 3.00GHz
      CPU Normal Speed Current Speed: 3000 MHz
      CPU Max Speed Max Speed: 3800 MHz
      Memory 3.73 GiB
      Hard Disk Model SanDisk SSD PLUS 240GB
      Hard Disk Firmware UF4004RL
      Chassis Manufacturer Hewlett-Packard
      Chassis Version
      Chassis Serial
      Chassis Asset CZC3457Z0Z
      GPU-0 Vendor Intel Corporation
      GPU-0 Product Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

      I have several of these - about 15 - and all seem ok. This one and 2 others give me the following error upon pxe boot:

      GATEWAY IP:
192.168.3.253

Auto-select:
Boot to FOG

BOOT SERVER IP: 192.168.0.48

PXE->EB: !PXE at 9944:0078, entry point at 9944:0100

UNDI code segment 9944:32CC, data segment 8CFA:C4AG@ (563-626kB)
UNDI device is PCI 63:00.6, type DIX+802.3
563KB free base memory after PXE unload

iPXE initialising devices...

iPXE 1.21.1+ (g5deSd) -- Open Source Network Boot Firmware -- https://ipxe.org
Features: DNS FTP HTTP HTTPS iSCSI NFS TFTP VLAN AoE ELF MBOOT PXE bzImage Menu
PXEXT

Configuring (net0 20:44:fd:14:dd:f6)...... ok
Received DHCP answer on interface net0
tftp://192.168.3.253/default.ipxe....

Connection timed out (https://ipxe.org/4c126835)
Chainloading failed,

hit 's' for the iPXE shell; reboot in 18 seconds_

      Hitting ‘s’ and then entering “autoboot” continues with the boot process, into fog, and no more issues. Why would this happen ?

      posted in FOG Problems
      L
      lperoma
    • RE: PXE Boot Error - "Kernel Panic" Issue "XZ decompressor ran out of memory"

      @george1421 As FYI, this machine is also missindentified in FOG as 32 bits. The same workaround is workking fine now:

      System Manufacturer Hewlett-Packard
      System Product HP EliteBook 8470p
      System Version A1029D1102
      System Serial Number CNU336BLTL
      System UUID 1e371eb7-7334-11e3-bfb9-d9e6c803c050
      System Type Type: Notebook
      BIOS Vendor Hewlett-Packard
      BIOS Version 68ICF Ver. F.43
      BIOS Date 07/16/2013
      Motherboard Manufacturer Hewlett-Packard
      Motherboard Product Name 179B
      Motherboard Version KBC Version 42.36
      Motherboard Serial Number PCWHK001X5FPRO
      Motherboard Asset Tag Not Specified
      CPU Manufacturer Intel® Corporation
      CPU Version Intel® Core™ i5-3380M CPU @ 2.90GHz
      CPU Normal Speed Current Speed: 2900 MHz
      CPU Max Speed Max Speed: 4000 MHz
      Memory 7.63 GiB
      Hard Disk Model MTFDDAK256MAM-1K12
      Hard Disk Firmware 08TH
      Hard Disk Serial Number 13330385921A
      Chassis Manufacturer Hewlett-Packard
      Chassis Version
      Chassis Serial CNU336BLTL
      Chassis Asset CNU336BLTL
      GPU-0 Vendor Intel Corporation
      GPU-0 Product 3rd Gen Core processor Graphics Controller

      posted in FOG Problems
      L
      lperoma
    • RE: PXE Boot Error - "Kernel Panic" Issue "XZ decompressor ran out of memory"

      @george1421 I was tenting other pxe images. It is using undionly.kpxe to BIOS machines and snp.efi for UEFI, unless you recommend anything else, I really have no idea which one to use, just using what seems most popular.

      posted in FOG Problems
      L
      lperoma
    • 1 / 1