Good morning,

I hoping some in the forums can shged some light on what is wrong with my server. As the outages are quite long when it is rebooted.

I have the following entries in my messages files

I also see the follow errors:

Jan 31 10:29:00 -hub kernel: EXT3-fs error (device ide0(3,3)): ext3_
new_block: block(19251895) >= blocks count(19251894) - block_group = 587, es ==
f7b28400
Jan 31 10:29:12 hub kernel: EXT3-fs error (device ide0(3,3)): ext3_
new_block: block(19251896) >= blocks count(19251894) - block_group = 587, es ==
f7b28400

and

Jan 31 09:09:38 -hub kernel: hda: write_intr: error=0x10 { SectorIdN
otFound }, LBAsect=156311348, high=9, low=5316404, sector=154014053
Jan 31 09:09:40 -hub kernel: hda: write_intr error1: nr_sectors=3, s
tat=0x51
Jan 31 09:09:41 -hub kernel: hda: write_intr: status=0x51 { DriveRea
dy SeekComplete Error }

When the server is rebooted it also seems to be failing on the following service
Jan 31 22:02:07 -hub nfslock: rpc.statd shutdown failed

EV1 said the fsck keeps looping and cannot perform a full fsck check. As a result i see the following message:
Feb 1 05:40:55 -hub kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended

They also ran a badblocks check in single user mode and did not find any problems.

Any help would be appreciated

David

Need more information on the system.
Which :
Redhat
hard disk
Raid (?)
kernel version
fstab setup

It could be a failing drive , but it needs testing properly.

alan

Hi sorry

os:Redhat 7.3

80GB Hdisk

P4 1 GB of ram

kernel : BOOT_FILE=/boot/vmlinuz-2.4.20-20.7 fastboot

fstab:
/dev/hda3 / ext3 defaults,usrquota 1 1
/dev/hda1 /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hda2 swap swap defaults 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0

Have you tried running e2fsck -pf /dev/hda1 and e2fsck -pf /dev/hda3 ?
( man e2fsck )
BTW, your kernel is pretty much out of date as well, the last released was 2.4.20-28.7 I think.
But get the filesystem clean before upgrading the kernel.

Does it eventually boot at all, or is it dead ?

alan

I know about upgrading the kernel...its the only thing on my redhat update that is out of date

It eventually boots but in single user mode and then we have to switch the run time afterwards.

I have have put in a request for a full hardware test and I guess we will see what happens

Just was wondering if anyone saw these messages before

I had errors on my RH9 box at home ,and fsck runs automatically.
But due to a block error, fsck couldn't complete, and suggested it was run manually, ie, not set to automatically fix errors.
I did that, and it found errors and asked me if I wanted to fix them, to which I replied yes, and after 4 or 5 prompts like that, fsck completed, and I have had no more errors.

I would check to make sure that the EV1 techs are running fsck manually.

alan

Thanks for the suggestion, that is exactly what they did....