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

    FOG restore only one partition

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    5
    83
    33.7k
    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.
    • S
      Sebastian Roth Moderator
      last edited by

      @plegrand As Tom said, could you please upgrade to the latest version. He is saying that you don’t need to re-upload. But I’d say it wouldn’t hurt anyway.

      You don’t need to update ipxe.krn on your TFTP server if booting the client works fine. The iPXE binary is not related to the error you see AFAIK!

      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

      P 1 Reply Last reply Reply Quote 1
      • P
        plegrand @Sebastian Roth
        last edited by

        @Sebastian-Roth Same problem

        1 Reply Last reply Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by

          @plegrand Please boot that client you tried to write the image to in debug deploy again (schedule a normal deploy task but tick “Schedule task as a debug task” in the advanced settings box just before you hit the button “CREATE DEPLOY TASK FOR …”).

          When you get to the shell please run sfdisk -d /dev/sda and post a picture of the output here (we need the exact numbers!!).

          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

          P 1 Reply Last reply Reply Quote 0
          • P
            plegrand @Sebastian Roth
            last edited by

            @Sebastian-Roth

            label: dos
label-id: 0x2bd2c32a
device: /dev/sda
unit: sectors

/dev/sda1 : start = 63,         size = 257024,    type = de
/dev/sda2 : start = 257087,     size = 102401024, type = 7, Bootable
/dev/sda3 : start = 102658111,  size = 209841152, type = 7
            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by

              @plegrand Did you copy&paste the numbers or typed them from the screen? I hope there is no typo in them! 😉

              If the figures are correct this is simple maths. The original first partition (as seen further down) starts at sector 40 and ends at 257480. Makes 257440 in total. After writing to the new disk the first partition starts at 63 (which should not be an issue) but ends at 257024. Makes a total of 256961 sectors for the first partition. Slightly smaller than the original one.

              I guess our re-sizing logic is still hating those recovery partitions (type=de)!

              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

              P 1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by

                I think I found where the issue is. Please give me some more time to see why things go wrong…

                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 0
                • S
                  Sebastian Roth Moderator
                  last edited by Sebastian Roth

                  @plegrand Can you please do a debug UPLOAD task on the original client you pull the image from. You don’t need to do the full upload. I just need to get some information. Run the following command when you get to the shell and post the full output here: blkid -po udev /dev/sda1

                  You can simply delete the task in the web interface and shutdown that client after you got the information.

                  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

                  P 1 Reply Last reply Reply Quote 0
                  • P
                    plegrand @Sebastian Roth
                    last edited by

                    @Sebastian-Roth

                    ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=2bd2c32a-01
ID_PART_ENTRY_TYPE=0xde
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=63
ID_PART_ENTRY_SIZE=257024
ID_PART_ENTRY_DISK=8:0
                    1 Reply Last reply Reply Quote 0
                    • P
                      plegrand @Sebastian Roth
                      last edited by

                      @Sebastian-Roth said:

                      @plegrand Did you copy&paste the numbers or typed them from the screen? I hope there is no typo in them! 😉

                      no typo !!

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by Sebastian Roth

                        @plegrand Thanks for posting all the details. They were really helpful in finding the issue and being able to replicate this on my test system. Tom and I have been working on a fix and it is up now. Please upgrade to the latest version and re-run the installer! No need to re-upload. Just try deploying to your machine and let us know if things are working.

                        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

                        P 1 Reply Last reply Reply Quote 0
                        • P
                          plegrand @Sebastian Roth
                          last edited by

                          @Sebastian-Roth Hello
                          I updated fog to the version 4919 / 6527 and i cant deploy image :

                          Failed to create deployment tasking for the following hosts
