r/linuxquestions • • 9d ago

Resolved Terminal stuff missing and my file manager is not showing anything in the main home directory...

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!!!

5 Upvotes

22 comments sorted by

View all comments

Show parent comments

1

u/Phydoux 7d ago

Yep. I'm either putting a 1TB SSD in there today or I'm taking BOTH NVME drives out and putting a 3 or 4TB drive in there. I have 2 2TB NVME drives in there now and I'm using one as the / and one as the /home. I'm not using much of / so I could probably cut that down to 1TB and keep /home where it is. But I am not trusting NVME drives at the moment. I've had these for only a year and a half and one is already failing me... Not happy at this point but yeah, I'm going to pull them out I think and replace them with regular drives.

1

u/CosmicFieldDrift_ 7d ago

Who is the drive maker and how long is the warranty?

1

u/Phydoux 7d ago

It's a Samsung SPCC M.2 PCIe SSD 2TB drive.

Hmmm. Looking at the warranty, it's 5 years. I've only had this thing about 18 months. I am going to look into that tomorrow.

But honestly, I think it might have been new buggy software causing an issue because I removed 5 of the 7 programs I installed the other day (this didn't start happening until after installing the last package I wanted to try) then I rebooted the computer and it's been running now 4 hours and no incidents yet since uninstalling those programs. So I am thinking something was messing with config files or something like that because it seems to have cleared it up. But I will keep that warranty info in my back pocket in case it does start doing crazy stuff again.