Ad
mason
asked Nov 20 2018
Answer
0
The reason for this error was an entry in /etc/fstab that pointed to partition UUID that was no longer exists.
The solution was to remove the unwanted fstab entry or uncommand the fstab entry.
for example,
#vim /etc/fstab
Remove the entry of the device that no longer exists
linuxhelp
Apr 04 2025
While System boots up, you may see the errors messages gets printing up ! From there you can find the partion with error
sudheerp494
Apr 04 2025
I have same issue. But tried it with # before UUID in /etc/fstab NO LUCK. <br />
How do i know which partition is unwanted in fstab
linuxhelp
Apr 04 2025
Hi caitlyn ! usually the fstab entries will be made manually by the user, and it must definitely mounted in a Directory from / so obviusly you should know which path does not exist.
Stoltz
Apr 04 2025
How do I know which one that is? Or how can you tell?
gokulravichandran2
asked Nov 23 2018
Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
when starting up the Centos 7machine I am receiving this error
Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)how to resolve this issue???