FOG restore only one partition

Sebastian Roth · Mar 2, 2016, 6:45 AM

@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.

plegrand · Mar 3, 2016, 7:16 AM

@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

Sebastian Roth · Mar 3, 2016, 7:20 AM

@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.

plegrand · Mar 3, 2016, 2:46 AM

@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

Sebastian Roth · Mar 3, 2016, 4:09 PM

@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.

plegrand · Mar 3, 2016, 5:27 PM

@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

Sebastian Roth · Mar 3, 2016, 1:28 PM

@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?

Tom Elliott · Mar 3, 2016, 7:18 PM

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?

Wayne Workman · Mar 4, 2016, 4:51 AM

@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?

plegrand · Mar 4, 2016, 8:07 AM

@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

plegrand · Mar 4, 2016, 2:57 AM

@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

plegrand · Mar 4, 2016, 1:10 PM

@Tom-Elliott Hello

Then i made an other test with an other machine (DELL optiplex 9020 - windows 7 - 3 partitions)
And it doesnt works
here is the result, sorry it’s little long

Optiplex 9020
Windows 7
3 partitions

Partitions configuration before “debug capture task”

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

/dev/sda1 : start=          63, size=       80262, type=de
/dev/sda2 : start=       81920, size=     1536000, type=7, bootable
/dev/sda3 : start=     1617920, size=   975153200, type=7

blkid -po udev /dev/sda1
ID_FS_SEC_TYPE=msdos
ID_FS_LABEL=DellUtility
ID_FS_LABEL_ENC=DellUtility
ID_FS_UUID=5450-4444
ID_FS_UUID_ENC=5450-4444
ID_FS_VERSION=FAT16
ID_FS_TYPE=vfat
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=97be5b6a-01
ID_PART_ENTRY_TYPE=0xde
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=63
ID_PART_ENTRY_SIZE=80262
ID_PART_ENTRY_DISK=8:0

blkid -po udev /dev/sda2
ID_FS_LABEL=RECOVERY
ID_FS_LABEL_ENC=RECOVERY
ID_FS_UUID=B2FA97C8FA97876F
ID_FS_UUID_ENC=B2FA97C8FA97876F
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=97be5b6a-02
ID_PART_ENTRY_TYPE=0x7
ID_PART_ENTRY_FLAGS=0x80
ID_PART_ENTRY_NUMBER=2
ID_PART_ENTRY_OFFSET=81920
ID_PART_ENTRY_SIZE=1536000
ID_PART_ENTRY_DISK=8:0

blkid -po udev /dev/sda3
ID_FS_LABEL=OS
ID_FS_LABEL_ENC=OS
ID_FS_UUID=A2B89AD7B89AA975
ID_FS_UUID_ENC=A2B89AD7B89AA975
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=97be5b6a-03
ID_PART_ENTRY_TYPE=0x7
ID_PART_ENTRY_NUMBER=3
ID_PART_ENTRY_OFFSET=1617920
ID_PART_ENTRY_SIZE=975153200
ID_PART_ENTRY_DISK=8:0

Messages :
Clearing part (/dev/sda2) …Reg file not found
Clearing part (/dev/sda3) …Reg file not found

Partitions configuration after capture task

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

/dev/sda1 : start=          63, size=       80262, type=de
/dev/sda2 : start=       81920, size=     1536000, type=7, bootable
/dev/sda3 : start=     1617920, size=   975153200, type=7

blkid -po udev /dev/sda1
ID_FS_SEC_TYPE=msdos
ID_FS_LABEL=DellUtility
ID_FS_LABEL_ENC=DellUtility
ID_FS_UUID=5450-4444
ID_FS_UUID_ENC=5450-4444
ID_FS_VERSION=FAT16
ID_FS_TYPE=vfat
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=4771a6a0-01
ID_PART_ENTRY_TYPE=0xde
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=63
ID_PART_ENTRY_SIZE=80262
ID_PART_ENTRY_DISK=8:0

blkid -po udev /dev/sda2
ID_FS_LABEL=RECOVERY
ID_FS_LABEL_ENC=RECOVERY
ID_FS_UUID=B2FA97C8FA97876F
ID_FS_UUID_ENC=B2FA97C8FA97876F
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=4771a6a0-02
ID_PART_ENTRY_TYPE=0x7
ID_PART_ENTRY_FLAGS=0x80
ID_PART_ENTRY_NUMBER=2
ID_PART_ENTRY_OFFSET=81920
ID_PART_ENTRY_SIZE=1536000
ID_PART_ENTRY_DISK=8:0

blkid -po udev /dev/sda3
ID_FS_LABEL=OS
ID_FS_LABEL_ENC=OS
ID_FS_UUID=A2B89AD7B89AA975
ID_FS_UUID_ENC=A2B89AD7B89AA975
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=4771a6a0-03
ID_PART_ENTRY_TYPE=0x7
ID_PART_ENTRY_NUMBER=3
ID_PART_ENTRY_OFFSET=1617920
ID_PART_ENTRY_SIZE=975153200
ID_PART_ENTRY_DISK=8:0

On the fog server

ls -al
total 15439040
drwxrwxrwx 2 root root        4096 mars   4 12:28 .
drwxrwxrwx 7 root root        4096 mars   4 13:19 ..
-rwxrwxrwx 1 root root           3 mars   4 11:57 d1.fixed_size_partitions
-rwxrwxrwx 1 root root         249 mars   4 12:02 d1.minimum.partitions
-rwxrwxrwx 1 root root          30 mars   4 11:58 d1.original.fstypes
-rwxrwxrwx 1 root root           0 mars   4 11:57 d1.original.swapuuids
-rwxrwxrwx 1 root root       78718 mars   4 12:02 d1p1.img
-rwxrwxrwx 1 root root   186067670 mars   4 12:02 d1p2.img
-rwxrwxrwx 1 root root 15623396077 mars   4 12:28 d1p3.img
-rwxrwxrwx 1 root root         249 mars   4 11:57 d1.partitions


cat d1.fixed_size_partitions
1:

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

/dev/sda1 : start=          63, size=       80262, type=de
/dev/sda2 : start=       81920, size=     1536000, type=7, bootable
/dev/sda3 : start=     1617920, size=    70285300, type=7

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

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

/dev/sda1 : start=          63, size=       80262, type=de
/dev/sda2 : start=       81920, size=     1536000, type=7, bootable
/dev/sda3 : start=     1617920, size=   975153200, type=7

Reboot

Windows Boot Manager
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:

        Insert your Windows installation disc and restart your computer.
        Choose your language settings, and then click "Next."
        Click "repair your computer."

    If you don't have this disc, contact your system administrator or computer manufacturer for assistance.

    Status: 0xc000000e

    Info: The boot selection failed because a required device is inaccessible.

Then i launch a deploy task
After the deploy task, the machine stay on “Booting…”

Here is partitions configuration after deploy task

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

/dev/sda1 : start=          63, size=       80262, type=de
/dev/sda2 : start=       80325, size=     1536000, type=7, bootable
/dev/sda3 : start=     1616325, size=   975156736, type=7

blkid -po udev /dev/sda1
ID_FS_SEC_TYPE=msdos
ID_FS_LABEL=DellUtility
ID_FS_LABEL_ENC=DellUtility
ID_FS_UUID=5450-4444
ID_FS_UUID_ENC=5450-4444
ID_FS_VERSION=FAT16
ID_FS_TYPE=vfat
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=63c5f4a0-01
ID_PART_ENTRY_TYPE=0xde
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=63
ID_PART_ENTRY_SIZE=80262
ID_PART_ENTRY_DISK=8:0

blkid -po udev /dev/sda2
ID_FS_LABEL=RECOVERY
ID_FS_LABEL_ENC=RECOVERY
ID_FS_UUID=B2FA97C8FA97876F
ID_FS_UUID_ENC=B2FA97C8FA97876F
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=63c5f4a0-02
ID_PART_ENTRY_TYPE=0x7
ID_PART_ENTRY_FLAGS=0x80
ID_PART_ENTRY_NUMBER=2
ID_PART_ENTRY_OFFSET=80325
ID_PART_ENTRY_SIZE=1536000
ID_PART_ENTRY_DISK=8:0

blkid -po udev /dev/sda3
ID_FS_LABEL=OS
ID_FS_LABEL_ENC=OS
ID_FS_UUID=A2B89AD7B89AA975
ID_FS_UUID_ENC=A2B89AD7B89AA975
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_UUID=63c5f4a0-03
ID_PART_ENTRY_TYPE=0x7
ID_PART_ENTRY_NUMBER=3
ID_PART_ENTRY_OFFSET=1616325
ID_PART_ENTRY_SIZE=975156736
ID_PART_ENTRY_DISK=8:0

Thanks for your help

Tom Elliott · Mar 4, 2016, 1:12 PM

@plegrand Where’s the d1.mbr file? I know it is created (or at least it should be).

plegrand · Mar 4, 2016, 1:13 PM

@Tom-Elliott where i should search ?

plegrand · Mar 4, 2016, 7:18 AM

@Tom-Elliott On the fog server in the image directory of the machine there is no “d1.mbr”

And for my other test before (xp machine) there is no d1.mbr but deploy and capture works fine.
D1.mbr is may be only usefull for windows 7 ?

Tom Elliott · Mar 4, 2016, 1:19 PM

@plegrand that’s my concern though. THe d1.mbr should be created for ALL uploads. Especially the Windows 7 stuff.

Tom Elliott · Mar 4, 2016, 1:19 PM

That isn’t your concern though, that’s mine. Just noting it’s a problem and I don’t know why it’s even happening.

plegrand · Mar 4, 2016, 1:21 PM

@Tom-Elliott i can make other tests if you want

Tom Elliott · Mar 4, 2016, 11:01 PM

I found out why the d1.mbr/d1.grub.mbr file wasn’t being created.

Yes, it’s kind of an important bit. Please update and re-upload the windows 7 guy (as well as your windows xp if you feel up to it.)

I know i’m asking a lot, but I really think we have all the kinks fixed now. (hopefully).

Again, my only worry on the Win 7 is in the case of resizable we do place our own generalized BCD file. I think this can cause issues, but it can be fixed. I don’t remove the original bcd, rather I move it to a BCD.bak

plegrand · Mar 5, 2016, 11:45 AM

@Tom-Elliott said:

I found out why the d1.mbr/d1.grub.mbr file wasn’t being created.

Yes, it’s kind of an important bit. Please update and re-upload the windows 7 guy (as well as your windows xp if you feel up to it.)

I will test on Monday. Do i have to capture again before ?
I will test for the windows 7 machine and windows XP machine

I know i’m asking a lot, but I really think we have all the kinks fixed now. (hopefully).

No problem for me. If i want it works …

FOG restore only one partition

151

12.0k

17.3k

155.2k