@Uncle-Frank @Wayne-Workman 4848 solved my extended partition problem. Thanks a lot!

@Uncle-Frank @Wayne-Workman 4848 solved my extended partition problem. Thanks a lot!

OK I’ll give that a go. I’m having problems with the latest revision (client isn’t detecting FOG server during PXE boot) so I’ll try 4848.

EDIT: Just kidding, dhcpd got uninstalled somehow on my FOG server lol.

Has this been fixed in the latest svn revision? Because I’m having this problem as well (2 NICS and a forever sending discover loop).

@Wayne-Workman Trunk = new, possibly buggy beta? I will try it out and report back. Thanks for the quick responses, Wayne!

1.2.0, MBR. SUSE linux
I provided two screenshots. First is correct partition list. Second is what happened after image download. Does this have to do with the extended partition??

I looked here: https://forums.fogproject.org/topic/2885/extended-logical-partitions-proposed-solution
Seems like Tom already implemented a solution to this though? Correct me if I’m wrong.

I successfully was able to upload a Multiple Partition - Single Disk image to my fog server, then I downloaded that image successfully, with all partitions being downloaded (I have screenshots of this). But after the download and when I boot, I get this error:

fsck.ext3: Unable to resolve ‘LABEL=mylabel’

So I checked out fdisk -l and noticed that my /dev/sda6 and /dev/sda7 partitions are not listed, even though during the image download it said it was successful. How do I fix this / prevent this from happening?

EDIT: Fog 1.2.0, disk is MBR. SUSE linux