PC boots to rescue mode, couldn't mount sysroot.mount

BuzzPCSOS

Jett We are all getting in a little deep here. Remote diagnostics and fixes are always hard work without the intuitive insight of working on the machine personally.
Why not try Rescatux? It has been about for a good while and can make a good job of making your machine bootable again. Before you run Rescatux it is helpful to know if your installation is Legacy (BIOS) or UEFI, then you can start Rescatux in the same mode.
It's good that you can boot from a (Solus?) Live USB, That at least indicates that your firmware is mostly not to blame. While in the Live environment you should check your hard drive for errors and also check S.M.AR.T. data for signs of failure.
Jett I'm afraid that error dump didn't give me any clues but it could go a long way to helping someone else help you.
If you get a chance, let us know which edition of Solus you are running (Budgie, Gnome, Plasma or XFCE) as this helps us to choose the right system tools for you to carry out checks with.
Good luck with fault finding, I hope you are feeling better soon.

Jett

BuzzPCSOS
My PC is UEFI, Plasma.
Here is the emergency screen my solus stops at.
[FAILED] Failed to mount sysroot.mount - /sysroot.
[DEPEND] Dependency failed for initrd-root--fs.target - Initrd Root File System
[DEPEND] Dependency failed for initrd-parsetpoints Configured in the Real Root

Generating "/run/initramfs/rdsosreport.txt"

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

Press Enter for maintenance
(or press Control-D to continue):

Thanks Buzz, I doubt I will be feeling better soon, I thought I had stroke, my right arm right leg is working at about
50% capacity right now...I'm right handed! I didn't stroke out they said. I just woke up Friday morning a week ago like this. My pc stroked out a couple days before.

Axios

Jett First I would check the file systems efi and root from live cd
if that checks ok
Would do what Buzz suggested the boot may still be messed up

BuzzPCSOS

Jett My PC is UEFI, Plasma.

That's handy I use Plasma too.
Boot into the Live USB. Run Menu>System>KDE Partition Manager.
Your hard drive should be listed under Devices in the top left corner of the screen.
Right-click on your hard drive and select Smart Status from the drop-down menu.
It should show Smart status = Good Healthy and Overall assessment = Healthy
Close Smart status.
In KDE Partition Manager main screen towards the top right-click on the individual hard drive partitions and choose "Check".
It will save that as a task that has to be applied from the top menu. From personal experience all partitions should be able to be checked in this way without further complicating your problem.
When the partitions have been checked make sure to look at the details to see if it has found anything important or that it could not fix.
Reboot in case that has fixed it.
For simplicity my next call would be to boot with Rescatux and try that.
Depending on how much you have stored on your PC it might just be easier to copy all your files onto an external drive and do a clean install. I try to keep as much as I can on external storage because every computer can go wrong.

Jett

I think I am gonna log out for tonight, I am out of energy now.
Thank you everyone for your help.

Jett

BuzzPCSOS
I checked the smart status and it was good, overall healthy.
I ran check and both partitions checked out as ok.
I can't access my solus drive using dolphin from live USB, so I can't move my home folder to save it.
It keeps looking like the mount point needs to be edited/restored and I have no idea what to do about that. I can't even chroot that solus drive because of no mount point. There is a place to do that in kde partition manager, but it is not very intuitive. What do I type in there for a new mount point?

Axios

I am just posting this as a general statement for people following the thread.
Because I see people say I did this and shut computer off and now its borked.
People make sure and let your computer finish its tasks before shutting off ect.
(Not saying thats what happened here)
Its not just a Linux thing it can happen with any computer.
They can be sneaky sometimes and the HD light is a good indicator on desktops
for activity.
(Just info)

BuzzPCSOS

Jett I can't access my solus drive using dolphin from live USB

This sounds like you used some kind of file encryption during install or you used a non EXT4 file system.
On a previous install I opted to use F2FS but then found that I could not access the file system from the Live USB.
I am no expert on chroot so will not muddy the conversation with my advice regarding that. At this point my own thoughts are that Rescatux is your best hope right now.
If you have installed with something like F2FS you might find booting into something like Fedora could make your home directory available again to save to external storage (but unsure). If you encrypted your install then I think your only option is to repair the boot, hopefully we will hear from someone with more experience who can talk you through that without loss of your data.

brent

BuzzPCSOS If you encrypted your install then I think your only option is to repair the boot,

that was my initial diagnosis way up there, or one of them. would explain /root not mounting as LVM has very distinct and different help center chroot steps (these specific lvm steps are written into the regular chroot guide so easy to get wires crossed.
I agree with your conclusion: let the pros handle it (rescatux).

Jett

BuzzPCSOS
It is NOT LVM encrypted
I have FAT32 boot partition and BTRFS for root partition.
I looked at Rescatux site at it's functions and I did not see anything about mountpoints. And I am on a live USB. I tried to download gparted, and it failed for not enough room.

brent

Jett and BTRFS for root partition

ding ding ding.
https://discuss.getsol.us/d/11340-btrfs-handling-restoration
"failed to mount sysroot.mount" with solution even though problem not the same but similar.
never dabbled with btrfs personally--seems like a whole other animal

Axios

Jett We really need to see the error text file when you try to boot.
I would be careful with BTRFS you can hose data easly (If you need to keep it)
I think because the root partion filesystem is still messed up its not booting.
And honestly dont know if kde partion can fix btrfs.

Jett

brent
That does not make a bit of sense to me! I have never been good at command line stuff because I can never remember all the commands. I don't think in words, I think in images. So I never got familiar with the command line. It makes me feel like I am dyslexic...or perplexic!
I know how to use snapper, but solus doesn't appear to have that.

Jett

Axios
This is the error text;
Here is the emergency screen my solus stops at.
[FAILED] Failed to mount sysroot.mount - /sysroot.
[DEPEND] Dependency failed for initrd-root--fs.target - Initrd Root File System
[DEPEND] Dependency failed for initrd-parsetpoints Configured in the Real Root

Generating "/run/initramfs/rdsosreport.txt"

Press Enter for maintenance
(or press Control-D to continue):

KDE partition manager says it supports BTRFS filesystems.

Axios

Jett Sorry I wasnt clear met the rdsosreport.txt
I am not versed enough with BTRFS on repair but can help with determining what the issue is
maybe.

Jett

It keeps looking like the mount point needs to be edited/restored and I have no idea what to do about that. I can't even chroot that solus drive because of no mount point. There is a place to do that in kde partition manager, but it is not very intuitive. What do I type in there for ~~a new~~ the correct mount point?

Jett

Axios
OK, I will have to Shut down solus live to do that. While I am still here, how should I get that text file?

Axios

Jett Dang you cant not sure what to do now!

Jett

Axios
I am getting mentally exhausted...how about we call it a day now?
It will give us some time to think of a new plan.

« Previous Page Next Page »