image failed to restore and exited with exit code 0



  • Server
    • FOG Version: 1.2.0
    • OS: Ubuntu
    Client
    • Service Version:
    • OS:
    Description

    Hi,
    I have added on my fog server a new hdd.
    To add the new hdd, i used this link:
    https://wiki.fogproject.org/wiki/index.php?title=Adding_Storage_to_a_FOG_Server

    Now, i can deploy but i have this error all the time:
    image failed to restore and exited with exit code 0 (writeImage)

    Do you have a solution for me ?

    Thanks

    Best Regards.



  • Thank you for your help.

    Best regards.


  • Moderator

    @afaure The image must be corrupt then, as you guessed.



  • Hi @Wayne-Workman,

    Yes, i have enabled the flag in the settings.
    FOG Configuration Page->FOG Settings->General Settings->FOG_FORMAT_FLAG_IN_GUI

    In the second time i have changed the format of my image.
    I have changed my image format of PartImage for PartClone.

    The result is the same.

    Do you want a screenshot of my image settings ?


  • Moderator

    @afaure You realize the change is 2-phase right? You enable the format flag, then you change the particular image’s format.



  • Hi,

    Thank you for your reply.

    I have changed this settings.
    I have the same thing…

    My image is corrupt, i guess.
    I think do a new image of this computer.

    Thanks for your help.

    Best regards.


  • Senior Developer

    @Wayne-Workman and @afaure :

    FOG Configuration Page->FOG Settings->General Settings->FOG_FORMAT_FLAG_IN_GUI


  • Moderator

    @afaure said in image failed to restore and exited with exit code 0:

    The format is PartClone for all working images.
    On the other hand, the format of images is Partimage and doesn’t work.
    How i can change this format to test ?

    @Tom-Elliott please correct me on this, I’ve not had to use it but,

    @afaure there is an option somewhere inside of Web Interface -> FOG Configuration probably in General Settings but I could be wrong (no access to fog server right now). The option is to turn on image management something or another, it’s an option that enables choosing the image management (partclone or partimage) for each image you have. Look around in there and you will find the option, enable it, and then you will be able to switch images to partclone or partimage as you please.

    Keep in mind, if an image was captured with partclone, it must be deployed with partclone, and vice versa with partimage.


  • Senior Developer

    @afaure What isn’t working?

    Permissions are not the casue of the exit code 0. This still feels/seems like a problem with the actual image, not a problem with permissions.

    You could, possibly, try ensuring it’s got root permissions too:

    sudo chown -R root:root /images && sudo chmod -R 777 /images

    However, it isn’t going to fix the exit code 0 problem.

    There are, however, cases where I’ve heard of this and it’s specific to the hard drive.

    maybe try a debug deploy and manually wipe the disk? (Just a thought).



  • @Wayne-Workman,

    It doesn’t work :(

    The format is PartClone for all working images.
    On the other hand, the format of images is Partimage and doesn’t work.

    How i can change this format to test ?
    The new version of FOG is compatible with Partimage ?

    Thank you again !


  • Moderator

    @afaure From your last post, your permissions are messed up on your images now. I assume that’s from manually copying over your backups. You can fix it with these commands:

    chown -R fog:root /images
    chmod -R 777 /images
    

    Then they might work.
    What could be happening here is your FOG server’s HDD is failing - just a possibility.



  • Hi @Wayne-Workman,

    I tried with other image.
    It’s works !!

    But, I do not understand … I used this image several times this year…

    I have a copy in my external hard drive… But, i tried and it doesn’t works…
    Do you have a solution to fix this image ?

    Thank you

    Edit:

    I don’t understand…

    The image ThinkPadEdgeWin7 work and the image Optiplex380 doesn’t work…

    root@DeploiementFOG:/images# ls -la
    total 124
    drwxrwxrwx 28 fog         root         4096 déc.   8 10:07 .
    drwxr-xr-x 26 root        root         4096 déc.   7 09:52 ..
    drwx------  2 utilisateur utilisateur  4096 août  11  2015 DellLatitudeE6400
    drwx------  2 utilisateur utilisateur  4096 févr.  6  2015 DellLatitudeE7240RDC
    drwx------  2 utilisateur utilisateur  4096 janv. 18  2016 DellOptiplex7010
    drwx------  2 utilisateur utilisateur  4096 févr.  6  2015 DELLPRECISIONM2800
    drwx------  2 utilisateur utilisateur  4096 févr. 12  2016 DELLPRECISIONM28002016
    drwx------  2 utilisateur utilisateur  4096 févr.  4  2015 DELLPRECISIONM4800
    drwx------  2 utilisateur utilisateur  4096 août  11  2015 DellVostro430
    drwxrwxrwx  2 fog         root         4096 sept. 29 14:43 dev
    drwx------  2 utilisateur utilisateur  4096 févr.  2  2015 LatitudeE5250
    drwx------  2 utilisateur utilisateur  4096 janv. 21  2015 LatitudeE5440
    drwx------  2 utilisateur utilisateur  4096 août  11  2015 LatitudeE5500SEVEN
    drwx------  2 utilisateur utilisateur  4096 août  11  2015 LatitudeE5500XP
    drwx------  2 utilisateur utilisateur  4096 août  11  2015 LatitudeE5510SEVEN
    drwx------  2 utilisateur utilisateur  4096 août  11  2015 LenovoB560SEVEN
    drwx------  2 utilisateur utilisateur  4096 déc.  24  2014 LenovoE530
    drwx------  2 utilisateur utilisateur  4096 févr. 12  2015 LenovoL520
    drwxrwxrwx  2 fog         root        16384 déc.   2 10:51 lost+found
    -rwxrwxrwx  1 fog         root            0 déc.   2 17:10 .mntcheck
    drwx------  2 utilisateur utilisateur  4096 sept. 29 14:43 Optiplex3020_2014
    drwx------  2 utilisateur utilisateur  4096 août  11  2015 Optiplex3020MT
    drwx------  2 utilisateur utilisateur  4096 août  11  2015 Optiplex380
    drwx------  2 utilisateur utilisateur  4096 août  11  2015 optiplex755
    drwxrwxr-x  7 utilisateur utilisateur  4096 déc.   7 18:00 PI
    drwxrwxrwx  2 fog         root         4096 janv. 21  2015 postdownloadscripts
    drwx------  2 utilisateur utilisateur  4096 janv. 14  2016 PrecisionT3500
    drwx------  2 utilisateur utilisateur  4096 mai   19  2015 ThinkpadEdgeWin7
    drwxrwxrwx  5 fog         utilisateur  4096 déc.   2 15:55 .Trash-1000
    
    root@DeploiementFOG:/images# cd Optiplex380/
    root@DeploiementFOG:/images/Optiplex380# ls -la
    total 8679772
    drwx------  2 utilisateur utilisateur       4096 août  11  2015 .
    drwxrwxrwx 28 fog         root              4096 déc.   8 10:07 ..
    -rw-------  1 utilisateur utilisateur        512 déc.   2  2014 d1.mbr
    -rw-------  1 utilisateur utilisateur    8729067 déc.   2  2014 d1p1.img
    -rw-------  1 utilisateur utilisateur 8870642916 déc.   2  2014 d1p2.img
    
    root@DeploiementFOG:/images/Optiplex380# cd ../ThinkpadEdgeWin7/
    root@DeploiementFOG:/images/ThinkpadEdgeWin7# ls -la
    total 11318296
    drwx------  2 utilisateur utilisateur        4096 mai   19  2015 .
    drwxrwxrwx 28 fog         root               4096 déc.   8 10:07 ..
    -rw-------  1 utilisateur utilisateur         512 mai   19  2015 d1.mbr
    -rw-------  1 utilisateur utilisateur     8797910 mai   19  2015 d1p1.img
    -rw-------  1 utilisateur utilisateur 11569786942 mai   19  2015 d1p2.img
    root@DeploiementFOG:/images/ThinkpadEdgeWin7# 
    

    0_1481188236889_list_image.png

    I can do something ?

    Thank you.


  • Moderator

    @afaure Try a different image - I’m starting to think that this particular image is bad. Also try to image a different computer as well.



  • Hi @Wayne-Workman

    Ok. I will install the uptdate with the svn method.
    I come again said the result !

    Thank you :)

    Edit:
    I have update my fog with git method.
    I have this error now:
    0_1481102397416_IMAG0647.jpg

    Do you have idea ?

    Thank you


  • Moderator

    @afaure The first issue I see is that you are not on FOG 1.2.0, but you’re actually on a very old version of FOG Trunk (between 1.2.0 and 1.3.0 Release Candidate).

    My first advice is to update to the very latest Release Candidate of 1.3.0, you would do this by just following the upgrade to trunk article in the wiki:
    https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

    This alone could potentially solve your issue with deployment. I looked over everything you posted, everything seems to be in order, so I’d say update.



  • @Wayne-Workman Hi,

    Thanks for reply.

    The version in the bubble of fog is 6267.
    The result of commands :

    utilisateur@DeploiementFOG:~$ lsblk
    NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
    sda      8:0    0 149,1G  0 disk 
    ├─sda1   8:1    0 147,1G  0 part /
    ├─sda2   8:2    0     1K  0 part 
    └─sda5   8:5    0     2G  0 part [SWAP]
    sdb      8:16   0 465,8G  0 disk 
    └─sdb1   8:17   0 465,8G  0 part /images
    
    utilisateur@DeploiementFOG:~$ df -h
    Filesystem      Size  Used Avail Use% Mounted on
    udev            1,9G  4,0K  1,9G   1% /dev
    tmpfs           390M  1,3M  389M   1% /run
    /dev/sda1       145G  120G   19G  87% /
    none            4,0K     0  4,0K   0% /sys/fs/cgroup
    none            5,0M     0  5,0M   0% /run/lock
    none            2,0G  412K  2,0G   1% /run/shm
    none            100M   40K  100M   1% /run/user
    /dev/sdb1       459G  119G  320G  28% /images
    
    utilisateur@DeploiementFOG:~$ showmount -e
    Export list for DeploiementFOG:
    /images/dev *
    /images     *
    
    utilisateur@DeploiementFOG:~$ sudo ls -la /images
    [sudo] password for utilisateur: 
    total 60
    drwxrwxrwx 12 fog  root         4096 déc.   2 17:07 .
    drwxr-xr-x 26 root root         4096 déc.   6 15:52 ..
    drwxrwxrwx  2 fog  root         4096 févr. 15  2016 DellLatitudeE54702016
    drwxrwxrwx  2 fog  root         4096 févr. 11  2016 DellLatitudeE7450
    drwxrwxrwx  2 fog  utilisateur  4096 janv. 18  2016 DellOptiplex7010
    drwxrwxrwx  2 fog  root         4096 sept. 29 14:43 dev
    drwxrwxrwx  2 fog  utilisateur  4096 janv. 21  2015 LatitudeE5440
    drwxrwxrwx  2 fog  root        16384 déc.   2 10:51 lost+found
    -rwxrwxrwx  1 fog  root            0 déc.   2 17:10 .mntcheck
    drwxrwxrwx  2 fog  root         4096 sept. 29 14:43 Optiplex3020_2014
    drwxrwxrwx  2 fog  utilisateur  4096 août  11  2015 Optiplex380
    drwxrwxrwx  2 fog  root         4096 janv. 21  2015 postdownloadscripts
    drwxrwxrwx  5 fog  utilisateur  4096 déc.   2 15:55 .Trash-1000
    

    In attachment 3 picture with the first screen of fog and the configuration of my storage node.

    2_1481037709907_storage_node_conf.png 1_1481037709907_storage_mgnt.png 0_1481037709906_home_fog.png

    Thanks for your help !

    Mod edited to use code boxes.


  • Moderator

    @afaure What version is in/around the FOG bubble in the top left of the web interface?

    Also, what is the output of these commands on your fog server:
    lsblk
    df -h
    showmount -e

    Also, please post a screenshot of your storage node(s) configuration.

    Feel free to blot out IP addresses if you feel it necessary, we don’t really need them, we need to look at paths, mounts, exports, permissions, and some other things.



  • Hi,

    Thank for reply.

    I downloaded and installed the latest verison published friday.
    I installed this version after the error of deployment.

    I saved my database of pictures and workstation.
    I think reinstall the solution on the new server.

    My fisrt version of FOG is 0.32 in 2014.
    I have update FOG several times since 2014.

    However this time, the uptate doens’t work…


  • Senior Developer

    Something seems fishy to me. The error messages you’re seeing should not appear in FOG 1.2.0 (as the init’s didn’t even get those changes until WAY later on in the development versions).

    If you are running on 1.2.0, but installed a more recent version what is the new version you actually attempted to install?


Log in to reply
 

402
Online

39.4k
Users

11.1k
Topics

105.5k
Posts

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