@nicolas-illi said in Problem of deployment of an old image:
I have 11 more images which I had created with FOG 1.2.0.
Ahh, I kind of figured that would be the case. But before we get to that let me say that I insist on you taking fresh images after having fixed and deployed those to your machines. Keep a backup copy of the old image files just in case (somewhere on a backup disk) and upload/capture fresh new images using the new FOG server!
Ok, so what do you need to do to fix those MBR files. Schedule a debug deploy task, boot up the client and start the process running the fog
command when you get to the shell. It will fail and drop you back to the shell. But it also deployed the MBR/partition layout half way. Back to the shell run gdisk /dev/sda
and it will tell you about a corrupt GPT and so on but it should also have the correct partition layout and all that. Simply type w
and hit ENTER, then y
and ENTER again to write changes and correct the whole layout. Now you have a proper MBR/partition layout on that client’s disk which you can check and then get a dump like that:
gdisk -l /dev/sda
...
...
sgdisk -b /root/d1.mbr /dev/sda
Now you only need to get that back to your server’s image directory. The easy way is to plug in a FAT32 formated USB key to your client and run:
mkdir -p /media/usb
mount /dev/sdb1 /media/usb
mv /root/d1.mbr /media/usb
umount /media/usb
Unplug the USB key, go to your FOG server and save that d1.mbr
file into the /images/...
directory of that image you just used on that client.
Now back to that client - no need to reboot or anything - just run fog
again and it should deploy without an issue.