You must first upload an image to create a download task
                          1 Reply Last reply Reply Quote 0
                          • S
                            Sebastian Roth Moderator
                            last edited by

                            @plegrand That’s a different issue… We’ve seen this reported by another user yesterday. I think @Tom-Elliott is onto it already. Stay tuned.

                            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

                            P 1 Reply Last reply Reply Quote 0
                            • P
                              plegrand @Sebastian Roth
                              last edited by plegrand

                              @Sebastian-Roth Hello
                              then i made the test to deploy. Except the ftp problem (solved for the moment by editing “/var/www/fog/lib/fog/fogftp.class.php”.
                              There is again a problem :
                              Now the deployement works fine, i mean no error message from partclone but once deployement finished :
                              “Error loading operating system”

                              i made some test :

                              sfdisk -d /dev/sda
label: dos
label-id: 0x2bd2c32a
device: /dev/sda
unit: sectors

/dev/sda1 : start=          40, size=      257480, type=de
/dev/sda2 : start=      257520, size=   102401024, type=7, bootable
/dev/sda3 : start=   102658544, size=   209841152, type=7

                              For sfdisk as you can see , the informations are not the same than my older post

                              blkid -po udev /dev/sda1
ID_FS_SEC_TYPE=msdos
ID_FS_LABEL=DellUtility
ID_FS_LABEL_ENC=DellUtility
ID_FS_UUID=07D9-0C13
ID_FS_UUID_ENC=07D9-0C13
ID_FS_VERSION=FAT16
ID_FS_TYPE=vfat
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=2bd2c32a-01
ID_PART_ENTRY_TYPE=0xde
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=40
ID_PART_ENTRY_SIZE=257480
ID_PART_ENTRY_DISK=8:0

                              blkid -po udev /dev/sda2
ID_FS_LABEL=OS
ID_FS_LABEL_ENC=OS
ID_FS_UUID=0660C20C60C20303
ID_FS_UUID_ENC=0660C20C60C20303
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=2bd2c32a-02
ID_PART_ENTRY_TYPE=0x7
ID_PART_ENTRY_FLAGS=0x80
ID_PART_ENTRY_NUMBER=2
ID_PART_ENTRY_OFFSET=257520
ID_PART_ENTRY_SIZE=102401024
ID_PART_ENTRY_DISK=8:0

                              blkid -po udev /dev/sda3
ID_FS_LABEL=data
ID_FS_LABEL_ENC=data
ID_FS_UUID=86DC8201DC81EC2D
ID_FS_UUID_ENC=86DC8201DC81EC2D
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=2bd2c32a-03
ID_PART_ENTRY_TYPE=0x7
ID_PART_ENTRY_NUMBER=3
ID_PART_ENTRY_OFFSET=102658544
ID_PART_ENTRY_SIZE=209841152
ID_PART_ENTRY_DISK=8:0
                              1 Reply Last reply Reply Quote 0
                              • S
                                Sebastian Roth Moderator
                                last edited by

                                @plegrand Are source and destination machine the same model? Please let us know what kind of hardware you are doing this on. Check the BIOS settings as well. Searching for that error on the internet I found several people who have issues after cloning a machine. See if you can match up the BIOS settings of source and destination on disk geometry. See here:

                                The most likely solution is that your HD geometry is set wrong… On many motherboards in the BIOS setting for your HD, it is set to AUTO… which sometimes tries to use CHS which is incorrect for most modern computers. Manually set it to LBA instead.

                                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

                                P 1 Reply Last reply Reply Quote 0
                                • P
                                  plegrand @Sebastian Roth
                                  last edited by

                                  @Sebastian-Roth said:

                                  @plegrand Are source and destination machine the same model?

                                  It’s the same machine, i mean this machine act as source and destination
                                  Tomorrow i’ll make a test from the beginning and i will post the result here

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    Sebastian Roth Moderator
                                    last edited by Sebastian Roth

                                    @Tom-Elliott Do you know if the dell recovery partition could be causing the “Error loading operating system” problem? Looking at the sector numbers I don’t see why this could go wrong. sda1 is identical and sda2 starts at the exact same sector as before. Maybe the MBR is not copied properly?

                                    @plegrand Looking at the file listing you posted some days ago I don’t see d1.mbr file. Can you please verify that there is no d1.mbr in your image directory on the FOG server!? There definitely should be one I reckon! As well, do you really need the recovery partition?

                                    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

                                    Tom ElliottT Wayne WorkmanW 2 Replies Last reply Reply Quote 0
                                    • Tom ElliottT
                                      Tom Elliott @Sebastian Roth
                                      last edited by

                                      It’s possible the mbr was taken in the corrupted state. Maybe an upload then down would be good to go now that we’re not moving partitions around?

                                      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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                      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

                                      P 3 Replies Last reply Reply Quote 0
                                      • Wayne WorkmanW
                                        Wayne Workman @Sebastian Roth
                                        last edited by

                                        @Sebastian-Roth said:

                                        @Tom-Elliott Do you know if the dell recovery partition could be causing the “Error loading operating system” problem? Looking at the sector numbers I don’t see why this could go wrong. sda1 is identical and sda2 starts at the exact same sector as before. Maybe the MBR is not copied properly?

                                        I don’t really understand what happens with the MBR. Can we do math on the fly in the inits to go from the sector before the first partitions start sector, and copy from sector 0 to that, in order to get the entire MBR every time? Also, make a RAW copy of the MBR or whatever it takes to get it?

                                        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/

                                        1 Reply Last reply Reply Quote 0
                                        • P
                                          plegrand @Tom Elliott
                                          last edited by

                                          @Tom-Elliott said:

                                          It’s possible the mbr was taken in the corrupted state. Maybe an upload then down would be good to go now that we’re not moving partitions around?

                                          It’s what i’m doing.
                                          I will post the result once finished with the maximum of informations

                                          1 Reply Last reply Reply Quote 0
                                          • P
                                            plegrand @Tom Elliott
                                            last edited by plegrand

                                            @Tom-Elliott
                                            Here is the test i made with the same machine (same machine used for source and destination:

                                            Optiplex 760 – Windows XP
                                            3 partitions

                                            I upgraded fog to 4929 / 6547 version

                                            Image configuration used :
                                            default: Windows 2000/XP
                                            Single Disk - Resizable
                                            Everything

                                            I use an old symantec ghost image to restore the machine, at this moment this machine works fine.

                                            I launch debug capture task to see the configuration of partition on client before any operation

                                            Partitions just before capture task on client

                                            sfdisk -d /dev/sda
label: dos
label-id: 0x2bd2c32a
device: /dev/sda
unit: sectors

/dev/sda1 : start=          39, size=      257049, type=de
/dev/sda2 : start=      257088, size=   102398712, type=7, bootable
/dev/sda3 : start=   102655800, size=   209842152, type=7

                                            blkid -po udev /dev/sda1
ID_FS_SEC_TYPE=msdos
ID_FS_LABEL=DellUtility
ID_FS_LABEL_ENC=DellUtility
ID_FS_UUID=07D9-0C13
ID_FS_UUID_ENC=07D9-0C13
ID_FS_VERSION=FAT16
ID_FS_TYPE=vfat
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=2bd2c32a-01
ID_PART_ENTRY_TYPE=0xde
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=39
ID_PART_ENTRY_SIZE=257049
ID_PART_ENTRY_DISK=8:0

                                            blkid -po udev /dev/sda2
ID_FS_LABEL=OS
ID_FS_LABEL_ENC=OS
ID_FS_UUID=0660C20C60C20303
ID_FS_UUID_ENC=0660C20C60C20303
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=2bd2c32a-02
ID_PART_ENTRY_TYPE=0x7
ID_PART_ENTRY_FLAGS=0x80
ID_PART_ENTRY_NUMBER=2
ID_PART_ENTRY_OFFSET=257088
ID_PART_ENTRY_SIZE=102398712
ID_PART_ENTRY_DISK=8:0

                                            blkid -po udev /dev/sda3
ID_FS_LABEL=data
ID_FS_LABEL_ENC=data
ID_FS_UUID=86DC8201DC81EC2D
ID_FS_UUID_ENC=86DC8201DC81EC2D
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=2bd2c32a-03
ID_PART_ENTRY_TYPE=0x7
ID_PART_ENTRY_NUMBER=3
ID_PART_ENTRY_OFFSET=102655800
ID_PART_ENTRY_SIZE=209842152
ID_PART_ENTRY_DISK=8:0

                                            On fog server after capture task

                                            ls -al /home/images/test/
total 7983332
drwxrwxrwx 2 root root       4096 mars   4 09:28 .
drwxrwxrwx 7 root root       4096 mars   4 09:29 ..
-rwxrwxrwx 1 root root          3 mars   4 09:03 d1.fixed_size_partitions
-rwxrwxrwx 1 root root        249 mars   4 09:10 d1.minimum.partitions
-rwxrwxrwx 1 root root         30 mars   4 09:10 d1.original.fstypes
-rwxrwxrwx 1 root root          0 mars   4 09:04 d1.original.swapuuids
-rwxrwxrwx 1 root root    3704994 mars   4 09:10 d1p1.img
-rwxrwxrwx 1 root root 8170806888 mars   4 09:28 d1p2.img
-rwxrwxrwx 1 root root     386111 mars   4 09:28 d1p3.img
-rwxrwxrwx 1 root root        249 mars   4 09:04 d1.partitions

                                            cat d1.fixed_size_partitions
1:

                                            cat d1.minimum.partitions
label: dos
label-id: 0x2bd2c32a
device: /dev/sda
unit: sectors

/dev/sda1 : start=          39, size=      257049, type=de
/dev/sda2 : start=      257088, size=    31386018, type=7, bootable
/dev/sda3 : start=   102655800, size=      779520, type=7

                                            cat d1.original.fstypes
/dev/sda2 ntfs
/dev/sda3 ntfs

                                            cat d1.partitions
label: dos
label-id: 0x2bd2c32a
device: /dev/sda
unit: sectors

/dev/sda1 : start=          39, size=      257049, type=de
/dev/sda2 : start=      257088, size=   102398712, type=7, bootable
/dev/sda3 : start=   102655800, size=   209842152, type=7

                                            After capture task, the machine works fine
                                            After deploy task, the machine works fine

                                            I have to test now an other Dell machine Optiplex 9020 with windows seven and also 3 partitions
                                            I’ll come back to tell you if it works fine

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 2 / 5
                                            • First post
                                              Last post

                                            216

                                            Online

                                            11.6k

                                            Users

                                            17.1k

                                            Topics

                                            154.6k

                                            Posts
                                            Copyright © 2012-2024 FOG Project