PDA

View Full Version : [ubuntu] File/Folder constantly revert to read-only



wind_dragon
January 3rd, 2009, 03:13 AM
As is described in the title my folders and files keep reverting to read-only a few minutes after the computer has been booted. Is there anyway to fix this and permanently keep my files read-write only without the terminal(i'm having trouble with that as well)?

cmnorton
January 3rd, 2009, 07:44 PM
Offhand this sounds like your file system was remounted read-only after a failure on the drive.

What Linux distro is this?

Does this happen to any other user on the system?

Do your logs indicated anything interesting? (/var/log/messages for starters).

What's the output of df?

scorp123
January 3rd, 2009, 08:27 PM
As is described in the title my folders and files keep reverting to read-only Which files precisely?? Can you please give us their exact names and locations? e.g. /usr/bin/something, /home/yourusername/something, and so on?

wind_dragon
January 4th, 2009, 01:35 AM
Offhand this sounds like your file system was remounted read-only after a failure on the drive.

What Linux distro is this?

Does this happen to any other user on the system?

Do your logs indicated anything interesting? (/var/log/messages for starters).

What's the output of df?

ubuntu 8.04
I am the only user, so i'm the admin(i think)

when i boot, Ubuntu does a disk scan and fails. I normally skip it because it can't continue due to various failures. I think my HDD might be dying.

Don't know what the "output of df" is, sorry.:(

wind_dragon
January 4th, 2009, 01:37 AM
Which files precisely?? Can you please give us their exact names and locations? e.g. /usr/bin/something, /home/yourusername/something, and so on?

Its everything in the home and sys folders. (docs, music, pics, desktop,etc. even the hidden files are all locked)](*,)

taurus
January 4th, 2009, 01:39 AM
What are the outputs of these commands from a terminal?

Applications -> Accessories -> Terminal

sudo fdisk -l
cat /etc/fstab
df -h

wind_dragon
January 4th, 2009, 04:44 AM
What are the outputs of these commands from a terminal?

Applications -> Accessories -> Terminal

sudo fdisk -l
cat /etc/fstab
df -h

I cannot access terminal.

handydan918
January 4th, 2009, 05:37 AM
Well, if you don't have another computer to use, write those commands down and hit ctrl+alt+f2 to cet to a console, and run them from there.

scorp123
January 4th, 2009, 11:27 AM
when i boot, Ubuntu does a disk scan and fails. Boot from the Live CD and then check the filesystem from there.

How to determine which HD partition to check:

sudo fdisk -l

This should spit out a list of all partitions and their type. Check those which are marked as being "Linux". Example:

> sudo fdisk -l
[sudo] password for sysadm:

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00061ad7

Device Boot Start End Blocks Id System
/dev/sda1 * 1 60770 488134993+ 83 Linux
/dev/sda2 60771 60801 249007+ 5 Extended
/dev/sda5 60771 60801 248976 83 Linux


So I'd have to check the partitions /dev/sda1 and /dev/sda5. Command:

sudo fsck /dev/sda1 ... depending on the damages it finds it will ask you a few questions. Usually it's best to reply "y" (=yes) and to let fsck repair the damages it encounters.

Repeat this step for each of your Linux data partitions; skip swap.

Once you're finished you should reboot. Your PC should now start without any complaints about damaged filesystems and the permissions should remain the way you set them, there should be no more unexpected changes.

wind_dragon
January 4th, 2009, 09:14 PM
My sda5 says Linux+Solaris
run the code on this as well?

Edit:
Whoops. nevermind it says swap next to it

wind_dragon
January 5th, 2009, 06:43 AM
so everything worked out ok on the reboot. On the next boot it reverted back to the old problem(the disk checks and a bunch of inode/orphan errors). OMG! this is so irritating!

Carl Hamlin
January 5th, 2009, 07:11 AM
so everything worked out ok on the reboot. On the next boot it reverted back to the old problem(the disk checks and a bunch of inode/orphan errors). OMG! this is so irritating!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Yep - your initial impression is probably correct, and this drive is toasting. I'd recommend backing up your important data as soon as possible and replacing the drive.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAklhpIoACgkQyLm4ydrABvfI0ACgxs3xQ7qsMd 7I3ku6HOK+A2GB
bI8An0U+sHIiIQG79gqvY3Kc0J7iAwlg
=6Tpj
-----END PGP SIGNATURE-----

wind_dragon
January 6th, 2009, 08:27 AM
As i thought. I'll just reinstall ubuntu on a different hard drive then.