Posts made by george1421

@dureal99d said in Secondary Drive:

for example at the end once I clean up the mnt test folder should I run "mount -t ext4 /dev/sdb1/whateverfolderIcreate /images

this would insure that the fog images folder is mounted in side this whateverfoldericreate folder yes?

Linux file system doesn’t work that way, the mount command mounts a partition to a mount point.

In your case you can either mount a new disk to the /images folder as in Sebastians post, or if your linux server uses LVM, you can just add that new disk to the root LVM group and then just extend your root lvm group. Let the LVM disk manager manage how that disk is used. There are many how-tos on how to work with LVM: https://www.rootusers.com/how-to-increase-the-size-of-a-linux-lvm-by-adding-a-new-disk/

@Sebastian-Roth You are right that firmware is for the fiber (10G) adapter. While it did fix the error in the log its not adding any real value for the OP or for FOG in general. But too, I’m still not seeing FOG as a good tool for cloning servers because of the other mix of hardware (you won’t find in desktops). I would say remove the firmware and have the OP test again now that its working in his environment (because the other roadblocks have been removed).

@FLHS If you want to direct connect two computers directly together than yes you must use a cross over cable. Understand in this configuration your FOG server must provide dhcp services, in addition to the other normal FOG pxe services. While this is a non-standard setup it will work as you ask. For the FOG server, it must use a static IP address on this interface. The target computer will use dhcp assigned IP address (required because the pxe boot data is sent via dhcp)

I do have to say my intuition is telling me you are doing something non-standard with fog (such as using it as a disaster recovery backup service). If that is the case there may be a better solution than fog. I do have to say that FOG is a complex combination of services. If you are using FOG as a DR backup tool, then clonezilla may be a better tool since it can boot from usb flash and save to a usb attached hard drive.

@grey Before you loose access to this server pxe boot it again and run the compatibility test from the FOG iPXE menu. I’m interested to see if both networking and storage passes (you will be too).

@Tom-Elliott That one I can test by setting the interface to a vlan without a dhcp server. I will prove that one out for sure. The other one I’m not sure if I can have a “unplugged” interface but have it appear in linux with ESXi.

@Tom-Elliott said in bnx2x fails to load firmware on Dell R430:

@george1421 It tries everything until it finds a link up I believe.

Great, I have never tried. But I just thought I can test this by creating a vm with 6 network adapters with eth5 being the only one connected. But I’m not sure if I can have it defined but not having the link up. I may have to play in my test lab later tonight.

Also pondering this a bit more since your first (usable) interface is eth5 I can see another issue.

@Developers Does the FOS engine stop enumerating the network adapter at eth1 or will it keep going until it finds a network adapter with a link up state to use? OR Is there a kernel parameter we can pass that says to use ethX as the FOS network interface?

Just to be clear FOG does not magically talk to target computers. There is a complex dance of technologies that work together to make a FOG capture/deployment a success.

Once your fog server is setup you need to modify your dhcp server to provide the FOG information to your target computers. This is typically done by setting dhcp options 66 {next-server} to the IP address of the fog server (which should be a static IP address) and dhcp option 67 {boot-file} to undionly.kpxe for bios (legacy) target computers and ipxe.efi for uefi based target computers.Once dhcp is setup then you pxe (network) boot the target computer. If everything goes well you should see the FOG iPXE boot menu. At the iPXE boot menu you select register device and register the target computer with FOG. After that you can go into the fog web gui and find the device you just registered and schedule a capture task for your mother or golden image. Then pxe (network) boot your golden image computer once more and then FOG should automatically start to capture the hard drive setting.

I skipped over a few steps but that is the general outline of what needs to be done.

OK this is good promising news. eth5 is getting a link up but no IP address in FOS but you can pxe boot and iPXE is getting an IP address because the FOS kernel (bzImage) and VHD (init.xz) are being sent to the target computer. When we see this we typically see that spanning tree is turned on at the network switch. Spanning tree takes about 27 seconds for the port to start forwarding data. The FOS engine is so fast that it has already given up by the time spanning tree starts to forward data.

