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

      My best guess is that it fails to mount the partition correctly for whatever reason.

      Only thing I can see (but shouldn’t cause issues afaik) is that you have mdraid=true in the kernel parameters twice.

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

        @Quazz Nope. It’s only in there once. Unless there’s somewhere else it would have been entered as well that I don’t know about.

        0_1537881795497_hostkernelargs.JPG

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

          @Zerpie It could also be under global settings, but I don’t think it really has anything to do with it failing.

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

            @george1421 said in Permission denied when trying to capture Intel RAID1 image:

            Did you schedule a boot time disk check like the message indicated?

            I just tried that and then attempted another capture task and it still failed with the same Permission denied error as my original post.

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

              @Zerpie
              I know it doesn’t directly address your issue; forgive me.

              Hardware raid cards are pretty darn cheap (used server pulls etc). Have you ever tried to rebuild one of those fakie raids? I’ve seen really poor results when it actually comes down to rebuilding a mirror, and the performance of general use is garbage.

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

                @Zerpie I have a feeling that you need to look into the details of this RAID array to get a better picture of what is going wrong. So after putting the machine into the original state start a debug capture task and when you get to the console run the following commands:

                mdadm --examine /dev/sd*
                cat /proc/mdstat
                

                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 I haven’t been able to get back to this issue in the past week or so, but I went ahead and tried this today. I’ve attached pictures of the results.

                  0_1538503404816_pic1.jpg

                  0_1538503411025_pic2.jpg

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

                    @Zerpie Ahh, I see, md126 is read-only which is probably causing the issue… Please try the following commands in another debug session:

                    mdadm --stop /dev/md126
                    mdadm --assemble --scan
                    cat /proc/mdstat
                    

                    Yes, yes, imsm raids tend to do that

                    ref: https://bbs.archlinux.org/viewtopic.php?id=137058

                    So far I am not exactly sure if there is something we can do about this in the startup scripts. Let’s see if you can fix it manually and take it from there.

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

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

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

                        @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

                          @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

                          george1421G Z 2 Replies Last reply Reply Quote 0
                          • george1421G
                            george1421 Moderator @Zerpie
                            last edited by

                            @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 Reply Quote 0
                            • Z
                              Zerpie @george1421
                              last edited by

                              @george1421 It doesn’t recognize the command mdstat.

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

                                            188

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project