Missing partitions after image download
-
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
-
What version of FOG? Is the disk MBR or GPT?
-
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. -
@patc15 Good find, and it looks like it has been fixed in Trunk. Here is info on updating to trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
As always, I would advise a DB and Host backup. Details on how to do those are at the bottom of that article. Please let us know if FOG Trunk can capture/deploy your image properly.
-
@Wayne-Workman Trunk = new, possibly buggy beta? I will try it out and report back. Thanks for the quick responses, Wayne!
-
@patc15 said:
@Wayne-Workman Trunk = new, possibly buggy beta? I will try it out and report back. Thanks for the quick responses, Wayne!
Yes, the potential for bugs exist. It’s best hosted on a VM with snapshots for safety. If you can do without this new feature and your fog server is in production right now and otherwise working fine, I’d ask you to wait for the 1.3.0 release.
But if you’re just using FOG at home or if it’s in a VM with snapshots, yeah, go for it.
-
@patc15 AFAIK version 4848 (GIT) / 4103 (SVN) is pretty good. Wayne said that he has spend a lot of time testing all the features of this revision. Maybe you want to give this a try on a test server to see if this is solving the issue for you.
-
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.
-
@Uncle-Frank @Wayne-Workman 4848 solved my extended partition problem. Thanks a lot!