On these ports you need to enable one of the fast spanning tree prototocols (port fast, fast stp, rstp, or what ever your switch mfg calls it). A quick check to see if its a spanning tree issue is to put an unmanaged switch between the building switch and the target computer. This unmanaged switch keeps the port on the building switch from winking as the iPXE kernel hands off the network interface to the FOS engine.

@Matthieu-Jacquart Wonderful that it works by name. That will save a lot of admin pain not having to manage wireless mac addresses too.

I may not have explained it well before. The wireless mac addresses won’t be recorded by the FOG linux OS [FOS] that runs on the target computer because that version of linux doesn’t have the drivers required to see almost all wireless adapters. Without these drivers the wireless adapter is invisible.

@rnavarro Thank you for the feedback. This java error is a bit confusing then. FOG does not use java at all (as Tom posted below), so its not clear why mysql is wanting to use it.

Is this a fresh install of cento 6.5? And did you pick the minimal (basic) install of centos 6.5? Normally java isn’t installed unless you pick something other than minimal (like centos workstation)

Can you also say when you tried to upgrade FOG were you logged in as the linux root user?

@Matthieu-Jacquart Now that I have the luxury of time to think about it, the FOS Engine (linux OS) doesn’t support/have the wireless drivers installed. So of course you will not see the mac address So your inventory either at first or later will not register the mac address. But adding the mac address may not matter for snapin or printer deployment since the device should be referenced by name or host ID. I “think” the mac address is only used during pxe booting to help identify the device.

I would be interested to know your success/failure on this, because I could be wrong too…

@rnavarro OK you are on Centos 6.5. Great. Before you try to upgrade fog, can you run yum update and make sure Centos is up to date.

One question, is this server that FOG is running on, supporting any other application or is it only FOG that runs on it?

One thing I just noticed, in your ssh terminal session you are logged in as the “fog” user but you are doing an upgrade. Unless I’m wrong, you should do any FOG installs as root. The “fog” user is only used by the FOG program internally and should never be logged into directly.

@x23piracy Great info, thank you.

The approach I’m looking at is to have user authentication and then if user is in AD group ( X ) then they are an admin, if they are in group ( Y ) then user, if they are not in either AD group then no access. Initially I was only thinking about a single group, but if there is admin and user levels in FOG then the dual group is the answer.

Your explanation also tells me why there was an admin field in the database. I hope to have time over the weekend to do a little coding to see if I can do a proof of concept test.

@grey Correct it will stay in debug capture until the capture completes or you cancel the task. its kind of handy for debugging your hardware.

As for the no link issue I would go back to the error logs on the FOS client. Also the lspci command (one of the switches) should show what kernel driver is managing which device.

@Tom-Elliott Understood, thx.

@Tom-Elliott said in bnx2x fails to load firmware on Dell R430:

You mind rerunning the installer? I’ve added the missing firmware to the kernel build.

So does that bring the current kernel to 4.7.4? Just for my knowledge.

@grey OK then, we are looking for device 02:00.0. If I understand the logs correctly you posted the error for device 04:00.0

Just to make sure eth0 and eth1 are the 1GbE nics?

I’ve also been searching on that error, I did find two posts that were similar errors
https://github.com/coreos/bugs/issues/450
https://lkml.org/lkml/2016/5/9/797

I’m still trying to understand if the error -2 means the firmware doesn’t exist or its some other indication.

@grey When you do a debug capture the FOS engine will boot just like its going to do a capture, but instead of capturing it will print a bunch of instructions on the screen. You have to press enter a few times (on the target computer)

… ok you just posted the logs that is a good find in the logs.

Well for some reason I think FOG lies…

Its not just a timezone issue here its off by days not just hours. If it was hours then I would say we need to update the php.ini file to reflect the correct time. If you drop to the fog linux console, is the time in agreement with the fog web gui?