• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    No source file passed (writeImage)

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    7
    33
    8.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Tom ElliottT
      Tom Elliott @Lombard
      last edited by

      @Lombard You should not need to change the partition type.

      Changing the sys.img.000 to d1p1.img will also not make the image usable due to how the imaging grabs the information.

      That said this should work in its current state. I’ll review when I have more time tonight.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      1 Reply Last reply Reply Quote 0
      • D
        drifter666
        last edited by drifter666

        I’m also having the exact same issue. We captured more info just from above the OP picture. See picture below. All our images are single-disk resize and once we upgraded to 1.3.5, they broke. All images were built in the 1.2.0 release. Thanks for the help.

        0_1490717925858_added_info.jpg
        0_1490718154651_added_info2.jpg
        0_1490718249308_added_info3.jpg

        george1421G 1 Reply Last reply Reply Quote 0
        • george1421G
          george1421 Moderator @drifter666
          last edited by george1421

          @drifter666 While I have no basis behind this suspicion, In the image definition for students, is the field “Image Manager” (as in your OP picture) set to partclone? If so can you try Partimage instead. Then do a test deploy again.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

          1 Reply Last reply Reply Quote 0
          • D
            drifter666
            last edited by drifter666

            Yeah, we did try that and the issue is the same. Did you want me to capture a screen shot of this as well with PartClone selected?

            Edit: Sorry, I just reread your comment and realized you asked me to try partimage. That’s what we actually have selected. That’s what the default was set to.

            george1421G 1 Reply Last reply Reply Quote 0
            • george1421G
              george1421 Moderator @drifter666
              last edited by

              @drifter666 said in No source file passed (writeImage):

              Yeah, we did try that and the issue is the same. Did you want me to capture a screen shot of this as well with PartClone selected?

              Just for clarity I’m talking about Partimage the name appear similar.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

              D 1 Reply Last reply Reply Quote 0
              • D
                drifter666 @george1421
                last edited by

                @george1421 Yeah, I just edited my response for clarity as well. Sorry about that.

                george1421G 1 Reply Last reply Reply Quote 0
                • george1421G
                  george1421 Moderator @drifter666
                  last edited by george1421

                  @drifter666 I think we are at the point we need the developers to look at this. There was quite a bit of work done between 1.3.4 and 1.3.5 around single disk resizable speed. Something may have got lost in translation.

                  I know I asked this before, but its still bugging me. You captured these images as “single disk resizeable” in FOG 1.2.0? From what I remember that did not work well at all in FOG 1.2.0. But either way we’ll need the developers to dig into the code. We should have enough screen shots of your system.

                  For your students image, you might want to post the output of cat /images/Students/d1.original.partitions that is the disc geometry.

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                  1 Reply Last reply Reply Quote 0
                  • D
                    drifter666
                    last edited by

                    I hear you @george1421 . The resize didn’t work for us for awhile but the technician here that does the image uploads noticed that it was working so he started using it.

                    If we regather and redeploy the image with single disk resize with version 1.3.5, it works fine.

                    Here is the output from your cmd.

                    root@FoG-Deb:/# cat /images/Student/d1.original.partitions
                    # partition table of /dev/sda
                    unit: sectors
                    
                    /dev/sda1 : start=     2048, size=   716800, Id= 7, bootable
                    /dev/sda2 : start=   718848, size=972513280, Id= 7
                    /dev/sda3 : start=        0, size=        0, Id= 0
                    /dev/sda4 : start=        0, size=        0, Id= 0
                    root@FoG-Deb:/# 
                    
                    1 Reply Last reply Reply Quote 0
                    • D
                      drifter666
                      last edited by

                      No updates or anything on this? At this point we are regathering our images to deploy them which kinda sucks. But if that’s the solution, we’ll just keep trucking.

                      george1421G 1 Reply Last reply Reply Quote 0
                      • george1421G
                        george1421 Moderator @drifter666
                        last edited by

                        @drifter666 I had a discussion with one of the developers over this issue late last week, and he recommended updating to 1.4.0-RC1 to fix the disk alignment issue you may be seeing.

                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                        1 Reply Last reply Reply Quote 0
                        • D
                          drifter666
                          last edited by

                          Cool! I’ll give that a shot and report back once I test it.

                          george1421G 1 Reply Last reply Reply Quote 0
                          • george1421G
                            george1421 Moderator @drifter666
                            last edited by

                            @drifter666 Please update to 1.4.0-RC3 before you test.

                            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                            1 Reply Last reply Reply Quote 0
                            • A
                              alserran
                              last edited by

                              It works with 1.4.0-RC3!!! But… doesn’t resize disk after deploy.

                              george1421G 1 Reply Last reply Reply Quote 0
                              • george1421G
                                george1421 Moderator @alserran
                                last edited by

                                @alserran Any error messages?

                                Was the image captured as single disk resizeable?

                                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                1 Reply Last reply Reply Quote 0
                                • A
                                  alserran
                                  last edited by

                                  Yes, it’s the same as first screenshot in this post…

                                  1 Reply Last reply Reply Quote 0
                                  • A
                                    allens
                                    last edited by

                                    Any chance this has been resolved? I’m having the exact same issue.

                                    george1421G 1 Reply Last reply Reply Quote 0
                                    • george1421G
                                      george1421 Moderator @allens
                                      last edited by

                                      @allens What version of FOG are you running?

                                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                      1 Reply Last reply Reply Quote 0
                                      • Tom ElliottT
                                        Tom Elliott
                                        last edited by

                                        Is this still happening on RC-6?

                                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                        1 Reply Last reply Reply Quote 0
                                        • R
                                          rmmadden
                                          last edited by

                                          Hi All,

                                          Just upgraded from 1.2.0 to 1.3.5 and am seeing the same symptoms as the OP. It looks like we may be waiting to see if this is solved in 1.4 at the moment. Let me know if there is anything I can provide to help troubleshoot this.

                                          Server: Centos 6
                                          Fog: 1.3.5

                                          george1421G 1 Reply Last reply Reply Quote 0
                                          • george1421G
                                            george1421 Moderator @rmmadden
                                            last edited by george1421

                                            @rmmadden That issue should have been addressed in 1.4.0RC1. The developers are still a few weeks away from releasing 1.4.0 stable, just be aware.

                                            You might want to upgrade to the 1.4.0RC6 release to ensure that your issue has been resolved before 1.4.0 is officially launched.

                                            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                                            R 1 Reply Last reply Reply Quote 1
                                            • 1
                                            • 2
                                            • 2 / 2
                                            • First post
                                              Last post

                                            231

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project