logwatch error

[Eyal - IsraServ]

--------------------- Kernel Begin ------------------------


WARNING: Kernel Errors Present
end_request: I/O error, dev 03:02 (hda)...: 8Time(s)
hda: dma_intr: error=0x40 { Uncorrect...: 8Time(s)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }...: 8Time(s)
raid1: hda2: unrecoverable I/O read error for block 147618...: 8Time(s)

---------------------- Kernel End -------------------------

should i worry ?
i have a software raid1 on my linux , and when i type cat /proc/mdstat i get :

Personalities : [raid1]
read_ahead 1024 sectors
md2 : active raid1 hda3[0] hdb3[1]
4096448 blocks [2/2] [UU]

md1 : active raid1 hda2[0]
112639680 blocks [2/1] [U_]

md0 : active raid1 hda1[0] hdb1[1]
305088 blocks [2/2] [UU]

unused devices: <none>


---------------------------------------------------

all my files are at md1 (as i can see in server information /dev/md1 106G 66G 36G 65% / , this mean that raid 1 isnt working ?

[chirpy]

If you only get that error once when you reboot the server, it's probably OK. If you're seeing a numer of those errors when the server has been running for a while, then the drive on /dev/hda may be about to die and you should get it replaced.

[Eyal - IsraServ]

If you only get that error once when you reboot the server, it's probably OK. If you're seeing a numer of those errors when the server has been running for a while, then the drive on /dev/hda may be about to die and you should get it replaced.

Hi

thanks for the fast reply , i get those error in the past of those 2 weeks every day , server's uptime is about 100+ days , so i will reboot it and i will see what is going on

what do you think about the raid ?

hda: WDC WD1200JB-00EVA0, ATA DISK drive
hdb: WDC WD1200JB-00EVA0, ATA DISK drive

/dev/md1 106G 66G 36G 65% /
/dev/md0 289M 67M 208M 25% /boot

md0 (that have the [UU] ) is the boot partition . this mean that just the boot partition is under the raid1 system ?

[chirpy]

With md devices, you'll probably get this information that you need from:

mdadm --detail /dev/md0
mdadm --detail /dev/md1

[Eyal - IsraServ]

With md devices, you'll probably get this information that you need from:

mdadm --detail /dev/md0
mdadm --detail /dev/md1

mdadm --detail /dev/md0
-bash: mdadm: command not found

[chirpy]

If this is a Linux server and you're running software raid, then you should be able to install mdadm with:

/scripts/ensurerpm mdadm

[Eyal - IsraServ]

root@ns1 [~]# mdadm --detail /dev/md1
/dev/md1:
Version : 00.90.00
Creation Time : Sun Feb 22 22:58:06 2004
Raid Level : raid1
Array Size : 112639680 (107.42 GiB 115.39 GB)
Device Size : 112639680 (107.42 GiB 115.39 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 1
Persistence : Superblock is persistent

Update Time : Thu Mar 24 22:09:58 2005
State : dirty, no-errors
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0


Number Major Minor RaidDevice State
0 3 2 0 active sync /dev/hda2
1 0 0 1 faulty removed

as i can see its gone , do i wrong ?