Problem uploading EXT3 Ubuntu image



  • Has anyone experienced problems uploading an EXT3 Ubuntu image on 0.32?

    I need to get Linux imaging working with FOG. Windows imaging is set up and has been working great for months. While I wait for EXT4 support in 0.33, I’m trying to at least test with EXT3.

    I install Ubuntu (tested both 12.04 beta and 11.10 with EXT3 and a swap part), set the image to single disk multi partition, and initiate the upload task. When I PXE boot the machine, it appears to go through the process, but finishes each upload instantly. It errors on the swap partition, saying it’s not supported. When I “ls -l” the /images/ directory on the server, the .mbr and .img files are there, but they are both only 6 bytes.

    I have tried installing Grub Legacy per other threads, but it doesn’t help. It seems like that only fixes a problem when deploying images, anyway. I have also tried a kernel from 0.29, from 0.32, and the 3.2.4 kernel per this thread:
    fogproject.org/forum/threads/fog-0-33-whats-coming.18/page-2

    I get the same results each time.

    Does anyone have any ideas? I would appreciate any tips and suggestions.


  • Senior Developer

    The issue I think, is not with the image or deploy. I think it’s more related to the GRUB and MBR file.

    You’re systems aren’t booting because they don’t know where to look at the hard drive for the information, so they just reboot, and the cycle keeps happening.



  • [quote=“atef, post: 12814, member: 3598”]I do the same,
    But the image can be deployed to only one machine its veruy strange; also I used Boot Repaire [COLOR=#0000ff][U][url]https://help.ubuntu.com/community/Boot-Repair[/url] [/U][/COLOR][COLOR=#0000ff][COLOR=#000000] and the same problem was happen.[/COLOR][/COLOR]

    Image ubuntu 12.04 ext3,
    after Pushing image the clients keep rebooting.
    any Idea <!>[/quote]
    This is the same problem that I am running into. Anyone have any ideas?



  • I do the same,
    But the image can be deployed to only one machine its veruy strange; also I used Boot Repaire [COLOR=#0000ff][U][url]https://help.ubuntu.com/community/Boot-Repair[/url] [/U][/COLOR][COLOR=#0000ff][COLOR=#000000] and the same problem was happen.[/COLOR][/COLOR]

    Image ubuntu 12.04 ext3,
    after Pushing image the clients keep rebooting.
    any Idea <!>



  • Thank you for the advice (run fsck!).

    Here I had the same problem: ubuntu 12.04, ext3 partition, uploaded a 900 bytes image!

    I run a fsck (which said “everything clean”), and the image is now uploading …
    now try to deploy it :-)

    bye
    giammy



  • Hi Pandemonium,

    I’ m having the same problem with the ubuntu 12.04 (actually just one machine uploaded the image correctly), the fsck with a live cd turn the drive “imageable”?

    Troy



  • We deployed Ubuntu 11.10 with fog.

    Installing GRUB did not work.
    We had to boot every PC and install GRUB per hand (grub-install /dev/sda).
    This had to be done once. Cloneing the second time worked. We gess, that the MBR is not wirtten correct.

    After Upgrading from working 11.10 to 12.04 deploying the same! host was not possible! Partitions did not change. (very strange?)

    After trying several partionings:

    / on /dev/sda1
    swap on /dev/sda5 logical

    could be deployed, but cloned maschine has no swappartition.



  • Update: I finally tried manually using PartImage to pull the image with the plan to then copy it manually in to the server. In doing so, I saw that PartImage was erroring out (which FOG was hiding). Googling around found that running an fsck prior to uploading the image fixes the problem. I may dig in to the FOG code to see if I can make it automatically run an fsck prior to pulling any Linux image. For now, though, I just boot my source PC in to a live CD and fsck, then I upload the image. Works a treat.

    Hopefully this will all just work better when 0.33 comes out.


Log in to reply
 

441
Online

38994
Users

10714
Topics

101704
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.