• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Sebastian Roth
    3. Best
    S
    • Profile
    • Following 0
    • Followers 28
    • Topics 48
    • Posts 12,331
    • Groups 3

    Posts

    Recent Best Controversial
    • RE: Full C:\ After Imaging Inconsistent

      @imagingmaster21 From what you posted it sounds like this is still an issue with the NVMe disks that we have fixed in 1.5.6.5 already. Very strange.

      When you deploy to the machines do you see any warning message or something like that when it tries to expand the partition? Could you schedule a debug deploy task and step through it while taking pictures of the screen when it does the resize. Maybe there is something in the output that might help us here.

      As well please run the following command when you are on the debug shell and post a picture of the output here: grep " part_number " /usr/share/fog/lib/procsfdisk.awk

      The partition layouts look pretty much alright I reckon.

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Full C:\ After Imaging Inconsistent

      @imagingmaster21 Yeah you got it right this time and it shows that you are indeed using the patched version that shouldn’t have the NVMe bug anymore. Just wanted to make sure so we don’t run down the wrong rabbit hole.

      I will look into the details you posted over the weekend and try to replicate the issue. Will let you know!

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Full C:\ After Imaging Inconsistent

      @imagingmaster21 Yes @Quazz is right, really sounds like a similar issue to the one linked. Pretty sure the issue is being found and we’ll fix it in the next days. Will let you know here!

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Unable to deploy images on 1.5.7

      @Mx7Nine @kafluke Thanks for reporting and sorry for that. Something I messed up obviously. Will be fixed within the next two hours!

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Full C:\ After Imaging Inconsistent

      @imagingmaster21 My fault!! Sorry. Will fix that in the next two hours and let you know.

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Unable to deploy images on 1.5.7

      @Jethrov @kafluke @Mx7Nine I just updated the inits. So updating to 1.5.7 should be save now. Sorry again for the hickup! Please test and let us know.

      About rolling back: It’s not officially supported to roll back to an earlier version because taking back some of the database changes we do from one version to the other can’t be reverted easily if entries were added based on the new table structure. Most often you can still just get the earlier installer and install that over the newer to get the earlier version. But as I said, it can cause real bad trouble and we don’t support rolling back.

      Best what you can do is take a snapshot/backup of the VM/server before upgrading and stepping back will be easy then because it also rolls back the database (entries and structure).

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Full C:\ After Imaging Inconsistent

      @imagingmaster21 Alright, should be fixed now. Just re-download the inits from the same links as before and give it a try. Please let us know how things go.

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Unable to deploy images on 1.5.7

      @kafluke Arrrrgh, just found out that the installer does not re-download the hash file to see if the binaries (kernels and inits) package changed on the webserver. Should change that!

      So to fix the issue, run rm fogproject/tmp/binaries1.5.7.* and then re-run the installer.

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Full C:\ After Imaging Inconsistent

      @imagingmaster21 Thanks for the heads up. I will mark this solved now here. If you see any new issues feel free to call out.

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: When i boot via pxe the client, nothing is happening after download files

      @keurky In the pictures we see that it downloads undionly.kpxe but the boot messages definitely stem from an UEFI based system. You need to set ipxe.efi as boot file for those machines. You wanna head this: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

      About the legacy system. Not sure why it hangs. You might try using ipxe.pxe instead of undionly.kpxe for that and see if it makes a difference.

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Corrupt file in image?

      @Quazz said in Corrupt file in image?:

      then it could also potentially be something far more silly such as a faulty ethernet cable.

      Or faulty RAM in the client machine.

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Allow FOG admins to login using AD credentials

      @rogalskij I guess what you are looking for is the FOG LDAP plugin: https://forums.fogproject.org/topic/12074/fog-ldap-plugin/15

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Newbie getting started

      @bogle Check out this topic: https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Laptop with 2 nvme drives randomly selected so selecting one drive to capture not working

      @george1421 said in Laptop with 2 nvme drives randomly selected so selecting one drive to capture not working:

      cmic    : 0
        [2:2] : 0     PCI
        [1:1] : 0     Single Controller
        [0:0] : 0     Single Port
      

      Nice! Is this the part we are after? Would be interesting to see this on a system with two NVMe drives! @jmason

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Cannot Install Fog on new Ubuntu 16.04 Server

      @SBrady @george1421 I see several issues in the log that make me think there is something “wrong” with your internet connection. The installer tries to add software repositories to be able to install PHP 7.0 but this fails in various ways:

      gpg: keyring `/tmp/tmp010gbxbg/secring.gpg' created
      gpg: keyring `/tmp/tmp010gbxbg/pubring.gpg' created
      gpg: requesting key E5267A6C from hkp server keyserver.ubuntu.com
      gpgkeys: key 14AA40EC0831756756D7F66C4F4EA0AAE5267A6C can't be retrieved
      gpg: no valid OpenPGP data found.
      gpg: Total number processed: 0
      gpg: keyserver communications error: keyserver helper general error
      gpg: keyserver communications error: unknown pubkey algorithm
      gpg: keyserver receive failed: unknown pubkey algorithm
      Failed to add key.
      gpg: keyring `/tmp/tmpc1vb8t4j/secring.gpg' created
      gpg: keyring `/tmp/tmpc1vb8t4j/pubring.gpg' created
      gpg: requesting key E5267A6C from hkp server keyserver.ubuntu.com
      gpgkeys: key 14AA40EC0831756756D7F66C4F4EA0AAE5267A6C can't be retrieved
      gpg: no valid OpenPGP data found.
      gpg: Total number processed: 0
      gpg: keyserver communications error: keyserver helper general error
      gpg: keyserver communications error: unknown pubkey algorithm
      gpg: keyserver receive failed: unknown pubkey algorithm
      Failed to add key.
      Get:1 http://ppa.launchpad.net/ondrej/apache2/ubuntu xenial InRelease
      Err:1 http://ppa.launchpad.net/ondrej/apache2/ubuntu xenial InRelease
        Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
      Get:2 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease
      Err:2 http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease
        Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
      Hit:3 http://us.archive.ubuntu.com/ubuntu xenial InRelease
      Get:4 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
      Hit:5 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease
      Get:6 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
      Fetched 226 kB in 0s (276 kB/s)
      Reading package lists...
      E: Failed to fetch http://ppa.launchpad.net/ondrej/apache2/ubuntu/dists/xenial/InRelease  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
      E: Failed to fetch http://ppa.launchpad.net/ondrej/php/ubuntu/dists/xenial/InRelease  Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
      E: Some index files failed to download. They have been ignored, or old ones used instead.
      

      Especially the last three lines of the logs you see above…

      Try using the following commands manually before running the installer again to see what happens:

      sudo -i
      add-apt-repository -y ppa:ondrej/php
      add-apt-repository -y ppa:ondrej/apache2
      
      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Error updating kernel

      @texturtle https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: NTFS partitions corrupt after capturing resizable image

      @dolf Great to see you read my reply as it was meant - a technical elaboration and not personal offense! 🙂

      Why do you choose resizable if you intend to make a backup copy of this laptop? This backup is supposed to go back to the same machine with the same disk and there shouldn’t be a need to use resizable image type for that reason!

      Because it’s the default option, and when in doubt, default options are usually safe. In this case it’s not. I understand why this was a bad choice. Lesson learnt.

      This choice is years old, so not something we changed lately. It was even before I started to help working on this project, so I can just guess. I think it’s the most used image type because people want to be able to image to different machines and it is working in most cases. While you can use FOG for backing up machines it’s not the common aim of this software. Again, not saying it’s perfect but we try to make it as save as we possibly can.

      May I suggest that there shoud be some help text or a link to the wiki in the GUI that warns users about the pros and cons of different types of images?

      Would you help us write the texts and find a good way to place them in the web UI so people definitely see them but don’t get annoyed?

      Did you disable Windows 10 fast boot and properly shutdown before you started the capture?

      I always shut down from the command line before capturing. Is that sufficient? As far as I understand that disables fast boot for the next boot.

      Yes, good you knew about this. I was under the impression that this might have been caused by a unclean filesystem because of fast boot that got somehow corrupted.

      There is no way we can prevent users from all different kinds of situations. We try to make FOG with as much care as we can bit it’s like a swiss knife and if someone uses it the wrong way no one will blame the factory or engineers for having created a dangerous tool, right?!

      This is true!! But maybe the default option should be the safe(-r) one?

      What is the default option of a swiss knife? I suppose it’s opening the hinging blade. I think you are on the right track with saying, we should add help text for people to let them know about the pros and cons of the different choices.

      I am sorry I can’t give you really good advice on the actual problem. Without having the machine in front of me I fear I could give instructions that could make things even worse. But let’s give it a try anyway. I suppose you have some parts of the image capture on the FOG server. Take a look at /images/dev/.... There should be a folder named by the MAC address of this computer. Take a look at that. Do you have files d1.mbr, d1.partitions and d1.minimum.partitions in that. Please post the contents of the later two here - they’re just text.

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Multicast just hangs

      @rogalskij Issue probably is that newer versions of FOG ignore the multicast interface setting and choose the interface “automatically” . This is probably going wrong in your setup. Please check the log in /var/log/fog/multicast.log just to make sure.

      Read Tom Elliott’s post here: https://forums.fogproject.org/topic/13387/unable-to-change-multicast-nic

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Cannot image - Mount point cannot be found

      @zclift15 As well read through this: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

      posted in FOG Problems
      S
      Sebastian Roth
    • RE: Multicast just hangs

      @rogalskij Is your VLAN 1 bound to em1 on your FOG server?

      posted in FOG Problems
      S
      Sebastian Roth
    • 1 / 1