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

    Permission denied when trying to capture Intel RAID1 image

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    6
    41
    8.7k
    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

      @Zerpie Try mdadm --detail /dev/md126

      See chat bubble in the right upper corner…

      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

      Z 1 Reply Last reply Reply Quote 0
      • Z
        Zerpie @Sebastian Roth
        last edited by

        @Sebastian-Roth 0_1538513231832_pic4.jpg

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

          With the raid array configured for raid-1 (Mirror) I am getting the same results as the OP. I can’t seem to switch it from raid-only to read write to start the resync process. I’m still working on the issue as time permits today. But there IS something up here, I feel its hardware/array related. It should work because all of the bits are aligned right as soon as I can get it out of read-only mode.

          0_1538573176989_raid1-proc.png

          0_1538573310811_mdadm-detail.png

          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!

          george1421G 1 Reply Last reply Reply Quote 0
          • Z
            Zerpie @Zerpie
            last edited by

            This post is deleted!
            1 Reply Last reply Reply Quote 0
            • george1421G
              george1421 Moderator @george1421
              last edited by george1421

              @george1421 OK I have a track on how to make it work. I just need to see how we can get the fix into the official FOS release.

              0_1538587716521_mdraid-syncing.png

              We can patch it, but it needs to be fixed right.

              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!

              Z 1 Reply Last reply Reply Quote 0
              • Z
                Zerpie @george1421
                last edited by

                @george1421 That’s good to know. Does that mean I’ll have to wait for a future update for this to work with my equipment?

                Thanks for all the work you guys have put into this. I really appreciate how much this community is willing to help.

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

                  @Zerpie Sebastian was working through why the program was missing from the inits. I think he was planning on patching the inits for now and then going back to the buildroot project with the error why its not including the file when its selected. FOG uses Buildroot to create the customized linux engine that runs on the target computers.
                  It should be just a day or two before we have a workable solution for you. Its not something you did or didn’t do, its related to mdadm and the missing monitoring application for raid 1 arrays.

                  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

                    @Zerpie @george1421 Build is done. Please find new test binaries here 64 bit and 32 bit.

                    Download and put in /var/www/fog/service/ipxe on your FOG server. Rename to match the original names - do not overwrite but also rename the original init’s I would say just in case.

                    Please test and let us know. Caputre, deploy… working?

                    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 R 3 Replies Last reply Reply Quote 1
                    • george1421G
                      george1421 Moderator @Sebastian Roth
                      last edited by george1421

                      @Sebastian-Roth Looks like you have it worked out.

                      The only thing I did was install the updated inits and then pxe boot into a debug console. It worked right out of the box. Well done!

                      I’m going to start a normal mode deploy to ensure it can push the image out to the disk, but I’m sure it will work as it did with the raid0 setup.

                      0_1538653432542_mdm_initz.png

                      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
                      • george1421G
                        george1421 Moderator @Sebastian Roth
                        last edited by george1421

                        @Sebastian-Roth Deployment was successful.

                        I did notice there was an error message I have not seen before, but I don’t think its related to intel raid.

                        db_root: can not open: /etc/target
                        

                        Everything works OK so I don’t know maybe if its a warning we can ignore.

                        Also FWIW I’m also running on the latest FOS kernels (4.18.11)

                        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!

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

                          @george1421 I’ve seen that on the latest kernels on normal installs too, doesn’t seem to hurt anything afaik.

                          1 Reply Last reply Reply Quote 1
                          • Z
                            Zerpie
                            last edited by

                            My first attempt to capture the image after downloading the new init files I got an error.

                            Partclone fail, please check /var/log/partclone.log !
                            
                            Failed to complete capture (savePartition)
                               Args Passed: /dev/md126p1 1 /images/00270e3b9d1e all
                                Exit code: 1
                                Maybe check the fog server to ensure disk space is good to go?
                            

                            After the host rebooted it started a CHKDSK and I’m waiting for it to finish now.
                            I may need to restore the original image again just to get a fresh start. I’ve also checked the image storage and there’s plenty of space available. I’ll update once I’ve gotten a few good tests. Thanks!

                            Z 1 Reply Last reply Reply Quote 0
                            • Z
                              Zerpie @Zerpie
                              last edited by

                              I’m not sure what that error was caused by the first time around, but I was able to successfully capture the image on my second pass. Now I’m deploying the captured image. So far so good. No errors yet. Fingers crossed…

                              1 Reply Last reply Reply Quote 0
                              • Z
                                Zerpie
                                last edited by

                                YOU GUYS ARE AMAZING!

                                Both the capture and deploy tasks completed successfully! Thank you all so much for your help! Now I can have our staging team start using Fog for our equipment with RAID.

                                Thanks again!

                                1 Reply Last reply Reply Quote 1
                                • R
                                  Robert H @Sebastian Roth
                                  last edited by

                                  @Sebastian-Roth, I have the exact same problem and really would like to download the patched files. But the links are broken. Can I get them somewhere please?

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

                                    @Robert-H As we have the mdmon included in the official inits I deleted the special ones now. Find the official inits here:

                                    https://fogproject.org/inits/init.xz
                                    https://fogproject.org/inits/init_32.xz
                                    

                                    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
                                    • 1
                                    • 2
                                    • 3
                                    • 2 / 3
                                    • First post
                                      Last post

                                    208

                                    Online

                                    12.0k

                                    Users

                                    17.3k

                                    Topics

                                    155.2k

                                    Posts
                                    Copyright © 2012-2024 FOG Project