• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. mm Ekimia
    3. Topics
    • Profile
    • Following 0
    • Followers 0
    • Topics 6
    • Posts 32
    • Best 4
    • Controversial 0
    • Groups 0

    Topics created by mm Ekimia

    • mm EkimiaM

      Solved Capturing W10 on Sata , restoring on NVME = Fail to boot

      Windows Problems
      • • • mm Ekimia
      7
      0
      Votes
      7
      Posts
      692
      Views

      S

      @mm-Ekimia From what I read between the lines I can imagine this being a UEFI vs. legacy boot issue or something.

      If you still need help with this I ask you to post the information I asked for. Marking as solved for now.

    • mm EkimiaM

      Solved Failed to set disk GUID on Windows 10 image

      Windows Problems
      • • • mm Ekimia
      6
      0
      Votes
      6
      Posts
      354
      Views

      mm EkimiaM

      @Sebastian-Roth Thanks We’ll wait 1.5.6 as it’s non-blocking

    • mm EkimiaM

      Solved Upgrading 1.3.0 -> 1.5

      General
      • • • mm Ekimia
      4
      0
      Votes
      4
      Posts
      1.5k
      Views

      mm EkimiaM

      Upgrade worked perfectly ! Great. thanks

    • mm EkimiaM

      Flashing Fog images From classic distro

      General
      • • • mm Ekimia
      18
      0
      Votes
      18
      Posts
      4.6k
      Views

      Tom ElliottT

      @mm-Ekimia I’m confused what you’re trying to replicate.

      While I understand you may not want to wait 5 minutes, it seems a bit extraordinary to be working so hard to come up with a FOG like solution that doesn’t involve actually use FOG as it was intended. All this time to image 20 HDD’s would’ve taken about an hour worth of time including the 5 minute pxe boot time if you simply just grabbed a few extra laptops, registered and then tasked them.

      Of note with this, it sounds like these Skylake laptops are attempting to boot VIA UEFI? UEFI booting is supported with FOG but as far as the implementation as handled from the NIC itself is outside of “FOG’s” realm of control. If it’s taking UEFI NIC booting 5 minutes, why not just tell the BIOS to boot nic in legacy mode? (Of which I’m pretty sure will NOT take 5 minutes to boot).

      Now here’s where I’m confused about why you need to create, essentially, a FOG like solution on your side.

      You don’t want to wait the 5 minutes of booting into the NIC. This is the ONLY reason, as far as I can see, as to why you don’t want to just use FOG as it was intended. Now we’ve been a week at this with back and forth information. When you initially made the posting asking for assistance, if you had installed FOG, had 5 of these laptops, inserted an HDD into each one, booted the system through PXE and telling that system to image. Run this 4 times, you’d have all 20 HDD’s complete within about an hour (give or take a little).

      If you had 20 laptops all at once, you’d probably be done in about 30 minutes to an hour if you ran it through a multicast task.

      I don’t know what the end goal is. I think FOG is perfectly capable of imaging these disks regardless of how long PXE takes to load up. You’d have been done by now if you had just waited the extra 5 minutes or so per system.

    • mm EkimiaM

      USB Booting + USB ethernet

      General
      • • • mm Ekimia
      5
      0
      Votes
      5
      Posts
      4.2k
      Views

      S

      @mm-Ekimia May I point you to a topic in the iPXE forum where one of the main developers was saying that “USB support is starting to arrive in mainline iPXE” only about a good year ago. They have made progress I am sure! We have seen more and more people successfully booting their devices with USB NICs on iPXE.

      The biggest problem from my point of view is if you want to PXE boot from the USB NIC! Using an USB NIC with linux (as you do right now) is fairly easy because linux takes control and provides full access through own drivers. Completely different if you want to PXE boot from the USB NIC. Then your client machine - its BIOS/UEFI firmware - must be able and willing to talk to the USB NIC for PXE booting. Sounds like you don’t aim for that but just wanted to point that out!

      Back to your initial question… booting iPXE via USB key - which is easier than USB NIC PXE booting but still harder than booting linux to use the USB NIC. As George already said it’s a matter of finding a USB NIC adapter that is supported by iPXE. I started a list of supported USB NICs some time ago. Unfortunately I lost track of it all as it was very hard to follow without having my own devices for testing. Maybe this is a good point to start again. Searching the forums we should be able to find a lot of information as lots of people have tried USB NICs lately, known working e.g. ASIX AX88772C…

      But that’s still not the whole story I’m afraid! iPXE provides native drivers (should work both for UEFI and legacy BIOS) as well as UNDI (for BIOS) and SNP (for UEFI):

      undionly.pxe, kpxe, kkpxe, usb, iso - BIOS no native drivers ipxe.pxe, … - BIOS with native drivers and UNDI interface snponly.efi, usb, iso - UEFI no native drivers ipxe.efi, … - UEFI with native drivers and SNP interface smsc95xx/intel/realtek.XXX - “single” native driver

      So you might need to play with the different iPXE binaries to see which one is working for you. Please let us know which USB NIC exactly you have - make and model!!

      Edit: I just updated the mentioned wiki article. Hope this is useful for a lot of people. Please keep us up to date with USB NIC adapters you try.

    • mm EkimiaM

      Solved Deploying Resizable UEFI linux disk

      General
      • • • mm Ekimia
      14
      0
      Votes
      14
      Posts
      3.8k
      Views

      mm EkimiaM

      Hi ,

      just to say that I deployed the same Image to a new SATA disk and the 3rd partition (Swap) had a fixed size as Expected.

      So I guess that was a mistake on my side.

      Problem solved !

    • 1 / 1