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

    Problem capturing image - " no space left on device"?

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    5
    15
    2.1k
    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.
    • S
      Sebastian Roth Moderator
      last edited by

      @Stepa Definitely follow Quazz advice und post the text content of the files from the directory mentioned.

      As well you can try defrag the Windows 😄 partition before capturing.

      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
      • S
        Stepa
        last edited by Stepa

        Oof sorry for taking so incredibly long to answer again, had a nightmare of a workday so far.
        Here’s a screenshot of all the files contents . It’s not much though, hope it’s sufficient.
        000cd615c141.PNG

        edit: Defraging the source pc was the first thing I tried, didn’t work 😕

        Q 1 Reply Last reply Reply Quote 0
        • Q
          Quazz Moderator @Stepa
          last edited by

          @Stepa I could be wrong, but don’t notice anything wrong so far.

          Something goes wrong with ntfsresize or the size it’s ordered to try.

          Perhaps try a debug capture (under advanced tasks of a host) (type enter until you’re at command line after loading and then type in fog and press enter, then press enter for each step)

          Does it say * Possible resize partition size: (size here) a few steps before the error?

          Just want to see if the numbers make sense.

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Sebastian Roth

            @Quazz I see there is something wrong. Where is p1.minimum.partitions. Should be another text file very similar to p1.partitions…

            @Stepa Please do a debug capture as suggested and take pictures of the messages on screen while it goes along. Post those pictures here.

            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
            • S
              Stepa
              last edited by

              Yeah I searched for it… p1.minimum.partitions does not exist it seems…
              I did a debug capture and took some pictures of the things that seemed weird to me.

              3107_03.jpg 3107_02.jpg 3107_01.jpg

              just realised I might have compressed them a little too much this time. Hope its still readable.

              1 Reply Last reply Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by

                @Stepa said in Problem capturing image - " no space left on device"?:

                just realised I might have compressed them a little too much this time. Hope its still readable.

                Compression ratio is not a problem here. The ceiling lights is what makes reading it hard. 😉

                Not shrinking (/dev/nvme0n1p1) fixed size

                That one is ok. It’s the first partition which is detected as fixed and FOG doesn’t resize it.

                I guess I was on the wrong track at first. The p1.minimum.partitions is not being created until FOS was abel to resize the partition…

                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
                • Q
                  Quazz Moderator
                  last edited by

                  @Sebastian-Roth Looking over the shrinkPartition function, it looks like the new size is calculated as the theoretical minimum size as given by ntfsresize + 5% of that size. (for safety and consistency I believe).

                  However, I can foresee situations where the theoretical minimum is small enough that the 5% of “safety space” isn’t enough to accomodate everything. I don’t think this will happen under every circumstance, only when there’s certain kinds of fragmentations that it can’t resolve.

                  Perhaps a preset minimum should be added to ensure a minimum safety boundry (like say 200MB)

                  Ntfsresize man page mentions you don’t require defragmentating the drive prior to using it since it kind of does that itself, but obviously on an SSD that logic doesn’t really make sense anyway!

                  Those are my current thoughts on this, but quite honestly I could be completely wrong.

                  B 1 Reply Last reply Reply Quote 1
                  • S
                    Stepa
                    last edited by

                    So, I kinda had to give up on that device, had to ship it. No idea what excactly was the problem with that.
                    I’ve set up a new devive today (basically same computer), did the same routine of setting it up, installing winodws and so on… With that one, capturing went perfectly fine. So basically my problem is somewhat solved by that… In the way that my company can continue their workflow as usual.

                    I still would like to understand what was going on with that pc… But I can’t do any more test on that one… So I guess we’ll never know…

                    Thank you guys for helping me 🙂

                    1 Reply Last reply Reply Quote 1
                    • E
                      eVal
                      last edited by

                      I have the same issue on diffrent PC’s. Since this topic is closed because the problem was “solved” for the reporter, what info do you guys need from mee?

                      My error screen looks the same as the reporter.

                      I’m on FOG 1.5.5 because I can’t yet upgrade to 1.5.7 due to problems with confilcts between ubuntu, mariadb and fog.

                      1 Reply Last reply Reply Quote 0
                      • S
                        Sebastian Roth Moderator
                        last edited by

                        @eVal said in Problem capturing image - " no space left on device"?:

                        My error screen looks the same as the reporter.

                        I am absolutely sure the information on your screen looks different to the one posted here. Pretty much ever situation is a little different and I may ask you to just open a new topic and if you like add a link to this one as well. In that new topic add all *your information. FOG version, picture with the error on screen, contents of p1.minimum.partitions, p1.minimum.partitions and p1.fixed_size_partitions, the actions you took to try and fix it so far and maybe more

                        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
                        • B
                          benc @Quazz
                          last edited by

                          I’ve never run into this specific problem until today. Generally, issues with resizing can be fixed by increasing the CAPTURERESIZEPCT in Fog Settings > General Settings. I agree with what @Quazz said about certain kinds of fragmentations causing issues with the theoretical minimum partition size. I’ve found that the more used (fragmented?) a drive is, the more likely it is to fail during resize. I was able to get past the no space left on device and numerical result out of range errors by increasing the CAPTURERESIZEPCT to 15%.

                          1 Reply Last reply Reply Quote 0
                          • 1 / 1
                          • First post
                            Last post

                          233

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project