Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
-
How did this corrupt then, no battery?
-
I'm also assuming this VM is running on a XenServer since the disks are xvda and xvdb.
-
@scottalanmiller Prob not. I'm not sure though
-
@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
-
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.
-
@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.
-
@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.
-
@scottalanmiller Isn't this a combination of xvda2 and xvdb?
-
@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?
-
@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?
-
@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.
-
@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.
-
So now the question is how to properly set up a home directory from scratch. Doesn't seem like I can just
mkdirit -
@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
mkdiritPretty much yo ucan. Just remove the fstab entry for it and mkdir /home
-
@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.
-
Interesting. if I
mkdir /homeit says file exists. Icdinto it and there is nothing there. -
It should. That's where it mounted the volume before. It can't mount it there if there isn't a mount point.
-
Right but I can't unmount what isn't mounted and I can't delete it if it's in use
-
Also I just saw the tag. How is this still on 7.2? It should have upgraded to 7.3 in December or so.
-
@stacksofplates I've been reading a lot
