Posts made by MRCUR

@Rusty I’m using our existing Win 7 unattend file without any issues on Win 10 Enterprise (1511). I made zero changes to the file and everything within the file is being completed.

@Tom-Elliott I’ll apply after school is done today and test. Thanks Tom.

@Tom-Elliott I did notice on the test server in /var/www, there is a symlink for fog to /var/www/html/fog. On the production server, this symlink doesn’t exist (everything is in /var/www/html/fog).

@Tom-Elliott First is the production server, second is test.

#!ipxe
set fog-ip 172.16.56.37
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
#!ipxe
kernel http://172.16.56.37/fog/service/ipxe/ loglevel=4 initrd=http://172.16.56.37/fog/service/ipxe/ root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.16.56.37/fog/ conosoleblank=0 mac=28:80:23:09:28:56 ftp=172.16.56.37 storage= storageip= web=172.16.56.37/fog/ osid= consoleblank=0 irqpoll hostname=TEA-440TEST mode=onlydebug
imgfetch http://172.16.56.37/fog/service/ipxe/
boot

#!ipxe
set fog-ip 172.16.200.10
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
#!ipxe
kernel loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.16.200.10/fog/ conosoleblank=0 mac=28:80:23:09:28:56 ftp=172.16.200.10 storage= storageip= web=172.16.200.10/fog/ osid= consoleblank=0 irqpoll hostname=TEA-440TEST mode=onlydebug
imgfetch init_32.xz
boot

@Tom-Elliott Output from where?

@Tom-Elliott Took the ipxe directory from the test server and copied it to the production server. Reapplied permissions and same results on the client. Kernel panic with any task.

@Tom-Elliott On the production server, the client throws the kernel panic with both tasks. On the test server, the client gets into the debug and then shows an “unknown task” error (maybe this is normal for debug?). With a deploy task it boots and begins imaging correctly.

@Tom-Elliott Same issue after running the installer again.

They’ve been the same throughout the day and were both 6285 when I updated last night when the problem started. The production is 6295 now as I’ve grabbed the latest a few times today.

@Tom-Elliott Same issue.

@Tom-Elliott

#!ipxe
set fog-ip X.X.X.37
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
iseq ${platform} efi && set key 0x1b || set key 0x127e
iseq ${platform} efi && set keyName ESC || set keyName F6
prompt --key ${key} --timeout 3000 Booting... (Press ${keyName} to access the menu) && goto menuAccess || sanboot --no-describe --drive 0x80
:menuAccess
login
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param username ${username}
param password ${password}
param menuaccess 1
param debug 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain -ar http://X.X.X.37/fog/service/ipxe/boot.php##params```

@Tom-Elliott Right. The test server was SVN from the start (not sure what rev I started with), the production server was originally 1.1 or 1.2 and upgraded to svn over the summer and then this week to 62XX series.

@Tom-Elliott I should mention that this hardware works fine with my test server (currently rev 6285 on 14.04 LTS, same as production server) using the default 4.4.1 kernel.

@Tom-Elliott It is, yes. Downloaded through the kernel update GUI as suggested by @Wayne-Workman. This also happens with the default 4.4.1 kernel.

@Wayne-Workman This is happening on all of our hardware that I know of. I’ve specifically been using HP ProBook 640’s and 440’s today while testing. I have a 440 sitting at my desk now which is displaying the issue.

@Tom-Elliott

@Tom-Elliott Changed the docroot to /var/www/ and didn’t have any success. Tried the 4.4 kernel as @wayne-workman suggested without success either. Same issue.

After talking to @Wayne-Workman, this seems like it might be an issue with the symlink being used to make /var/www/html work on Ubuntu where the root is really /var/www.

@tom-elliott I see in .fogsettings there’s a line for “docroot”. If I update that to be /var/www/ instead of /var/www/html/, will that work?

@Wayne-Workman I’m testing with an HP ProBook 640 G1, which works fine on a separate SVN install (also worked fine on the previous rev I was running).

Boot file is undionly.kpxe which it was before and is the same on the test server where this works fine.

Upgraded from SVN in the 3000’s (build from July sometime) to 6285. When trying to image a client (or register them, anything that requires access to the menu), I get an error of Kernel panic - not syncing.

Reran the installer again to get the inits downloaded (which says OK during install) and problem still occurs.

@Tom-Elliott It is enabled, yes. We don’t do hardware independent images (ugh), so we haven’t run into any issues where the client interrupts sysprep. After talking to @Jbob a bit, I have a better understanding of what’s happening and a workaround to correct it.

@Tom-S It seems to only happen immediately after imaging and sysprep is complete. I have noticed that the same model laptop with an SSD doesn’t exhibit this issue, which makes me think this is a service start timeout issue being hit that doesn’t occur on a sufficiently fast computer.