| View previous topic :: View next topic |
| Author |
Message |
ranmakun
Guru
Joined: 06 Nov 2002
Posts: 372
Location: Buenos Aires - Argentina
|
 Posted: Mon Mar 31, 2003 7:12 pm Post subject: my filesystem turns to read only!? |
 |
|
I'm not sure whats happening with this machine, after a while of being up multilog starts giving a lot of errors because it says the file system is read-only and an attempt to create a new directory or something gives the same error.
the fstab entry is the usual:
| Code: |
/dev/hda3 / ext3 noatime 0 0
|
and mount gives this output:
| Code: |
kaori / # mount
/dev/hda3 on / type ext3 (rw,noatime)
proc on /proc type proc (rw)
none on /dev type devfs (rw)
tmpfs on /mnt/.init.d type tmpfs (rw,mode=0644,size=2048k)
tmpfs on /dev/shm type tmpfs (rw)
|
I also checked that the disk is not full.
So I don't know why I'm geting these errors.
Any Ideas?
Francisco |
|
| Back to top |
|
 |
David_Escott
l33t
Joined: 12 Jan 2003
Posts: 952
Location: Boston, MA
|
| Posted: Tue Apr 01, 2003 3:29 am Post subject: |
|
|
| what are the permissions on /var/log (ls -l /var) and what is multilog running as (ps -aux | grep log). This is probably the cause somehow. If multilog doesnt have permissions to modify the directory structure of /var/log (and its subdirectories) it wont be able to rotate log files as needed. |
|
| Back to top |
|
|
ranmakun
Guru
Joined: 06 Nov 2002
Posts: 372
Location: Buenos Aires - Argentina
|
| Posted: Tue Apr 01, 2003 5:57 pm Post subject: |
|
|
No, thats not the problem, when I said I couldn't create a directory for example, I mean I cannot create it anyware in the disk. On the other hand if I try to remount / in rw mode I get this:
| Quote: |
kaori root # mount -o remount,rw /
mount: block device /dev/hda3 is write-protected, mounting read-only
|
 ???, what does this mean?, its a hard drive!
Well, some more info:
After this, if a I reboot the machine (with reboot command) I get a kernel panic:
| Quote: |
EXT3-fs: INFO: recovery required on read only filesystem.
EXT3-fs: write access will be enabled during recovery
journal-bmap: journal block not found at offset 3084 on ide0(3,3)
JBD: bad block at offset 3084
journal-bmap: journal block not found at offset 3086 on ide0(3,3)
JBD: bad block at offset 3086
JBD: recovery failed
EXT3-fs: error loading journal.
EXT2-fs: ide0(3,3): couldn't mount because of unsuported optional features (4).
kernal panic: VFS: Unable to mount root fs on 03:03
|
Now, if I reboot again now, it goes well, but at boot it says that my partition has errors and it cant repair them because of an UNEXPECTED INCONSISTENCY, and says to run fsck manually.
Well, I gess is all I can tell, it's driving me crazy. Any ideas on what is going on here?, can this be a hardware problem or something?
Thank you very much.
Francisco |
|
| Back to top |
|
|
db_404
Guru
Joined: 05 Dec 2002
Posts: 336
|
| Posted: Tue Apr 01, 2003 7:48 pm Post subject: |
|
|
I've not used ext3, however just from the messages it looks as though you have some drive corruption.
I've seen something similar with ext2 where I had a box that would boot, run for a while, and then start complaining about bad blocks and file system errors. That was caused by a dead (or at least dying) drive.
You might want to just reformat and restore from backup (assuming you have a backup) and see if that helps. In my case doing that didn't help as the drive errors soon started again. |
|
| Back to top |
|
|
David_Escott
l33t
Joined: 12 Jan 2003
Posts: 952
Location: Boston, MA
|
| Posted: Tue Apr 01, 2003 10:33 pm Post subject: |
|
|
When you boot are you getting a message about the partition not being checked in X many mounts. You probably need to fsck it.
Get our your install cd. You can then use that to fsck your filesystem.
This is actually a good reason to consider breaking up your partitions. Having a seperate /home /usr /opt from / makes this stuff easier to deal with since corruption on one partition doesn't mean the others are in trouble. |
|
| Back to top |
|
|
ranmakun
Guru
Joined: 06 Nov 2002
Posts: 372
Location: Buenos Aires - Argentina
|
| Posted: Tue Apr 01, 2003 10:57 pm Post subject: |
|
|
well, I've already fsck my partition everytime this happen, and always reboot and I have the same problem after a while, my partition "turns" to read only, so I'm not sure what to do. I've also tried to mount the boot partition to see if this partition has the same problem, but it mounts without problems.
Maybe its a hardware problem, I'll try with another disk I have laying arround.
Thank you guys.
Francisco |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
