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

    Imaging not starting

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    5
    22
    6.2k
    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.
    • K
      Killklli @Sebastian Roth
      last edited by

      @Uncle-Frank KIMG0188.jpeg KIMG0187.jpeg

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

        FOG uses its own too to enumerate disks. I am pretty sure we won’t see any surprises here but could you please boot into debug mode again and run fogpartinfo --list-devices?

        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

        K 1 Reply Last reply Reply Quote 0
        • K
          Killklli @Sebastian Roth
          last edited by

          @Uncle-Frank 14437890823151044250807.jpg

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

            Well, there we go I’d say. FOG does not expect this output (“unrecognized disk label”) and is propably not able to parse this. I am away for the weekend and won’t be able to have a closer look at this till Monday.

            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
            • sudburrS
              sudburr
              last edited by

              Have you tried zeroing the disk entirely with DBAN? (Darik’s Boot and Nuke - just use the quick method)

              Is it possible the disk is failing?

              [ Standing in between extinction in the cold and explosive radiating growth ]

              K 1 Reply Last reply Reply Quote 0
              • K
                Killklli @sudburr
                last edited by

                @sudburr I’ve tried DBAN on both. I’d be surprised if both started failing at the exact same time.

                1 Reply Last reply Reply Quote 0
                • sudburrS
                  sudburr
                  last edited by

                  Is that a 512e drive?

                  [ Standing in between extinction in the cold and explosive radiating growth ]

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

                    @Killklli As I am still kind of new in the Dev-Team I don’t know all details of all the tools yet. Looking into the code of fogpartinfo I just saw that it tries to read a partition table from a disk. This fails because your disks don’t have a partition table yet (as we see in the output of fdisk). Quick solution would be to boot up into debug mode and create one partition on both drives e.g. using fdisk.

                    @Developers Is there a reason why fogpartinfo expects a valid partition table when enumerating disks only? I don’t know enough about libparted. Maybe it’s just the way it is?!

                    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

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      Killklli @Sebastian Roth
                      last edited by

                      @Uncle-Frank After doing some heavy messing around with the images I was deploying it seems that for some reason the size of the image was an issue. Even though every computer has the same hard drive and have all been wiped, lowering the image size by 50 more GB (instead of leaving the 10gb padding I had before) fixed it. I used 50GB as a brute test to see it it worked and its strange that it did. Considering the 1tb drive should have taken over no matter what. So I put the 1tb drive in another computer and it imaged fine in there. It seems to just be a strange image size issue.

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

                        Thanks for reporting this. Would be interesting to see if you can nail it down exactly just to see if this could be an issue on other systems too.

                        Does that mean that my assumption about fogpartinfo (it fails when there is no partition table) is wrong??

                        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

                        K 1 Reply Last reply Reply Quote 0
                        • K
                          Killklli @Sebastian Roth
                          last edited by

                          @Uncle-Frank That seems to be the case. The drives themselves had DBAN run on them so it might just assume pre existing partitions. Not default info.

                          1 Reply Last reply Reply Quote 0
                          • JunkhackerJ
                            Junkhacker Developer
                            last edited by

                            is there a reason you’re not using the re-sizeable image type?

                            signature:
                            Junkhacker
                            We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                            K 1 Reply Last reply Reply Quote 0
                            • K
                              Killklli @Junkhacker
                              last edited by

                              @Junkhacker I had multiple hard drives I was trying to image at once and once this issue started popping up I actually did switch to re sizable but it was still having that issue strangely.

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

                              184

                              Online

                              12.0k

                              Users

                              17.3k

                              Topics

                              155.2k

                              Posts
                              Copyright © 2012-2024 FOG Project