I removed a file, now my filesystem is read only

jgreen1tc · 2011-10-25 15:28:38

Yesterday, when running pacman -Syu, I got the error described here. I didn't know the procedure to solve the issue at the time, and in my haste to get the update started so I could get to class, I just removed the file before checking if it was owned by another package. Everything worked for a while afterwards, and then my system completely froze. I gave it a hard reboot and now my filesystem is read-only.

I'm assuming another (important) package owned this file? If I were to find out what file I removed, would I be able to find the package that owned it and transfer the file somehow to my computer?

I will edit this post with the file I removed after I walk back to my room to check my pacman log...if that is important at all...

karol · 2011-10-25 15:49:52

We need to know what file was that. Was it http://www.archlinux.org/news/initscrip … -required/ ?

If in doubt, postpone an update until you have time to think - especially if it involves unusual steps, doubly so if you're removing stuff.

DSpider · 2011-10-25 16:03:17

How do you know it's read-only? If you right click something - Properties - Permissions, does it say which user it belongs to?

Are you part of the "storage" group?

$ groups jgreen1tc   (or whatever name you use to log in)

When in doubt, use "mv /path/to/source/file /path/to/destination/and/or/file" instead of rm. It basically moves it, and you can also "move" it in the same directory with the ".bak", ".backup", ".old", etc., extension.

Last edited by DSpider (2011-10-25 16:03:46)

jgreen1tc · 2011-10-25 18:02:43

karol wrote:

We need to know what file was that. Was it http://www.archlinux.org/news/initscrip … -required/ ?

If in doubt, postpone an update until you have time to think - especially if it involves unusual steps, doubly so if you're removing stuff.

I couldn't find it in the log but I am 90% sure that was it. I'm going to read up on that and be more careful in the future. Teaches me to not read the front page I guess.

DSpider wrote:

How do you know it's read-only? If you right click something - Properties - Permissions, does it say which user it belongs to?
Are you part of the "storage" group?
$ groups jgreen1tc   (or whatever name you use to log in)
When in doubt, use "mv /path/to/source/file /path/to/destination/and/or/file" instead of rm. It basically moves it, and you can also "move" it in the same directory with the ".bak", ".backup", ".old", etc., extension.

I know it's read only because many commands tell me so. I cannot right click anything as I startx through my .xinitrc file and it is read only. I am stuck in tty1.

Good advice with the second part. I'll keep that in mind. I'll post back after I read through karols link if I need any help.

karol · 2011-10-25 18:06:26

-rwxr-xr-x 1 1,5K 10-10 06:53 .xinitrc

These are my .xinitrc permissions, what are yours?

Can you create or edit some file?

jgreen1tc · 2011-10-25 21:39:02

karol wrote:

-rwxr-xr-x 1 1,5K 10-10 06:53 .xinitrc
These are my .xinitrc permissions, what are yours?
Can you create or edit some file?

Now that I'm looking around, I'm starting to notice this error when I log in as user

No directory, logging in with HOME=/

So I have no .xinitrc or anything in my users /home directory for that matter. Even as root, my files are read only.

I'm starting to think about doing a clean install and being more careful. Would I even be able to fix it without editing any files?

meph · 2011-10-26 15:22:56

The error message you see means that the login command can't find a home directory for the user in your /etc/passwd file and uses / instead.

Your /etc/passwd might be corrupt, your problem might have nothing to do with the update and your removing a file. This would also explain why even root doesn't have write access to the whole filesystem, as its UID is read from /etc/passwd file as well. Your /etc/shadow might still be intact and that would be why login command lets you actually log in any user with its respective password, but missing info from /etc/passwd confuses it into thinking that even root is a regular user.

You can manually check contents of /etc/passwd, or there's a tool for that, called pwck.

Arch Linux

#1 2011-10-25 15:28:38

I removed a file, now my filesystem is read only

#2 2011-10-25 15:49:52

Re: I removed a file, now my filesystem is read only

#3 2011-10-25 16:03:17

Re: I removed a file, now my filesystem is read only

#4 2011-10-25 18:02:43

Re: I removed a file, now my filesystem is read only

#5 2011-10-25 18:06:26

Re: I removed a file, now my filesystem is read only

#6 2011-10-25 21:39:02

Re: I removed a file, now my filesystem is read only

#7 2011-10-26 15:22:56

Re: I removed a file, now my filesystem is read only

Board footer