• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Image upload & deploy taking a long time

Scheduled Pinned Locked Moved Solved
FOG Problems
10
64
31.1k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G
    george1421 Moderator @Brad Schumann
    last edited by Sep 27, 2017, 6:46 PM

    @brad-schumann I would like to give you a hint and a request as long as you have the FOS engine running there.

    First the hint.
    At the FOS command prompt (as in the picture) do the following

    1. Key in ip addr show and note the IP address of the FOS target computer.
    2. Give root a temporary password by keying in passwd then give it a simple password like hello This password will be lost when FOS reboots, so don’t worry.
    3. Now from a windows computer connect to the FOS engine at the address gleaned at step 1 using putty (3rd party windows ssh application)
    4. Login with root and the password you defined in step 2.

    You can use putty to copy and paste stuff into the FOS engine from windows. It makes it easier to key stuff in and post to the forums because you can cut the text directly off the putty window and paste here.

    Now for my request (if Sebastian already asked for this you can ignore). Key in the following at the command prompt

    1. fdisk /dev/sda
    2. At the fdisk prompt key in p
    3. Copy the contents and paste it here.
    4. At the fdisk prompt key in q and you will be back at the FOS command prompt.

    What I’m interested in is the Id value in the 6th column.

    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

    B 1 Reply Last reply Sep 27, 2017, 7:31 PM Reply Quote 0
    • B
      Brad Schumann @george1421
      last edited by Sebastian Roth Sep 27, 2017, 2:02 PM Sep 27, 2017, 7:31 PM

      @george1421 I didn’t see a 6th column below (assuming you meant row) is what I got.

      Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disklabel type: gpt
      Disk identifier: 8897879E-4ECF-42A1-A6DC-F682422F50B6
      
      Device                Start            End         Sectors      Size   Type
      /dev/sda1              2048        1026047         1024000      500M   EFI System
      /dev/sda2           1026048        1288191          262144      128M   Microsoft reserved
      /dev/sda3           1288192      975800319       974512128    464.7G   Microsoft basic data
      /dev/sda4         975800320      976637447          837128    408.8M   Windows recovery environment
      

      0_1506540727574_460ef4b2-6fd2-4817-97a4-8b697199b5ee-image.png

      G 1 Reply Last reply Sep 27, 2017, 7:44 PM Reply Quote 0
      • G
        george1421 Moderator @Brad Schumann
        last edited by Sep 27, 2017, 7:44 PM

        @brad-schumann just for clarity this is what I expected to see.

        Disk /dev/sda: 999.7 GB, 999653638144 bytes, 1952448512 sectors
        Units = sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes
        Disk label type: dos
        Disk identifier: 0x0004a2f3
        
           Device Boot      Start         End      Blocks   Id  System
        /dev/sda1   *        2048     4098047     2048000   83  Linux
        /dev/sda2         4098048  1952448511   974175232   8e  Linux LVM
        

        It just may be the difference in the versions of fdisk program. The Id column tells what the partition ID is marked as. It was not a wasted effort since we have been able to collect more info on your exact hardware.

        I am bit intrigued that the Type in your screen shot says “Microsoft basic disk”

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        G 1 Reply Last reply Sep 27, 2017, 7:54 PM Reply Quote 0
        • G
          george1421 Moderator @george1421
          last edited by Sep 27, 2017, 7:54 PM

          @george1421 Interesting when I boot FOS from my USB drive and run the fdisk program I get the ID column as I expected

          In my case I have 3 partitions from this Win10 image running in bios/legacy mode.
          The boot partition is type 7
          So is the 😄 drive type 7
          The recovery partition is type 27.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

          B 1 Reply Last reply Sep 27, 2017, 8:12 PM Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Sebastian Roth Sep 27, 2017, 2:09 PM Sep 27, 2017, 8:07 PM

            @george1421 Probably a difference because @Brad-Schumann has a GPT layout and the one you posted is a legacy DOS layout. Still we see the partition type but in text instead of ID. The output posted looks ok to me. See here as well: https://en.wikipedia.org/wiki/Microsoft_basic_data_partition

            Be careful to not mix up partition type ID and filesystem type. You can label a partition in fdisk to be Linux for example and still format it as NTFS (fs type). Linux will still be happy with that.

            But I still have no idea why udev wouldn’t identify this to be an NTFS formated partition. @Brad-Schumann Are you able to mount the partition?

            mkdir -p /mnt/win
            mount.ntfs-3g /dev/sda3 /mnt/win
            ls -al /mnt/win
            umount /mnt/win
            

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            B 1 Reply Last reply Sep 27, 2017, 8:44 PM Reply Quote 0
            • B
              Brad Schumann @george1421
              last edited by Sep 27, 2017, 8:12 PM

              @george1421 we are not using legacy mode in the bios we are using the UEFI boot mode.

              1 Reply Last reply Reply Quote 0
              • B
                Brad Schumann @Sebastian Roth
                last edited by Sep 27, 2017, 8:44 PM

                @sebastian-roth 0_1506545044865_61b3c725-284f-4bfe-ac08-5f98ab30c46f-image.png

                1 Reply Last reply Reply Quote 0
                • S
                  Sebastian Roth Moderator
                  last edited by Sep 28, 2017, 4:54 AM

                  @Brad-Schumann From what it looks like there is no proper NTFS filesystem on sda3. How is it even possible that Windows boots from that? Can you please boot Windows up and post a picture of the disk management dialog. Maybe this can shed a light on this mystery!?!

                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                  B 1 Reply Last reply Sep 28, 2017, 12:56 PM Reply Quote 0
                  • B
                    Brad Schumann @Sebastian Roth
                    last edited by Sep 28, 2017, 12:56 PM

                    @sebastian-roth this all you were looking for? or did you need more detail on a particular drive?
                    0_1506603342694_Capture.PNG

                    G 1 Reply Last reply Sep 28, 2017, 2:59 PM Reply Quote 0
                    • G
                      george1421 Moderator @Brad Schumann
                      last edited by george1421 Sep 28, 2017, 9:00 AM Sep 28, 2017, 2:59 PM

                      @brad-schumann Dind, ding, ding we have our answer.

                      Bitlocker encrypted drive == raw data file to fog.

                      Bitlocker needs to be activated after the target system has been created not before its captured.

                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                      B 1 Reply Last reply Sep 28, 2017, 6:11 PM Reply Quote 0
                      • B
                        Brad Schumann @george1421
                        last edited by Sep 28, 2017, 6:11 PM

                        @george1421 But we don’t activate/use Bitlocker…
                        0_1506622282318_bitlocker.PNG

                        T 1 Reply Last reply Sep 28, 2017, 6:37 PM Reply Quote 0
                        • T
                          THEMCV @Brad Schumann
                          last edited by THEMCV Sep 28, 2017, 12:42 PM Sep 28, 2017, 6:37 PM

                          @brad-schumann Try this, I ran into this on Surface’s.

                          Open command prompt as admin.

                          manage-bde -off 😄

                          manage-bde -status 😄

                          Fingers crossed that it will fix it. In my case, Windows was by default encrypting the free space which caused issues.

                          X W 2 Replies Last reply Sep 28, 2017, 7:42 PM Reply Quote 4
                          • S
                            Sebastian Roth Moderator
                            last edited by Sep 28, 2017, 7:26 PM

                            OMG!!! Thank god we figured this out. I thought I was lost in this.

                            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                            1 Reply Last reply Reply Quote 2
                            • X
                              x23piracy @THEMCV
                              last edited by Wayne Workman Sep 28, 2017, 7:14 PM Sep 28, 2017, 7:42 PM

                              @themcv said in Image upload & deploy taking a long time:

                              @brad-schumann Try this, I ran into this on Surface’s.

                              Open command prompt as admin.

                              manage-bde -off 😄

                              manage-bde -status 😄

                              Fingers crossed that it will fix it. In my case, Windows was by default encrypting the free space which caused issues.

                              @Wayne-Workman #wiki worthy!

                              ║▌║█║▌│║▌║▌█

                              1 Reply Last reply Reply Quote 4
                              • T
                                THEMCV
                                last edited by Sep 28, 2017, 7:46 PM

                                @Sebastian-Roth Glad I could help. Yeah, I hate that Windows gives you the option to “Turn On Bitlocker”, but don’t tell you that the free space is encrypted. I am not sure if this is a something with the latest update/service pack for Windows 10, but I know that I’ve only seen it on Surface’s so far. I haven’t made an image for the latest Windows 10 so we’ll see. 🙂

                                @x23piracy You’re too kind. 😉

                                B 1 Reply Last reply Sep 28, 2017, 8:38 PM Reply Quote 3
                                • B
                                  Brad Schumann @THEMCV
                                  last edited by Sep 28, 2017, 8:38 PM

                                  @themcv @Sebastian-Roth That is looking to be the fix… The on server size now shows ~48GB and only took 15min to upload to the server. I am deploying the image to another laptop and the ETA is 12min. Thank you for your help. FYI, we build our images from scratch with Win10 download from Microsoft with a SA agreement so it must be a built in thing 😞 .

                                  1 Reply Last reply Reply Quote 1
                                  • W
                                    Wayne Workman
                                    last edited by Sep 29, 2017, 1:19 AM

                                    @THEMCV @Sebastian-Roth @george1421 I need to clairify because I’ve not been following this thread and don’t really understand fully the problem or solution.

                                    I understand the hardware is: Dell latitude 5580 laptop & Surface Pro

                                    FOG was taking an image as RAW for some reason? Why?
                                    @THEMCV What does the answer you posted do to fix it?
                                    Might other hardware models have this problem?
                                    What’s the best way to word the problem?

                                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                                    Daily Clean Installation Results:
                                    https://fogtesting.fogproject.us/
                                    FOG Reporting:
                                    https://fog-external-reporting-results.fogproject.us/

                                    T 2 Replies Last reply Sep 29, 2017, 1:29 AM Reply Quote 0
                                    • T
                                      THEMCV @Wayne Workman
                                      last edited by Sep 29, 2017, 1:29 AM

                                      @wayne-workman The problem is Microsoft is pushing for more BitLocker, so while it is technically off, it is encrypting the free space on the drive causing FOG to want to make it a raw image. I don’t know if this is just on pre installs or with the latest version of Windows, but I ran into this with the latest Surface Pro.

                                      X 1 Reply Last reply Sep 29, 2017, 6:58 AM Reply Quote 0
                                      • T
                                        THEMCV @Wayne Workman
                                        last edited by Sep 29, 2017, 1:32 AM

                                        @wayne-workman manage-bde -status shows if BitLocker is encrypting the free space and -off starts the decryption process

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          Sebastian Roth Moderator
                                          last edited by Sebastian Roth Sep 28, 2017, 11:07 PM Sep 29, 2017, 5:03 AM

                                          Though this is fixed I wanted to look into this a bit more to understand why this has happened and if we can do something about it to detect this. I am not sure if I can confirm the “free space encrypted” information. Reading this it sounds as if BitLocker was in a state of already encrypted (full disk) but not “activated” (whatever that means):

                                          Waiting for Activation - BitLocker is enabled with a clear protector key and requires further action to be fully protected.

                                          Though I am still not sure if and how we would be able to detect this. Oh wow, reading about this I just found out that you can actually mount bitlocker partitions from linux. Shall we add this to FOG?!? Well, we would need to ask people if they want to clone fast but have an unencrypted clone (mount bitlocked drive and do a file-aware cloning) or slow and have it encrypted on the destination. I don’t think we will be able to generate a fast and also encrypted target. So I reckon it’s not worth adding this feature at all.

                                          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                          G 1 Reply Last reply Sep 29, 2017, 10:03 AM Reply Quote 0
                                          • 1
                                          • 2
                                          • 3
                                          • 4
                                          • 3 / 4
                                          3 / 4
                                          • First post
                                            41/64
                                            Last post

                                          158

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project