Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
-
-
Well that's why plex-home failed, it doesn't exist. What vhd was it on?
-
If you don't need the data that was in it you could just create another volume for the home directory and mount it.
-
@stacksofplates Home was just auto generated during installation. I wasn't using afaik
-
You could just create the home directory on the root partition. You would have to copy any keys back. Then just remove the line in fstab for that volume.
-
THis is hardware RAID, but lsblk is showing individual drives coming from the controller. So it looks like the controller has potentially failed?
-
@scottalanmiller Other VM's are fine
-
@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
-
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.
