Hi,

Sat down yesterday to read through my Sys Log emails and found this on one of my machines:

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


WARNING: Kernel Errors Present
Error: Medium error --...: 17 Time(s)
Unrecovered read error -- (asc=0x11, as...: 17 Time(s)
Buffer I/O error on device hda, l...: 34 Time(s)
end_request: I/O error, dev hda, sector...: 17 Time(s)
hda: irq timeout: error=0xd0LastFailedSe...: 9 Time(s)
hda: media error (bad sector): er...: 17 Time(s)
hda: media error (bad sector): st...: 17 Time(s)

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

I can see it looks like the Internal disk is on its way out, but is there anything i can do to fix this error liek running fsck etc ???? and if so, whats the safest way of using fsck on LINUX?

Thanks People,

Bboy-Mass

One of the signs that you have a hardware problem is that fsck won't fix the problem. The same is true of any operating system with the appropriate disk structure fixer. I recommend replacing the disk as soon as possible but don't discard it. If you have the same problems with a replacement disk then the problem may be the CPU or motherboard or a cable. I had disk problems for a while. The problems continued to happen in the same machine with the new disk. I put the original disk in another machine where it has worked fine. I decided that the motherboard or CPU of the first machine must be the problem and that machine is no longer in service.

Thanks mate.

The machine in question has a mirror in place, so if the disk does go I have some time.

I guess MDADMIN will be my best friend over the next couple of days.lol

Do you have any suggestions with using mdadmin with my issue?

R.
Bboy-Mass

No, I haven't directly used the device mapper. I have heard that it is easier to get things done with device mapper by using EVMS. I could be wrong. All I know is that the EVMS GUI (/sbin/evmsgui) looks pretty easy to use.