• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • 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.
  • G
    george1421 Moderator @Zerpie
    last edited by Oct 2, 2018, 7:29 PM

    @Zerpie I’m thinking that md127 being set to inactive is also a clue. I just grabbed an old Opltiplex 780 and I’ll spin up a test workstation with the intel raid configured to see if I can duplicate the results here.

    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!

    G 1 Reply Last reply Oct 2, 2018, 7:51 PM Reply Quote 1
    • G
      george1421 Moderator @george1421
      last edited by george1421 Oct 2, 2018, 1:58 PM Oct 2, 2018, 7:51 PM

      @george1421 Well this is what I see when I configured the 780 with 2 250GB disk setup in raid 0 move (stripped)

      0_1538509662011_mdstat.png

      and for lsblk
      0_1538509672956_lsblks.png

      I can say that I have a global kernel parameter of mdraid=true always set. When I watched FOS boot, I saw message about mdadm container assembled and then the container started. I haven’t tried to deploy to this system just yet because I need to edit the host configuration to include /dev/md126, but I’m pretty sure it will image like this. The raid array appears to be in good health.

      [Edit] Yes I can affirm that it imaged correctly Windows OOBE is currently running on that system.

      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 1
      • Z
        Zerpie @Sebastian Roth
        last edited by Oct 2, 2018, 8:05 PM

        @Sebastian-Roth Here’s what I got. This was the same debug session. Not sure if I need to start a new session first.

        0_1538510645422_pic3.jpg

        G Z 2 Replies Last reply Oct 2, 2018, 8:34 PM Reply Quote 0
        • G
          george1421 Moderator @Zerpie
          last edited by Oct 2, 2018, 8:34 PM

          @Zerpie I can see that my test is a bit off point since I “though” you were configuring for a stripped array (raid-0), but looking at your picture below you are using a mirrored array (raid-1). So my screen shots are not really valid other than proving that FOS can support intel raid arrays.

          What does the output of this command look like?
          mdstat --detail /dev/md126

          Hint reboot first since you disassembled the /dev/md126 device with the stop command.

          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 Oct 2, 2018, 8:43 PM Reply Quote 0
          • Z
            Zerpie @george1421
            last edited by Oct 2, 2018, 8:43 PM

            @george1421 It doesn’t recognize the command mdstat.

            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by Oct 2, 2018, 8:44 PM

              @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 Oct 2, 2018, 8:47 PM Reply Quote 0
              • Z
                Zerpie @Sebastian Roth
                last edited by Oct 2, 2018, 8:47 PM

                @Sebastian-Roth 0_1538513231832_pic4.jpg

                1 Reply Last reply Reply Quote 0
                • G
                  george1421 Moderator
                  last edited by george1421 Oct 3, 2018, 7:29 AM Oct 3, 2018, 1:28 PM

                  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!

                  G 1 Reply Last reply Oct 3, 2018, 5:28 PM Reply Quote 0
                  • Z
                    Zerpie @Zerpie
                    last edited by Oct 3, 2018, 3:42 PM

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • G
                      george1421 Moderator @george1421
                      last edited by george1421 Oct 3, 2018, 11:29 AM Oct 3, 2018, 5:28 PM

                      @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 Oct 3, 2018, 8:05 PM Reply Quote 0
                      • Z
                        Zerpie @george1421
                        last edited by Oct 3, 2018, 8:05 PM

                        @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.

                        G 1 Reply Last reply Oct 3, 2018, 8:48 PM Reply Quote 0
                        • G
                          george1421 Moderator @Zerpie
                          last edited by george1421 Oct 3, 2018, 2:49 PM Oct 3, 2018, 8:48 PM

                          @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 Oct 4, 2018, 4:49 AM

                            @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

                            G R 3 Replies Last reply Oct 4, 2018, 11:45 AM Reply Quote 1
                            • G
                              george1421 Moderator @Sebastian Roth
                              last edited by george1421 Oct 4, 2018, 5:46 AM Oct 4, 2018, 11:45 AM

                              @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
                              • G
                                george1421 Moderator @Sebastian Roth
                                last edited by george1421 Oct 4, 2018, 6:07 AM Oct 4, 2018, 11:55 AM

                                @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 Oct 4, 2018, 12:03 PM Reply Quote 0
                                • Q
                                  Quazz Moderator @george1421
                                  last edited by Oct 4, 2018, 12:03 PM

                                  @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 Oct 4, 2018, 6:58 PM

                                    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 Oct 4, 2018, 8:22 PM Reply Quote 0
                                    • Z
                                      Zerpie @Zerpie
                                      last edited by Oct 4, 2018, 8:22 PM

                                      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 Oct 4, 2018, 8:41 PM

                                        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 Oct 20, 2018, 10:20 AM

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

                                          157

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project