I reinstalled ML9.0 (for the third time) on 9/2/03
I found just by coincidence in
/lib/modules/2.4.19-16mdk/kernel/drivers/scsi:
53c7,8xx.o.gz 2GB big !!!!!! I repeat 2GB big (date was normal 20/9/02)
and the partition is only 2GB big.
What happened ???
I haven't done much configuration yet to that install, last thing I did
with it was make a backup.
I guess at install something must have gone wrong.
>From my ML8.2 I did a
"e2fsck -f -c /dev/hda2" (suggested by J.Grant)
to search for badblocks.
I first changed in /etc/fstab hda2 to ro (read-only).
"e2fsck -f -c /dev/hda2" gave this:
"[root@mycom root]# e2fsck -f -c /dev/hda2
e2fsck 1.26 (3-Feb-2002)
/dev/hda2 is mounted.
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)? yes
Checking for bad blocks (read-only test): done
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create<y>? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #3 (13860, counted=13859).
Fix<y>? no
Free blocks count wrong (132161, counted=132160).
Fix<y>? no
Free inodes count wrong for group #0 (8528, counted=8527).
Fix<y>? no
Directories count wrong for group #0 (527, counted=528).
Fix<y>? no
Free inodes count wrong (145295, counted=145294).
Fix<y>? no
/dev/hda2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/hda2: ********** WARNING: Filesystem still has errors **********
/dev/hda2: 118001/263296 files (0.2% non-contiguous), 393967/526128
blocks"
I pressed no when asked to fix things, when it asked to create a
/lost+found DIRECTORY I had to say yes: it created a /lost+found on
/dev/hda2 allthough in /etc/fstab it says ro.
How come that a directory could be created by e2fsck in a partition that
has read-only access?
I'm not sure what e2fsck does, I think it didn't find badblocks
("Checking for bad blocks (read-only test): done"), is this correct?
I'll have to reinstall ML9.0 ( for the 4th time, bah).
How can I be certain that it'll be installed correctly?
How many other files have been compromised? "rpm -Va" isn't sufficient
to check a complete linux installation, is it?
I don't know what the errors above mean.
And what has caused this corruption of files? Is it memory, hard disk,
IDE cable, IDE controller, UDMA, CPU, cooling, CD-Writer,...?
Did it happen at installation of ML9.0, afterwards?
In thread "ML9.0:file system completely crashed ext3,"could not find
mime type",kde3.0.3" I began to think it might have been the bad UDMA5
implementation of my Western Digital hard drive but now I'm not sure
wether it might be because of something else.
I tested my 512 MB memory a couple of times with memtest86 (not enough I
know), I tested with a utility from WD my hard drive: didn't found any
errors.
J.Grant replied:
"If they were badblock errors your HD has failed, replace it and your
problems might go away."
vatbier
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
