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

    Failed to Set Disk GUID (sgdisk -U) (restoreUUIDinformation)

    Scheduled Pinned Locked Moved Solved
    Bug Reports
    5
    50
    12.5k
    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 @Sebastian Roth
      last edited by

      @Sebastian-Roth well if the workaround is to update the ram disk size, it’s not too hard a thing to do. We can push out a patch to fix it directly, but seeing as this value is already easy to change what about simply documenting the error and the change for the resolution?

      As fog keeps making progress I don’t think asking people to make this change is too difficult. And as for 1.5.7, just add in a patch to check if the ram disk size is too small in the bootmenu, and if so update the value directly.

      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
      • S
        Sebastian Roth Moderator
        last edited by Sebastian Roth

        @Tom-Elliott Sure we’ll fix that in 1.5.7 but I’d like to see 1.5.6 not going on ground just a few days after we released it. Therefor I am trying to get to a solution where people can just use 1.5.6 without having to fix anything manually. Just tested and seems we are fine with the currently uploaded files. All good I hope.

        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
        • A
          austinjt01 @Sebastian Roth
          last edited by

          @Sebastian-Roth So I re-ran the FOG installer. After that I tried capturing an image which appeared to work okay, but now i’m getting the same error upon trying to deploy that captured image.

          It goes through the whole download process and says “A warning has been detected: Failed to set disk guid (sgdisk -U) (restoreUUIDInformation)”

          Sits on that screen for about 60 secs and then gets stuck at “Changing hostname…” again

          Shall I try manually downloading the files ? Maybe the re run of the FOG installer didn’t cut it?

          Thanks.

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

            @austinjt01 Please run the following commands on your FOG server and post output here:

            md5sum /var/www/html/fog/service/ipxe/init*
            cat /images/<IMAGENAME>/d1.partitions
            

            Make sure you put in the name of your image instead of <IMAGENAME>!

            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

            A 1 Reply Last reply Reply Quote 0
            • A
              austinjt01 @Sebastian Roth
              last edited by austinjt01

              @Sebastian-Roth 363628ff-95c8-4fb7-adf2-61762cb042a8-image.png

              I have our images stored on our media server, if I path over to /mnt/media-images/<IMAGENAME>/d1.partitions

              This is what’s in the file

              42e29df3-dbf8-4e04-82ba-541f6a62b685-image.png

              UPDATE:
              I manually installed the updates and got this as the output
              114ebb98-fd51-4eb7-a78f-1303a3f701b8-image.png

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

                @austinjt01 said in Failed to Set Disk GUID (sgdisk -U) (restoreUUIDinformation):

                So I re-ran the FOG installer.

                The md5 sums we see in the picture are definitely not the most current ones. Which installer version did you run? Where did you download FOG? I mean from github or downloaded an archive?

                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

                A 1 Reply Last reply Reply Quote 0
                • A
                  austinjt01 @Sebastian Roth
                  last edited by

                  @Sebastian-Roth I ran the updates and got the same output that you have below.

                  Seem to still have trouble with capture / deploy though. Keeps getting hung up on “Changing hostname…”

                  I manually installed the updates and got this as the output
                  35c99458-d092-4c10-8f02-69f11f609ea0-image.png

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

                    @austinjt01 said in Failed to Set Disk GUID (sgdisk -U) (restoreUUIDinformation):

                    Seem to still have trouble with capture / deploy though. Keeps getting hung up on “Changing hostname…”

                    What do you mean by “hung up”?? Please take a picture of the screen and post 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

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      austinjt01 @Sebastian Roth
                      last edited by

                      @Sebastian-Roth IMG_0241.jpg

                      It will just sit here and not do anything.

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

                        @austinjt01 This is the exact same picture you posted days ago. I can hardly believe you see the exact same screen again as we have changed the size of the init files and I would expect the “No space left in device” error to have vanished.

                        Please take a new picture of what exactly you have on screen when it hangs!

                        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

                        A 1 Reply Last reply Reply Quote 0
                        • A
                          austinjt01 @Sebastian Roth
                          last edited by austinjt01

                          @Sebastian-Roth Yeah you are right, I grabbed a different laptop to test on just now and everything is fine. Thanks for your help, I really appreciate it and your support.

                          Edit: The capture worked this time, but the deploy gives this error.

                          IMG_0270.jpg
                          Picture was taken just now

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

                            @george1421 @Junkhacker Is anyone able to to reproduce this issue?!?!?

                            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

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

                              @Sebastian-Roth said in Failed to Set Disk GUID (sgdisk -U) (restoreUUIDinformation):

                              @george1421 @Junkhacker Is anyone able to to reproduce this issue?!?!?

                              I can not duplicate the issue here, but that just means the circumstances (environment) is different.

                              I did see something that raised a red flag.

                              I have our images stored on our media server, if I path over to /mnt/media-images/<IMAGENAME>/d1.partitions

                              How are you doing this? You are not supposed to be able to reshare an nfs mounted share (technically you can, but fog is not configured to support it). You can’t do that in ms windows either.

                              Images are captured to /images/dev/<mac_address> directory (nfs share) and then “moved” to the /images/<image_name> directory using the ftp server built into the fog server. At the very least if /images/dev is on the fog server and /mnt/media-images/<image_name> is on the NFS share the ftp server will have to copy the entire image to the remote nfs server instead of just moving the file pointers as it would if the /images/dev and /images are on the same disk. If you want to store your images on an NFS nas but have the fog server manage the process there is another (unsupported) configuration you can use instead of resharing an nfs mount.

                              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!

                              A 1 Reply Last reply Reply Quote 0
                              • A
                                austinjt01 @george1421
                                last edited by austinjt01

                                @george1421 Our storage node that we have setup is on ‘media’
                                ‘/mnt/media-images’ is just an admin shortcut for us to navigate easier we aren’t using that for uploading or downloading. Upon capture the storage location on the FOG screen is listed as: ip address:/mnt/pool/it/images/dev/ Is it a possibility that the image is being captured into DEV but not being copied out of dev during deploy?

                                IMG_0274.jpg

                                The other thing I have to add to this, I have 7 different brands of laptops. All of the other brands work (Capture and Deploy) just fine. These new laptops we just got (30, Lenovo P52s) they are at least two years newer than any other device in our inventory. Do you think they need to be set up on UEFI instead of Legacy boot?? The only drastic difference between these machines is that they all have SSD’s which I didn’t think would make a difference?

                                Thanks

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

                                  @austinjt01 is 10.228.255.10 your fog server?

                                  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!

                                  A 1 Reply Last reply Reply Quote 0
                                  • A
                                    austinjt01 @george1421
                                    last edited by

                                    @george1421 no, that’s the IP of our file server. .3 is the FOG server IP

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

                                      @austinjt01 So your file server is a linux server with the fog code installed? Or is it a linux (like) nas device?

                                      Do you have this working using the non-supported configuration where you create a second storage node and then set that node as the master? I’m still trying to understand your landscape.

                                      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!

                                      A 1 Reply Last reply Reply Quote 0
                                      • A
                                        austinjt01 @george1421
                                        last edited by

                                        @george1421
                                        Our file server based on FreeNAS.

                                        I know that this isn’t supported by FOG, I guess I am just curious as to why everything will still work except for our new laptops.

                                        ‘fog’ is our master node, points to /mnt/media-images (backed by NFS) ‘media’ is an additional node, points to /mnt/pool/it/images (direct NAS). We set it up this way because the images are stored on a server with about 12 TB free currently.

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

                                          @austinjt01 Well… I don’t have an answer why it works on everything except this laptop model.

                                          On your freenas box you then will need the ftp service running with a user ID and password you listed in the storage node definition configured to allow the fog client to move the files. If the ftp service isn’t configured correctly your images will stay in /images/dev/<mac_address> (you will need to translate that path into your environment) and not be renamed to /images/<image_name>.

                                          While its a little off-point and also not supported, here is a tutorial to make a synology NAS function as a FOG Storage Node: https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node

                                          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
                                          • S
                                            Sebastian Roth Moderator
                                            last edited by

                                            @george1421 @Tom-Elliott I am still wondering if the “No space left on device” was caused by another error and it’s not actually the rootfs being too small. I need to double check when booted into FOS later on but I think we don’t actually have a space issue. Should we still increase root fs size?

                                            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

                                            Tom ElliottT 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 2 / 3
                                            • First post
                                              Last post

                                            153

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project