| View previous topic :: View next topic |
| Author |
Message |
SillyPants
Apprentice
Joined: 02 Sep 2002
Posts: 154
|
 Posted: Sun Jun 08, 2003 6:00 am Post subject: 'Read-only file system' |
 |
|
| After about 5 minutes, one of my drives starts saying it's read-only. I can remount it, and it goes back to being read-write for about 5 minutes, then goes back to being read-only. Does anyone know why this would be the case? |
|
| Back to top |
|
 |
marshall_j
Tux's lil' helper
Joined: 22 Jan 2003
Posts: 98
Location: NZ
|
| Posted: Sun Jun 08, 2003 11:22 pm Post subject: |
|
|
| what is in /etc/fstab and do you have any messages in the logs? |
|
| Back to top |
|
|
SillyPants
Apprentice
Joined: 02 Sep 2002
Posts: 154
|
| Posted: Mon Jun 09, 2003 2:34 am Post subject: |
|
|
The faulty drive is my WD400BB (/dev/hdb). Here's my fstab: | Code: | # Copyright 1999-2002 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License, v2 or later
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.7 2002/05/12 21:48:18 azarah Exp $
# /etc/fstab: static file system information.
#
# noatime turns of atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail and tail freely.
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/sda1 /boot ext3 noauto,noatime 1 1
/dev/sda3 / ext3 noatime 0 0
/dev/sda2 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/dvd auto user,noauto,ro 0 0
/dev/cdroms/cdrom1 /mnt/cdrom auto user,noauto,ro 0 0
/dev/hda1 /mnt/wd800 ext3 defaults 0 0
/dev/hdb1 /mnt/wd400 ext3 defaults,rw 0 0
/mnt/wd800/home /home none defaults,bind 0 0
/dev/fd0 /mnt/floppy ext2 noauto 0 0
proc /proc proc defaults 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink). Adding the following
# line to /etc/fstab should take care of this:
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will use almost no
# memory if not populated with files)
#tmpfs /dev/shm tmpfs defaults 0 0
|
I wasn't sure which logs to look at, but in /var/log/kernel I have a few of these: | Code: | Jun 8 01:58:45 [kernel] EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jun 8 01:58:45 [kernel] EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,65), internal journal
Jun 8 01:58:45 [kernel] EXT3-fs: mounted filesystem with ordered data mode.
Jun 8 02:39:41 [kernel] hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jun 8 02:39:41 [kernel] ext3_new_block: aborting transaction: Journal has aborted in __ext3_journal_get_undo_access<2>EXT3-fs error (device ide0(3,65$
Jun 8 02:39:41 [kernel] ext3_abort called. |
which may be relevant?
--Frank |
|
| Back to top |
|
|
marshall_j
Tux's lil' helper
Joined: 22 Jan 2003
Posts: 98
Location: NZ
|
| Posted: Mon Jun 09, 2003 8:45 pm Post subject: |
|
|
Yeah from what's in the log I'd go with fsck'ing the drive and see if that helps first.
fstab looks fine tho.  |
|
| Back to top |
|
|
SillyPants
Apprentice
Joined: 02 Sep 2002
Posts: 154
|
| Posted: Mon Jun 09, 2003 9:09 pm Post subject: |
|
|
fsck gave some errors. Backed up my data and re-formatted the drive. ow it's been running for about 24 hours and no problems. Must have been cosmic radiation randomly twiddling the all-important 'function properly' bit.
thanks |
|
| Back to top |
|
|
|
Kernel & Hardware
