[Solved]Error on boot, Emergency mode available only

zabrielza · 2015-08-07 05:28:23

Hello,

Yesterday I tried to configure Slim as my display manager. I changed only /etc/slim.conf and .xinitrc files. So, in the /etc/slim file I changed my username, and hashed out the line sessiondir

# Set directory that contains the xsessions.
# slim reads xsesion from this directory, and be able to select.
# sessiondir            /usr/share/xsessions/

.xinitrc file before changing it, contained this line

exec startfluxbox

to start my fluxbox session and worked perfectly

after changing it I placed this line

[]
exec $1
[/]

without knowing what it is :-$ So, After that I rebooted and then I am getting

try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):

Also I am getting this Error

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

journalctl -p 3 -b gives

fsck failed with error code 4
Failed to start File System Check on /dev/disk/by-uuid/2f5b7f54-cad1-4f7d-8290-2e50ae9f7382
emergency.service: Failed at step EXEC spawning /bin/plymouth: No such file or directory
fsck failed with error code 4.

What is going on? I have two Drives one Hard Drive and one SSD. On the SSD I have / partition mainly and on the Hard Drive I have data etc. Is my SSD dead or something? How can I fix this prolem?

Thanks in advance

Last edited by zabrielza (2015-08-07 12:29:18)

esdaniel · 2015-08-07 07:33:53

Seems you've had some bad luck and some data on the disk got corrupted. This can happen if cached data in memory hasn't been flushed to a disk and written before you turn off the computer.

The fsck error pertains to "4 - File system errors left uncorrected".

In maintenance mode, you should run fsck on the *unmounted* volume throwing the error:
# fsck -AR -y

Would be wise to read up on fsck before you actually run that though so you know what it's doing, in the example above it checks all filesystems except root filesystem and attempts to fix any errors discovered.

If all is well and good then you can reboot and things should be back to normal.

zabrielza · 2015-08-07 12:28:18

esdaniel wrote:

Seems you've had some bad luck and some data on the disk got corrupted. This can happen if cached data in memory hasn't been flushed to a disk and written before you turn off the computer.
The fsck error pertains to "4 - File system errors left uncorrected".
In maintenance mode, you should run fsck on the *unmounted* volume throwing the error:
# fsck -AR -y
Would be wise to read up on fsck before you actually run that though so you know what it's doing, in the example above it checks all filesystems except root filesystem and attempts to fix any errors discovered.
If all is well and good then you can reboot and things should be back to normal.

Thanks for the reply! It worked. I am marking this as solved. Last thing I did actually was closing the computer from the power button. Was bad luck the reason or that actual last action? Also I am not sure which is the safest way to shutdown the computer. Is systemctl poweroff safe or not? I know that this is irrelevant to the topic but if you can give any direction it would be great.

Anyway thanks for the reply.

jasonwryan · 2015-08-07 18:46:09

Always use systemctl poweroff if you want the system to be shutdown safely.

Arch Linux

#1 2015-08-07 05:28:23

[Solved]Error on boot, Emergency mode available only

#2 2015-08-07 07:33:53

Re: [Solved]Error on boot, Emergency mode available only

#3 2015-08-07 12:28:18

Re: [Solved]Error on boot, Emergency mode available only

#4 2015-08-07 18:46:09

Re: [Solved]Error on boot, Emergency mode available only

Board footer