Fog 1.01 will not deploy linux image
-
If you can, update to the latest and greated.
I’ve, since this problem occurred, followed fractal13’s suggestions on doing, basically, exactly this. From all accounts this should work now. The reason it didn’t before was most likely because of the partitions not being restored properly which was a factor of just the mbr being re-included.
Hopefully it will give you better success. And you shouldn’t have to re-install grub for it to work as we’re collecting all the data of partition. Of course, this is assuming your image type is set to linux, we’ve not yet just added it as there’s no real easy way to detect if grub is installed, but with any luck, all will work properly for you.
-
[quote=“Tom Elliott, post: 30372, member: 7271”]If you can, update to the latest and greated.
I’ve, since this problem occurred, followed fractal13’s suggestions on doing, basically, exactly this. From all accounts this should work now. The reason it didn’t before was most likely because of the partitions not being restored properly which was a factor of just the mbr being re-included.
Hopefully it will give you better success. And you shouldn’t have to re-install grub for it to work as we’re collecting all the data of partition. Of course, this is assuming your image type is set to linux, we’ve not yet just added it as there’s no real easy way to detect if grub is installed, but with any luck, all will work properly for you.[/quote]
I upgraded to the latest release last week (I was using the svn version for the current release) and I am re-uploading the image(s) now. I will know for sure tomorrow or the next day as I plan to use the new image to push out to server 3 of this group of identical servers. The image type is Linux and all disks multi-partition no resize I am keeping the old image if you would like me to try with that one first.
Thanks
-
I’m pretty sure we don’t really need the old, but seeing as you know how to recover using it, it couldn’t hurt to just have a backup just incase.
-
[quote=“Tom Elliott, post: 30374, member: 7271”]I’m pretty sure we don’t really need the old, but seeing as you know how to recover using it, it couldn’t hurt to just have a backup just incase.[/quote]
Well I deployed the second image set today and as with the previous attempts it failed to deploy until I created a blank partition table (via PartEd) on each drive. I did find something else out that might help. When I created the blank partition tables I missed sdd, when I deployed it did sda-sdc correctly but then deployed the sdd image to sdf and f to g so when it’s restoring the images for some reason of the partition table is blank it treats that drive as non existent… instead of failing sdd it just put in on hd4 instead of hd3. Is there a way you test for the existance of a partition table and apply one in the even it’s missing? Again this was not an issue with windows images just the linux image(s). On a positive note, once I corrected the missing part table on sdd and redeployed the image I did not have to repair grub this time
-
I’ll take a look at the init then. Chances are it needs to create one after wiping the drive which should help you out. It shouldn’t matter how big or anything, but it should work.
-
I’m adding some code to test in theory. I believe partprobe only inserts the partition table of the first disk found, not all disks.
I’ve modified the code to run for all disks, hopefully it will still work.
-
If it’s in svn I can test it by deleting the part tables and try again tomorrow
-
It is all in svn now. I don’t know if it will work, but hopefully…
