SVN 3587 - Failed to restore image
FOG = 3587
uploaded an image from Latitude 3550 worked fine.
Single Disk - Resizable
Protected = N (what is this one?)
Compression = 6
On trying to deploy to another laptop (same model/purchase date(so firmware)) i get “failed to restore image”.
not sure if bug of config issue. (added to bug as not live ver)
@ITCC lol… IMO, the speed bump is the single biggest improvement to FOG Trunk.
Everyone can thank @Junkhacker for that, he’s the one that improved it.
I have upgraded fog to the latest SVN (3596)
Not that this made an diff but an update.
I uploaded a basic build we have instead of the Dell OS and it deployed in 2mins !!! i’m sure this is faster than .32 (current live)
The image must be decompressed first as well.
This is ran from within the image folder.
cat d1p2.img | pigz -d -c | partclone.restore -O /dev/sda2 -N -f -i -C
@ITCC Maybe check this out…
I imagine you’d just use this command instead of the one in that article:
[CODE]/usr/sbin/partimage restore /dev/sda1 /images/[imagename] -f3 -b -C[/CODE]
But, those instructions are for partimage… the new FOG uses partclone so I don’t even know if these instructions are valid or not… probably not…
This article needs updated… it’s in the WiKi To-Do list…
I agree. I’ll opt out of this i think. would be nice if you could just add to the “Host Kernel Arguments” or something.
@ITCC You’d issue that command manually from a debug task (I think)… I haven’t figured it out yet. Thing is though, when you run the “fog” command on the client and hit enter on the mounting and MBR and all that other stuff, when it comes to the partclone command, you’d hit “Ctrl+C” to exit the “fog” script, then execute the Partclone -C option manually… (don’t know how to do that), but after it finishes, you have to do all the other commands manually (don’t know how t o do that) because you exited the script… Just seems like a huge hassle to me - especially when you can just make a scratch image.
how do i use option -C (for testing…)
Yes, image is the Dell base OS as this was just a test. Live images are manually created so this shouldn’t be an issue.
Ok. This is a known issue with Dells. The problem is that Dell creates their very own custom MBR and it’s about a meg larger than a standard MBR. FOG makes standard MBRs at the moment… the wheels are turning on this issue… but I don’t know how long it’ll take to get addressed.
There is a work around… don’t use the manufacturer’s base image. Build your very own image from scratch.
There is another topic for that problem : https://forums.fogproject.org/topic/5220/target-partition-size-is-smaller-than-source
the GUI error only shows for a second so missed the 1st time !
@ITCC Can you post a photo of the error? This would be very helpful for us to figure out where things are going wrong and what might be causing it.