/dev/hda2 has now been mounted for two hours and 15 minutes without going ro. That surpasses by more than a factor of four any records that were made over the past week. Normally things wouldn't even have lasted as long as it has taken me to write a fraction of this message. I'm inclined to think that the problem is not going to occur now.
Here's what I did.
1) Booted into Knoppix. Mounted /dev/hda2. Edited /mnt/hda2/etc/fstab/ and changed the line pertaining to /dev/hda2 from ext3 to ext2.
/etc/fstab now looks like:
Code:
# /etc/fstab: static file system information.
#
#<file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda2 / ext2 defaults 0 1
/dev/hda5 none swap sw 0 0
/dev/sda1 /mnt/sda1 auto sync,noauto,user,exec 0 0
/dev/hdc /mnt/cdrom iso9660 ro,user,noauto 0 0
/dev/hda1 /mnt/windoze ntfs ro,user,noauto 0 0
2) Shut down the computer and booted into the /dev/hda2 partition (i.e. running the Debian installation now).
3) Was disappointed to see the problem still occured, but then found out that it was still mounted as ext3 anyway (according to /etc/mtab).
4) Things were still buggered up so rebooted the computer again back into /dev/hda2 (i.e still Debian installation). Computer did an fsck for about an hour before being able to continue.
5) Back logged on now into Debian installation working from /dev/hda2 as root. Couldn't umount /dev/hda2 or remount it read-only. Then the problem occurred. Once the partition was sent into read-only mode, I was able to umount it.
6) Then issued: e2fsck -fy /dev/hda2
This gave a bunch of errors about
:
- blocks claimed by more than one inode
- incorrect filetype (was 2 should be 1)
- deleted/unused inode
- unconnected directory inode
- inode ref count wrong
- unattached inode
and (according to all appearances) was fixing the errors.
The second time issuing e2fsck -fy /dev/hda2 it again found errors and fixed them.
The third time it did not find errors so I did not try it a fourth.
7) Then issued: tune2fs -O ^has_journal /dev/hda2
8) Then issued again: e2fsck -fy /dev/hda2
No errors were reported this time.
9) Restarted by typing init 6; crossed fingers to near injury
10) Noted that /etc/mtab now states that /dev/hda2 is mounted as ext2.
11)
Even if it comes back now, at least there's a positive development.
Thank you so much everyone freakyg, Nylex, sundialsvcs, tuxdev, aysiu, Ambroise, Bonzodog!!!for your helpful posts!!!
Ambroise I hope this helps your situation.
--------------------------------------------------------------------------------------------------------------------
EDIT: Up now for 11 hours and still going strong.
Next project: see if bringing back jounaling causes the problem to come back.
--------------------------------------------------------------------------------------------------------------------
EDIT: Bringing back journaling caused no problems at all.
(did #tune2fs -j /dev/hda2 to bring it back)
Everything seems to be fixed although I don't know what really happened.
)
