Tuxedo entering emergency mode

MetaNorm

Hi everyone! My father's Tuxedo Laptop did run very well for the last three years with Solus. There hasn't been any single issue. But yesterday the Laptop did not boot suddenly. Instead there was the following message displayed:

Generating "/run/initramfs/rdsosreport.txt"

Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USBstick or /boot
after mountung them and attach it to an bug report.

:/#

Can someone tell me what it means? My Dad could boot several times after the last update.
By typing exit the message appears again.

Thanks in advance

kyrios

You should look at the report to get more info as the message says.

MetaNorm

Thank you so much for not ignoring my post.
Well, I already did it but the report is way too long to transfer it here by typewriting. But there are lot of lines highlighted and coloured. A few things that are problematical for my very limited understanding of those reports:

Girtablulu

MetaNorm aaah yea saw that error on my system as well the last couple of times, easy but annoying to fix

get yourself an usb iso and boot it

when inside the live env open the terminal and run lsblk

you find stuff like sda/sdax etc

now run fsck /dev/sdax manually and click through it, best do it for all your drives

reboot now everything should work

brent

what is sda3?
check for broken packages?

nathanpainchaud

brent Those warnings appear even before the OS itself can properly kick in. The file system itself is corrupted, so I don't think broken packages are relevant in this case.

File system corruption happened a few times to computers in my lab. Sometimes running fsck manually (like recommended here in the log) did end up solving the problem. But other times it didn't fix the issue, and IT techs had to reinstall the workstations from scratch.

brent

nathanpainchaud Those warnings appear even before the OS itself can properly kick in. The file system itself is corrupted, so I don't think broken packages are relevant in this case.

you are correct. i saw a tty and ran with it! I've variations (long ago) of this corruption message and in the end it was physical: dying disk with reinstall.
besides fsck I wonder what else is in the arsenal for this? guess we will see the fsck result soon enough
edit: word

brent

Girtablulu (cut and pasted this gem)

MetaNorm

Wow guys, thank you so much for your support!!!! I did it as Girtablulu suggested and it really fixed this issue. I'm so happy not having to reinstall Solus at all again. It was the right decision to pick this distribution and to know you guys around.
Thank you again and have a nice day.