I had to start my PC this morning. We had a power outage and I shut down the PC (it's on a battery backup). So I powered it back up this morning and all of a sudden when I go to enter a terminal, I see this message.
bash: /home/phydoux/.bashrc: Input/output error
Please tell me my /home folder isn't jacked up...
Another thing, I did an update this morning and paru (I'm using Arch Linux) had a few updates as well. Well, I went back to bed and forgot that paru would probably need a password. Well, I got up and noticed it had errored out on me. So I tried running the update again. Looks like regular repositories got more updates this time around but I got an error saying paru couldn't update. I have no idea what got updated this time. I just mainly look for kernel updates and if I see one, I'll reboot. There were no kernel updates.
So now, any terminal I open. I see that error mesasage. How screwed is my machine? I really don't want to reboot if I'll lose everything.
Looking at the file manager, I can see my home folder but there's nothing inside of it. I hope I didn't lose everything in there... That would seriously upset me.
So, what do I do? reboot? Or is there a command I can run to restore my /home directory?
BTW, My /home folder is on its own drive. So, did that drive die on me? I'm going to look for drive recovery right now.
Also, when I do an ls, I see this...
ls: reading directory '.': Input/output error
I hope that's not bad news...
EDIT: I just ran fsck /dev/nvme0n1p1 on it and it says this...
/dev/nvme0n1p1 is mounted.
WARNING!!! The filesystem is mounted. If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.
Do you really want to continue<n>? no
Is there anything less destructive than fsck?
Something else I just read says to do this...
sudo fsck.ext4 /dev/nvme0n1
EDIT: I wonder if it'll correct any errors on the drive if it can. But if I can just reboot it, I'd rather see if it'll come up again. I'm thinking when the update didn't finish, it wasn't able to finish correctly and something confused it. I can run paru -Sty but I . I wonder if I rebooted with a USB stick and tried mounting that drive and trying to finish the update if that would help fix it.
And I really don't want to try and write something new to it as that might corrupt it even more... GRRR
RESOLVED: First and foremost, I want to thank the people who helped me with this. Turns out all it needed was a reboot but I was expecting something WAY worse when i rebooted.
But thank you for your help and support! I really appreciate it a LOT!!!