ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)

    Scheduled Pinned Locked Moved IT Discussion
    centos 7.2
    51 Posts 5 Posters 19.5k Views
    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.
    • scottalanmillerS
      scottalanmiller
      last edited by

      THis is hardware RAID, but lsblk is showing individual drives coming from the controller. So it looks like the controller has potentially failed?

      wirestyle22W stacksofplatesS 2 Replies Last reply Reply Quote 0
      • wirestyle22W
        wirestyle22 @scottalanmiller
        last edited by

        @scottalanmiller Other VM's are fine

        1 Reply Last reply Reply Quote 0
        • stacksofplatesS
          stacksofplates @scottalanmiller
          last edited by

          @scottalanmiller said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

          THis is hardware RAID, but lsblk is showing individual drives coming from the controller. So it looks like the controller has potentially failed?

          They're VHDs

          1 Reply Last reply Reply Quote 1
          • scottalanmillerS
            scottalanmiller
            last edited by

            How did this corrupt then, no battery?

            wirestyle22W 1 Reply Last reply Reply Quote 0
            • stacksofplatesS
              stacksofplates
              last edited by stacksofplates

              I'm also assuming this VM is running on a XenServer since the disks are xvda and xvdb.

              wirestyle22W 1 Reply Last reply Reply Quote 1
              • wirestyle22W
                wirestyle22 @scottalanmiller
                last edited by

                @scottalanmiller Prob not. I'm not sure though

                1 Reply Last reply Reply Quote 0
                • wirestyle22W
                  wirestyle22 @stacksofplates
                  last edited by

                  @stacksofplates said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                  I'm also assuming this is running on a XenServer since the disks are xvda and xvdb.

                  Correct

                  1 Reply Last reply Reply Quote 0
                  • stacksofplatesS
                    stacksofplates
                    last edited by stacksofplates

                    Ya while it's not a great idea IMO to put all of the data on the root file system (and span two disks like that), you can just create a home directory for your user and continue on. Just remove the mount line in fstab.

                    scottalanmillerS 1 Reply Last reply Reply Quote 0
                    • scottalanmillerS
                      scottalanmiller @stacksofplates
                      last edited by

                      @stacksofplates said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                      Ya while it's not a great idea IMO to put all of the data on the root file system (and span two disks like that), you can just create a home directory for your user and continue on. Just remove the mount line in fstab.

                      Aren't we looking at the raw devices,before LVM? How are the underlying devices showing up as 3.9TB when they are limited to 2TB. Those are the "physical" partitions on the VHDs.

                      stacksofplatesS wirestyle22W 2 Replies Last reply Reply Quote 0
                      • stacksofplatesS
                        stacksofplates @scottalanmiller
                        last edited by

                        @scottalanmiller said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                        @stacksofplates said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                        Ya while it's not a great idea IMO to put all of the data on the root file system (and span two disks like that), you can just create a home directory for your user and continue on. Just remove the mount line in fstab.

                        Aren't we looking at the raw devices,before LVM? How are the underlying devices showing up as 3.9TB when they are limited to 2TB. Those are the "physical" partitions on the VHDs.

                        It looks like a volume group spanned over two VHDs. XebServer has a 2TB limit for disks so he spanned the volume over two disks to get 4TB.

                        scottalanmillerS 1 Reply Last reply Reply Quote 0
                        • wirestyle22W
                          wirestyle22 @scottalanmiller
                          last edited by wirestyle22

                          @scottalanmiller Isn't this a combination of xvda2 and xvdb?

                          scottalanmillerS 1 Reply Last reply Reply Quote 0
                          • scottalanmillerS
                            scottalanmiller @stacksofplates
                            last edited by

                            @stacksofplates said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                            @scottalanmiller said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                            @stacksofplates said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                            Ya while it's not a great idea IMO to put all of the data on the root file system (and span two disks like that), you can just create a home directory for your user and continue on. Just remove the mount line in fstab.

                            Aren't we looking at the raw devices,before LVM? How are the underlying devices showing up as 3.9TB when they are limited to 2TB. Those are the "physical" partitions on the VHDs.

                            It looks like a volume group spanned over two VHDs. XebServer has a 2TB limit for disks so he spanned the volume over two disks to get 4TB.

                            Yeah, I get that. But shouldn't lsblk show us the underlying devices before the span?

                            stacksofplatesS 1 Reply Last reply Reply Quote 0
                            • scottalanmillerS
                              scottalanmiller @wirestyle22
                              last edited by

                              @wirestyle22 said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                              @scottalanmiller Isn't this a combination of xvda1 and xvdb?

                              Is lsblk taking the LVM data and applying it from the upper level?

                              1 Reply Last reply Reply Quote 0
                              • stacksofplatesS
                                stacksofplates @scottalanmiller
                                last edited by stacksofplates

                                @scottalanmiller said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                                @stacksofplates said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                                @scottalanmiller said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                                @stacksofplates said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                                Ya while it's not a great idea IMO to put all of the data on the root file system (and span two disks like that), you can just create a home directory for your user and continue on. Just remove the mount line in fstab.

                                Aren't we looking at the raw devices,before LVM? How are the underlying devices showing up as 3.9TB when they are limited to 2TB. Those are the "physical" partitions on the VHDs.

                                It looks like a volume group spanned over two VHDs. XebServer has a 2TB limit for disks so he spanned the volume over two disks to get 4TB.

                                Yeah, I get that. But shouldn't lsblk show us the underlying devices before the span?

                                It does. But you can see /dev/mapper/plex-root is where 3.9TB is. xvda and xvdb only have 2 TB.

                                scottalanmillerS 1 Reply Last reply Reply Quote 0
                                • scottalanmillerS
                                  scottalanmiller @stacksofplates
                                  last edited by

                                  @stacksofplates said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                                  @scottalanmiller said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                                  @stacksofplates said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                                  @scottalanmiller said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                                  @stacksofplates said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                                  Ya while it's not a great idea IMO to put all of the data on the root file system (and span two disks like that), you can just create a home directory for your user and continue on. Just remove the mount line in fstab.

                                  Aren't we looking at the raw devices,before LVM? How are the underlying devices showing up as 3.9TB when they are limited to 2TB. Those are the "physical" partitions on the VHDs.

                                  It looks like a volume group spanned over two VHDs. XebServer has a 2TB limit for disks so he spanned the volume over two disks to get 4TB.

                                  Yeah, I get that. But shouldn't lsblk show us the underlying devices before the span?

                                  It does. But you can see /dev/mapper/plex-root is where 3.9TB is. xvda and xvdb only have 2 TB.

                                  Gotcha, okay.

                                  1 Reply Last reply Reply Quote 1
                                  • wirestyle22W
                                    wirestyle22
                                    last edited by wirestyle22

                                    So now the question is how to properly set up a home directory from scratch. Doesn't seem like I can just mkdir it

                                    scottalanmillerS stacksofplatesS 2 Replies Last reply Reply Quote 0
                                    • scottalanmillerS
                                      scottalanmiller @wirestyle22
                                      last edited by

                                      @wirestyle22 said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                                      So now the question is how to properly set up a home directory from scratch. Doesn't seem like I can just mkdir it

                                      Pretty much yo ucan. Just remove the fstab entry for it and mkdir /home

                                      1 Reply Last reply Reply Quote 1
                                      • stacksofplatesS
                                        stacksofplates @wirestyle22
                                        last edited by stacksofplates

                                        @wirestyle22 said in Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1):

                                        So now the question is how to properly set up a home directory from scratch

                                        You might just be able to log in as your normal user and it will do it automatically. If not just create a directory with your username under /home and chown it to your ID. Don't forget SELinux labels.

                                        1 Reply Last reply Reply Quote 0
                                        • wirestyle22W
                                          wirestyle22
                                          last edited by wirestyle22

                                          Interesting. if I mkdir /home it says file exists. I cd into it and there is nothing there.

                                          1 Reply Last reply Reply Quote 0
                                          • stacksofplatesS
                                            stacksofplates
                                            last edited by

                                            It should. That's where it mounted the volume before. It can't mount it there if there isn't a mount point.

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