Problems inventorying a HP 450g1 with 0.33b
-
We’ve recently received a pile of new HP 450g1’s that need inventory and image. None of the 0.32 kernels would work, so we elected to jump ahead to 0.33b. We have run into this problem attempting a quick inventory and have no idea where to start looking;
[COLOR=windowtext][FONT=Calibri]-[FONT=Times New Roman] [/FONT][/FONT][/COLOR][COLOR=windowtext][FONT=Calibri]esas2r: driver will not be loaded because no ATTO esas2r devices were found[/FONT][/COLOR]
[COLOR=windowtext][FONT=Calibri]-[FONT=Times New Roman] [/FONT][/FONT][/COLOR][COLOR=windowtext][FONT=Calibri]request _module: runaway loop modprobe binfmt-464c[/FONT][/COLOR]
[COLOR=windowtext][FONT=Calibri]-[FONT=Times New Roman] [/FONT][/FONT][/COLOR][COLOR=windowtext][FONT=Calibri]Starting init: /sbin/init exists but couldn’t’ execute it (error -8)[/FONT][/COLOR]
[COLOR=windowtext][FONT=Calibri]-[FONT=Times New Roman] [/FONT][/FONT][/COLOR][COLOR=windowtext][FONT=Calibri]request _module: runaway loop modprobe binfmt-464c[/FONT][/COLOR]
[COLOR=windowtext][FONT=Calibri]-[FONT=Times New Roman] [/FONT][/FONT][/COLOR][COLOR=windowtext][FONT=Calibri]Starting init: /bin/sh exists but couldn’t’ execute it (error -8)[/FONT][/COLOR][COLOR=windowtext][FONT=Calibri]-[FONT=Times New Roman] [/FONT][/FONT][/COLOR][COLOR=windowtext][FONT=Calibri]Kernel_panic – not syncing; No working init found. Try passing init=option to kernel. See linux documentation/init.txt for guidance[/FONT][/COLOR]
[COLOR=windowtext][FONT=Calibri] [/FONT][/COLOR][COLOR=windowtext][FONT=Calibri] any help is appreciated, thank you. [/FONT][/COLOR]
-
It appears this particular issue was related to the kernel that you downloaded ([url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]) which would normally be correct for the situation, except the bzImage is now a 64 bit kernel, while the init.gz file you were using was 32 bit. It wasn’t compatible so it would fail. This result is expected.
What we ended up doing, we found a few more bugs in my code and fixed them. Kernel page, specifically, had a missing " and due to it would not display the kernel text box. Next, I found out that there was an issue in the init.xz file (64 bit) which I have now fixed as well.
After the updates to switch the 0.32 from pxelinux.0 to undionly.kpxe and pointing to the working init_32.xz and bzImage32 as well as the download location, he was able to inventory and before we let go, his system was uploading an image. I will know more tomorrow, but just be understanding there may be issues here and there to get things working properly for your specific setup. I’m willing to help where and when I can as well.
Thank you John for allowing me your time (I have no issue giving up mine.) And being so understanding towards how to get things working for you.
-
Tom, should the link to the bzImage file have the fixes you made? And where do I go to change pxelinux.0 to undionly.kpxe? Thanks for your help on this.
-
[quote=“jbrabhamMSD, post: 24822, member: 22901”]Tom, should the link to the bzImage file have the fixes you made? And where do I go to change pxelinux.0 to undionly.kpxe? Thanks for your help on this.[/quote]
You will want to update your DHCP server information, specifically Option 67. You will want to update your DHCP server to point to the undionly.kpxe file instead of the pxelinux.0 file you used with FOG 0.32.
If you use a dnsmasq proxy service, you need to edit the ltsp.conf information and update the pxelinux.0 listing in there to point to the new undionly.kpxe as well.
Also the link provided is the most up to date version of the kernel and includes all fixes up to this point.
