@martial said:

USB\VID_0BDA&PID_8153…

Ok, we definitely have that driver included in our kernel config (since a long time). So I was wondering if other people had issues with Linux on this device. But seems like people are happily installing Linux on it despite some video card issues - see here. But no one complaining about network issues.

So I went hunting for those USB messages and read about USB hubs or other faulty USB hardware here and there, e.g.:

It seems the hub in the monitor went bad and was screwing with all other USB ports on the system

Maybe just some faulty hardware? Have you tried different ones. Always getting the exact same error on every try?

Then again I ask you for the third time (and last!), have you tried adding the Kernel Parameter has_usb_nic=1 to the host settings?? If this device is still unregistered and the error happens on registration you might just add the host manually via the web UI, add the parameter and try a capture task to see if that helps.

@Tom-Elliott Thank you for pointing this out, I feel that this solution has an immense potential and I am only scratching the surface of it. Kudos to you and @Fernando-Gietz for working on such a thourough product!

@coop90 Any update on this?

Sorry about the long intervals between posts. Just finishing up internal product training…

SO… I did as @Sebastian-Roth suggested and was able to successfully take an image and push it down on a blank VM! I have not tried putting the image back on the source VM but thought I would report back that I am successful and appear to be all set.

The take away from this is having 2 storage nodes on the same machine is not a great idea. If you run out of space, add a HDD and mount it /Images to add space.

Thank you @Sebastian-Roth and @george1421 for your help and guidance!

@Sebastian-Roth
Thank you so much, I missed it when you originally said that, running it with --exitFail didn’t work, however running it with -X did work. After this I was able to update/install the schema and actually log into the server via the web interface.

Additionally I tested booting to the server via PXE and was able too!

@Sebastian-Roth Thank you so much. You found the solution. The new password had an underscore ( _ ) as a chracter. I changed it and all is well again. Now I’m planning the upgrade to the latest FOG. Thanks again for your help. Alex

@Les https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

Please start there. Mind you this thread is very old and while the message you’re seeing may be similar, hence my posting to the wiki article, chances are your circumstances, version, file, etc… are vastly different. It’d be recommended to open a new thread.

@lschnider FWIW: Some people “need” to have it enabled because of internal security policies. That is why the developers came up with a list of required ports.

@Sebastian-Roth okay, thanks. I’ll do some research and see which route seems best. I still have a lot to learn about linux and wasn’t sure if there was a “new” way of adding storage to a FOG server since the wiki didn’t mention LVM and I was am not familiar with that yet.

@Sebastian-Roth So I went ahead and switched to dev-branch and upgrade nodes along with fog server. Seems like it’s working fine and the storage group info is now displayed. Thank you again for your help in this.

I Fixed it thanks for your Help guys.
First yes i needed the UEFI.
Than we uesed a Network bond on centos wich didnt worked so we del it and now it works fine 🙂

Thanks for the prompt response Sebastian, you guys rock!

I was able to resolve this by installing FOG 1.5.5 again after I fixed the TFTPD-HPA issue. You woulda thought I’d tried that already, but you’d be wrong, ugh. Anyway, please mark this as solved and thanks again, Sebastian.

Nevermind. Found it (in my own post history no less…)

https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

@george1421 it worked
finally it was a wrong placed host kernel that caused the trouble …
Thanks for the good help, we keep enjoying your system and appreciate your service!great!

@Les said in FOG Imaging/Capturing progress bar.:

@Sebastian-Roth

I think you might be on to something regarding the sectors, beacause i am running Win 10 on a 500GB HDD.

One of my drives on the desktop seems to be failing during the capturing process, as I hear my one of my drives snap, resulting in a error.(Can post the error if you are keen)

@Les just to be clear…is the 6TB Win10 desktop you are trying to capture the same one from your last comment, with a 500GB HD and additional hard drives? I am asking this because I noticed in an earlier comment you posted a screenshot uploading a Single Disk image seen here:
alt text

If your desktop has multiple drives you want to capture, you need your image format to be like this:
0_1543803913394_3260b69f-2f3c-452c-8ce9-da381b71177e-image.png

Perhaps that is why you are getting the error? I would post it for good measure though, just so @Sebastian-Roth or one of the many helpul forum mods can verify what the problem is.

OK - so Partedmagic is now $11 for the latest version - which also comes ready to PXE - no scripts etc required to get ready
Add files to TFTP share - add menu item - done.

menu item =

kernel http://${fog-ip}/pmagic/bzImage64
initrd http://${fog-ip}/pmagic/initrd.img
initrd http://${fog-ip}/pmagic/files.cgz
initrd http://${fog-ip}/pmagic/fu.img
initrd http://${fog-ip}/pmagic/m64.img
imgargs bzImage64 boot=live ip=dhcp edd=on noapic load_ramdisk=1 prompt_ramdisk=0 rw vga=normal sleep=0 loglevel=0 keymap=us splash quiet - || read void
boot || read void

Worked first time 🙂

@syschuck I just stumbled upon this post again as I have been thinking about removing Mageia from the installer scripts altogether. But seems like you are still using it. As I have not heard back from you since my last answer I lost track of this and forgot to add php-curl.

I just added php-curl and removed liblzma-devel for Mageia installs. Will be in the next release.

@Kagashe Editing the script solved it, thanks Sebastian.