Posts made by sarge_212

I changed the debugging up to level 7 and there isn’t any more output on the surface after I try to register it. Any suggestions on a minimal ISO that I could drop on a USB stick and live boot it to run a few commands? Thanks all!

@george1421 You guys rock, and thanks for the encouragement. Don’t worry, I’m far from giving up! Sebastian, thanks for the tips on getting a higher level of debugging going, I will do that. Thanks FOG team!

Well shucks.

@george1421 no, no FOG broken here However, it is using the most current inits and kernels I believe as I am no longer getting the cdc-ether error @Sebastian-Roth . That’s a step in the right direction. And @george1421 I do believe they DO have a weird hard drive structure. I think Windows preloads 3 separate partitions on these surfaces:

A recovery partition, system partition, and the actual partition where the OS is.

That being said, I think I’m going to play with blowing away these partition schemes, USB image it, and then try and register the image with the FOG server. That might just do it. You guys have been so helpful!

@Sebastian-Roth Here is the output from the modded 1.2.0:

#  ls -al /var/www/html/fog/service/ipxe/{bzImage,bzImage32,init.xz,init_32.xz}
-rw-r--r--. 1 fog apache  6847456 Jan 21 15:20 /var/www/html/fog/service/ipxe/bzImage
-rw-r--r--. 1 fog apache  6759504 Jan 21 15:20 /var/www/html/fog/service/ipxe/bzImage32
-rw-r--r--. 1 fog apache 15448272 Jan 21 15:20 /var/www/html/fog/service/ipxe/init_32.xz
-rw-r--r--. 1 fog apache 16476332 Jan 21 15:20 /var/www/html/fog/service/ipxe/init.xzere

testing again to see if I still get the cdc first

@george1421 Yes. I downloaded and installed FOG trunk on a separate server. Copied the bzImage, bzImage32, init.xz, init_32.xz to the /var/www/html/service/ipxe folder. Kernels do work on regular computer, yes.

Tested with the new kernels from trunk FOG. This resulted in the same kernel panic on the surface. I’m open to any other suggestions.

Well that’s really nice. I’m testing now with new kernels and FOG 1.2.0, will update you all when that’s been done.

@Sebastian-Roth Can I use kernels from trunk with FOG 1.2.0? I didn’t think that was a good mix together, but at this point we’re open to that I think.

Thanks again @tom and @george1421 for your input(s). I will hold tight. Good news, I didn’t brick the Surface, just takes an incredibly long time to reboot!

Would it be kosher to pull the bzImage, bzImage32 init_32.xz and init.xz from the trunk install and put them in the 1.2.0 install and see if that works? I’ll try that next, but wasn’t sure how that would affect things. I’m still learning all of this, thanks!

@george1421 – I’ve seen these in directories in I believe /var/www/html/fog/service/ is that the correct path where all these are stored? Good information, thank you. /me tips hat! I suppose we’ll wait for Tom’s feedback, which is great because that machine is bricked so I will need some time to rebuild the win10 image and get it on that machine. Thanks again!

Update:

Copied over the contents of a fresh trunk install to /tftpboot/ on FOG 1.2.0 server
Updated Kernel from 3.19.3 to 4.1.2 as seemed good in FOG UI
Tried imaging, it pulled ipxe.efi down from dhcp and we got our customized FOG menu(different than before)
Went to register and the machine kernel panic’d:

i8042: No Controller found
cdc-ether 2-2.2:2.- eth0 kevent 12 may have been dropped
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
Kernel Offset: disabled
-----[ end Kernel panic – not syncing: VFS: unable to mount root fs on unknown-block(1,0)]----

I am not familiar with kernel panics, but I will be googling today for sure. If you gents can make sense of that or provide any insight, I’m sure it’d be helpful. Thank you.

You guys rock, seriously. So I can use updated files in /tftpboot and keep other things the same? That is cool. I will download the trunk version today, install it, and scp those files or something over to that server. A small note, how does one go about updating the kernel? Wouldn’t that be done in the FOG web UI > FOG Configuration > Kernel update? Question there is, how do I know which one to choose, and how to tell currently what kernel I am using? Also, any ideas on when 1.3.0 will be released? Pure curiosity there. Thank you fine gentlemen again!

Wayne,

I appreciate the feedback and I’m not trying to be a stickler. However, the “powers at be” would prefer only one FOG server in production. Will the latest kernel work with FOG 1.2.0 as well as this shiny Surface Pro 4? Also a side note, how do I tell what kernel I’m currently using? Thank you again, and FOG really does rock it.

Hello kind FOG gents!

We’re trying to image some Surface Pro 4’s here in our environment. We successfully had the Surface pull the snponly.efi file and it gets an option menu. However, when selecting “Perform full host reg” it gets to /init.xz…/%17 and then never finishes | or drops back to fog menu. We are using FOG 1.2.0 on CentOS 7. My guess is that there isn’t a kernel yet for this new device, however we’re up for trying most anything EXCEPT upgrading to trunk. I hope this will be possible as we would like to continue using the stable version of FOG.

Thanks Tom. I appreciate your help and this forum has always been awesome.

Hmm…can’t restart the switch as we’re in production and i can’t cut everybody’s access to the network. I can play with FOG as needed though.

Tom,

How would I check if I’m doing unicast? I’m just wanting to do one image at a time to one machine.

@Psycholiquid Yes I can test 2 different machines on 2 different jacks if that is what you mean.