Skip to contentSkip to conversation

dying hdd causing MCE and panic (libata)

DISCUSSION Rumi Szabolcs 2 participants 2 messages Apr 20, 2008

lore
Share & tools
lore
#0 lore raw

Hello all!

A SATA drive in one of my servers has made some final steps towards the grave and it has put out some obvious signs of this onto the console (ATA transactions failing) but then it has also thrown an MCE (CPU context corrupt) and then the kernel has panicked. This server is rock stable otherwise and used to make uptimes measured in months between planned restarts.

The machine has been removed from power completely and restarted multiple times but during the boot process it always crashed with an MCE or a panic or both.

Sorry but I cannot provide exact debug information right now because I wasn't physically there at the time and I'm still 250kms away from that server. In fact I've remotely guided two people without a clue through the phone and they have read things from the console for me, restarted the machine, etc.

So in the end I told them to open up the server and pull the SATA cable from that particular drive. Suddenly all the MCEs and panics had gone away and the machine is running fine since then.

Hardware:

- Nforce4 based motherboard (chipset integrated SATA ports)
- Athlon64 single core CPU
- Diamondmax 9 SATA hard drive

Kernel:

2.6.23-gentoo-r3 (no preempt, no smp)

My questions:

- Is it normal that a simple hard disk failure (that is not even the system disk) causes MCEs and kernel panics?

- Is this a problem that is induced completely on the hardware level (eg. the southbridge going crazy and making the whole hardware platform unstable) or a problem that could be fixed or handled properly on the software (kernel) level?

Thanks!

Best regards,
Sab

#1 lore raw
Quoted 2 lines

- Is it normal that a simple hard disk failure (that is not even the system disk) causes MCEs and kernel panics?

No but with old style (pre AHCI) IDE it can because the system may MCE if the CPU<->Disk hangs. If a drive is causing PSU problems it could also occur I guess - ditto heat. You'd need to decode the MCE

Quoted 4 lines

- Is this a problem that is induced completely on the hardware level (eg. the southbridge going crazy and making the whole hardware platform unstable) or a problem that could be fixed or handled properly on the software (kernel) level?

An MCE the hardware can recover from is reported and we continue. CPU Context Corrupt means the processor internally set a "cannot carry on" indicator.

Alan