Solus Emergency mode

DrGouh

Hello there !

I'm a beginner with Solus and I tried to fix my problem by myself but I need smarter people help.

I was just downloading movies, when suddenly I lost my internet connection, so I decided to reboot my computer but now I can't access Solus as I'm locked in emergency mode pic).)

I don't know what to do I've tried different things (fsck, mount..) on Solus live, without success... I don't know how to send the journalctl thing, if anyone can guide me. I just know that there are two red lines:

fsck failed with exit status 4            
Failed to start File System Check on dev/disk/by-uuid/2ccc5161-c3ae-4bd9-8a07-e7a4ec8ad2fa

If I can give any useful information, simply tell me, I'll do it.
I don't know if it's linked but my computer is an old HP Pavilion dm4 which previously ran W10, I've had some issues with the hard drive before but nothing like that.

I saw that people are talking about emergency mode on the forum but I cannot access those old threads since the forum update (and since I'm a beginner, I'm a bit lost without the forum..).

Any help would be much appreciated !
Thanks in advance

brent

I would sudo eopkg up---fix the package you broke or accidentally damaged. Or other eopkg rebuid options in --help. The mods have a grep command for the rebuild but long lost by me.

I have had the message in your picture before and I was lucky enough to fix with package upgrade. But every case is different.
Good luck. I hope you get some more advice.

DrGouh

Thanks a lot for your help, I've tried a little bit of everything without success... The good point is that I can access my hard drive through Live Solus and get back all my data.

Will a clean install of Solus solve the problem? Because if that's the case, I just have to save my data on my external drive and reinstall Solus.

Thanks again brent and moriel5

moriel5

That had happened to me once, due to faulty RAM.
I forget the exact commands, but I'll check on the Phabricator, where I had posted about this back then.
Edit: It turns out that I had posted something unrelated, and when this had happened to me, I had done something else, which I do not currently remember.
Hopefully this bug report/thread on the Phabricator should help.

moriel5

DrGouh Unless you have faulty hardware, OS reinstallation should resolve the issue.

Can you please verify that the RAM is functioning properly though? You can boot MemTest+ from a disk, or boot it from one of the Ubuntu disks to check this.
RAM testing should be done one DIMM (stick) at a time.

gohlip

fsck the partition.
partition must be unmounted, so it has to be done from outside the OS, like from livecd or another OS.

moriel5

gohlip Thanks, I had completely forgotten about how fsck works, since I had only used it twice in my life.

DrGouh

My issue is now resolved, fsck didn't work because I was doing it on the wrong partition (yeah I know sorry for being dumb). It finally worked after doing

fsck /etc/sdm-2 (I thought it was sda...)

I didn't run a memtest because I didn't manage to find the option to do it despite the tutorials on the web.

Thanks again a lot everybody for the help!
EDIT: How do I put [SOLVED] in the title please?

kyrios

@DrGouh You can't but we'll do it for you 🙂

Yarrboat

My friend had this issue yesterday after an update +restart, FYI you can fsck the partition from the emergency mode so you don't need to use a liveUSB or anything. Looking at the report log it seems that systemd tried to mount his windows partition on /dev/sda2 which of course failed, I mounted and looked into his root partition on /dev/sdb2 and his /etc/fstab was empty which was odd. Unmounting and just running /# fsck /dev/sdb2 and hitting Y for the fixes and exiting emergency mode worked and fstab was populated after logging in when I checked again.

To get the command options just use /# fsck --help

tortuga_Bob

Hello! I am new to the Forum and fairly new to Solus. I am encountering a similar problem to the others that have posted in this thread. I have tried to enter some of the commands that have been suggested but nothing really does anything. The computer was working fine earlier in the day and when I tried to login again it became unresponsive and rebooting put me into emergency mode. The following screen shot was obtained by using the journalctl -r command.

Justin

tortuga_Bob I would run through the Boot Rescue guide and try to Rollback.