![]() Cyber Recovery with MultiCloud Data Services.ECS EXF900 All-Flash Enterprise Object Storage.PowerVault RD1000 Removable Disk Storage.I’m only offering this kernel because I think this has the right drivers loaded into it.Įdit: found it, in this thread it was a R640 server Now that I look at the subject line, it looks like you have an intel network adapter and not a qlogic adapter, so this probably won’t work. If that doesn’t work then we will debug this server to get the answer. ![]() ![]() If it does you know you have the updated kernel. Have a quick eye, but you should see ipxe download bzImage5.15.44qed-2. Pick full registration, or hardware detection. In the field that says kernel and has bzImage as the value in the property field, change that to bzImage5.15.44qed-2 the same exact name and case you set the file to. We will change the global because these R650 computers haven’t been registered yet. This is the global setting that tells FOG what kernel you want to load. Hit the expand all button, then search the page for bzImage. Now go into the FOG WebUI ->FOG Configuration -> FOG Settings. Copy this file to the fog server in /var/www/html/fog/service/ipxe directory. A quick google search returns this linux kernel network adapter “QLogic QED 25/40/100Gb core driver”ĭownload this file as bzImage5.15.44qed-2 Watch your case, because it is important. At the time it meant something to be but now… I think this was the custom kernel I built for an other fog admin. I see this kernel in my inventory with qed in the title. I think I might have build a custom kernel for a server build back in june. With that said fog can be extended to support almost any intel based computer. Its not designed for server with custom and unique hardware requirements. But to preface this FOG is intended and designed to image desktop or workstation class systems. We can get an answer but will need your help. Lspci -nn | grep -i we are going to need to build a one off kernel for this. Lets see if FOS Linux can see the disks in this server. The next commands have nothing to do with the network but rather with the disk subsystem. These need to be included in the custom kernel. For certain network adapters updated firmware (microcode) may be required. That should return any lines where firm is mentioned. Grep -i firm /var/log/syslog (check to confirm syslog file exists in /var/log directory. The next command we need to search the syslog to see if there are any messages regarding missing firmware. I need the hex code to know what kernel model is missing. We should see the LOM adapters and then the OPC or pcie adapters. This should list all of the network adapters installed in that computer. I’m most interesting in the hex codes that appear between the squared brackets on the next command. Now I want you to run these debugging commands to help identify that hardware. After a few screens of text that you will need to clear with the enter key you will be dropped at the fos linux command prompt on the target computer. PXE boot the target computer, it should go right into imaging where you will not see the fog ipxe menu. Before you hit the schedule task button tick the debug check box then schedule the task. Now schedule a deploy image to that computer, we are not going to deploy anything during the debugging process. In fog manually register that host (in host management) with the collected mac interface. You need the mac address of that network port you are using. You are going to connect that server to the network for pxe booting via the sfp+ port. var/ #1 SMP Sat Apr 16 10:40:, RO-rootFS, swap_dev 0x8, Normal VGAĪs I understand it, they should be supported OK for debugging its pretty easy on your part (kind of). var/ #1 SMP Sat Apr 16 10:44:, RO-rootFS, swap_dev 0x8, Normal VGA file /var/www/html/fog/service/ipxe/bzImage* This tells me the kernel doesn’t have the right driver but I am using the latest kernel available. The servers are able to PXE boot to the 25Gb NIC and even get the FOG menu but upon attempting to capture a FOG image, the kernel quits at “No network interfaces found.” This is after I disabled the 1Gb NIC in the BIOS. I will not be cabling the 1Gb NIC and intend to only use the 25Gb NIC. I just got a new batch of Dell R650 servers with both an Embedded BCM5720 NIC and an add-on Intel Ethernet 25G 2P E810-XXV.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |