FOG restore only one partition

[plegrand]

Hello
i’ve got a problem during deploy task on a windows xp station.

I made a capture task (entire dsk) and it seems that everything worked fine, i can see in the images directory all my partitions
When i make a deploy task, fog only restore the first partition with “test memory” and test system" tools

Does someone could explain me what is the problem ?
As i said in an other post, i move the “images” directory from “/images” to “/home/images”
Thanks

[ch3i]

@plegrand Hi, Could you try in debug task ?

Chosse debug task after select deploy task :

After PXE boot, you have to run fog task with fog command

[plegrand]

@ch3i then i use debug task and it restore only sda1, sda2 and sda3 are not restored

[plegrand]

@ch3i Here is the “image setting”

Image Name Portable Service Info
Image Description
Operating System Windows 2000/XP - (1)
Image Path /home/images/PortableServiceInfo
Image Type Single Disk - Resizable - (1)
Partition Everything - (1)

And here is the content of /home/images/PortableServiceInfo/
ls -al /home/images/PortableServiceInfo/
d1.fixed_size_partitions
d1.minimum.partitions
d1.original.fstypes
d1.original.swapuuids
d1p1.img
d1p2.img
d1p3.img
d1.partitions

i cant understand what is the problem
thanks again

[Wayne Workman]

@plegrand It might be permissions? use chmod -R 777 /home/images

Also, you can look through some of the files for this image and make sure details about sda2 and sda3 are included. Look inside of the d1.original.fstypes, d1.minimum.partitions, d1.fixed_size_partitions, and d1.partitions.

[plegrand]

@Wayne-Workman

drwxrwxrwx  5 root root      4096 févr.  4 12:35 images

cat d1.fixed_size_partitions
1:

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

/dev/sda1 : start=          63, size=      240912, type=de
/dev/sda2 : start=      240975, size=    34105626, type=7, bootable
/dev/sda3 : start=   156408840, size=    19799712, type=7

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

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

/dev/sda1 : start=          63, size=      240912, type=de
/dev/sda2 : start=      240975, size=   156167865, type=7, bootable
/dev/sda3 : start=   156408840, size=   156167865, type=7

[Tom Elliott]

What version of fog do you have?

[plegrand]

@Tom-Elliott The last one i think : in the cloud 6186

[plegrand]

@Tom-Elliott could it be the modification i made about storage
/images => /home/images ?

[Tom Elliott]

@plegrand we are now up to 6194 not that you will see any different results. Is this image truly an xp/2000 image? When was the image uploaded?

[plegrand]

@Tom-Elliott
I just upgraded now 6194
It’s trully an xp image from an old portable with windows XP
i made the test today with the 6186 version
i just made the test with the 6194 version with same problem

[Tom Elliott]

@plegrand I do know what the problem is though I don’t know of a good fix at the moment. I believe it’s because of checking done for the image files. Old XP images were to be a single partition/single file. But have no XP image to test with/from. What happens if you change the is version to Windows 10? I’d say 7 or 8 but I know that it would fail due to bcd files trying to be placed that aren’t used in XP. I set up Windows 10 to not replace the bcd though.

[Tom Elliott]

@plegrand I just rebuilt the init’s to attempt to approach this scenario (three partitions and what not for xp).

The one partition was a failure on my part. I was checking if the d1p1.img file was there and verifying it. This is correct, but i was never iterating partitions and what not for XP/Vista. This is because I guess XP/Vista are so old that I didn’t really expect any person to be using an image of these types in such a manner.

I’m almost certain, however, that this will still be an issue as we always default to using the FOG systems mbr file. This mbr file only has one partition within it. Maybe I was lucky with how I coded it though?

[Wayne Workman]

@Tom-Elliott said:

I’m almost certain, however, that this will still be an issue as we always default to using the FOG systems mbr file. This mbr file only has one partition within it. Maybe I was lucky with how I coded it though?

Sounds like a good reason to have… two… MBRs.

[plegrand]

@Tom-Elliott
then what i have to do ?
do you want i test with windows 10 version.
However this morning i updatet to 6209 version, and now when i try to deploy, partclone “tell” me that “This is not a partclone image”.
Did you change something ?

Thanks for your help

[plegrand]

@Tom-Elliott
I made the test with windows 10 version and this is not the same error :
Image store corrupt : Unable to locate MBR(restorePartitionTableAndBootLoaders)

[plegrand]

@Wayne-Workman
I saw on the wiki that there is 4 partition types :
Single Partition
Multiple Partition - Single Disk
Multiple Partition - All Disks
Raw Image

On the web frontend
Single Disk - Resizable - (1)
Multiple Partition Image - Single Disk (Not Resizable) - (2)
Multiple Partition Image - All Disks (Not Resizable) - (3)
Raw Image (Sector By Sector, DD, Slow) - (4)

As you can see the first option is different.
Then may be i would choose “Multiple Partition - Single Disk”
And it’s, may be, for this reason it failed now ?

[plegrand]

@Tom-Elliott
Then do you think i have to restore manually my station or it will be possible from fog ?

[Tom Elliott]

@plegrand Try changing the OS type to Windows 10.

[plegrand]

@Tom-Elliott
As i said before, i already done that without success