Hi guys I have server I reboot it the below massege appear to me
my server based on redhat linux .please inform me what can I do?



hda:read_intr:error=0x40 {uncorrectableEroor},LBAsect=3196936,sector=1
end_request:I/O error ,dev 03:06 (hda),sector 1 >
RAMDISK:Compressed image found at block 0
autodetecting RAID arrays
autorun...
...autorun DONE.
apm:BIOS not found.
EXT2-fs warning:checktime reached,running e2fsck is recommended
VFS:Mounted root (ext2 filesystem).
autodetecting RAID arrays
autorun...
... autorun DONE
attempt to access beyond end of device
03:0d:rw=0, want=2, limit=0
dev 03:0d blksize=1024 bloknr=1 secto=2 size=1024 count=1
EXT2-fs:unable to read superblock
Invalid session number or type of track
attempt to access beyond end of device
03:0d: rw=0, want=33, limit=0
dev 03:0d blksize=1024 blocknr=32 sector=64 size=1024 count=1
isofs_read_super:bread failed, dev=03:0d, iso_blknum=16, block=32
kernel panic:VFS:Uable to mount root fs on 03:0d

Looks like you have a bad disk. Did you backup?

could you please provide more details about what you have done before rebooting? (e.g. update, changing some files, change hardware, install software)

also, are you able to get access to your hard drive with rescue CD?

Hi
my server it was running and suddenly the power switch off
then I tunred on and that massege appear to me

I dont know how I access to the hard disk and I dont know
make scan for bad sector or repairing the bad sector

Hi again,

this is the plan:
1. the boot process is as follow: BIOS initialization -> bootloader stage 1 (MBR) then stage 2 (/boot) -> kernel initialization -> init starting. we should check where is the error location.
2. based on the location of the error, we will try to fix it.

from the error message i can see that:
1. You are using ext2 filesystem, which is not supporting journalling. The journalling will help in such situation.
2. it might be the whole harddrive is corrupted or (i hope) the /boot partition, which could be solved by reinstall the boot loader.

I have a question: are you NOW getting the lilo or grub boot menu? and was you getting the same menu before the error?

for the time being, you may run the command "e2fsck -vf /dev/hda?" where ? is number from 1 to the max partition number do you have; usually /dev/hda1 for /boot (which is my concern) and /dev/hda2-4 for others

replay with the result and the answer of the two questions, and i will be glad to help you.

by the way, what is the version of Redhat do you use? and what service(s) do you run in that server?