linux-kernel - Re: raid5:md3: read error corrected , followed by , Machine Check Exception: .

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 15 Jul 2007 02:04:54 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Mr. James W. Laferriere" <babydr@...y-dragons.com>
Cc:	linux-raid maillist <linux-raid@...r.kernel.org>,
	Linux Kernel Maillist <linux-kernel@...r.kernel.org>
Subject: Re: raid5:md3: read error corrected ,  followed by ,  Machine Check
 Exception: .

On Sat, 14 Jul 2007 17:08:27 -0700 (PDT)
"Mr. James W. Laferriere" <babydr@...y-dragons.com> wrote:

>  	Hello All ,  I was under the impression that a 'machine check' would be 
> caused by some near to the CPU hardware failure ,  Not a bad disk ?

It indicates a hardware failure

> Jul 14 23:00:26 filesrv2 kernel: sd 2:0:1:0: SCSI error: return code = 0x08000002
> Jul 14 23:00:26 filesrv2 kernel: sdd: Current: sense key: Medium Error
> Jul 14 23:00:26 filesrv2 kernel:     Additional sense: Read retries exhausted

So your disk throws a fit

> Jul 14 23:17:06 filesrv2 kernel: raid5:md3: read error corrected (8 sectors at 72269184 on sdd)
> Jul 14 23:17:06 filesrv2 kernel: raid5:md3: read error corrected (8 sectors at 72269192 on sdd)

Raid happily recovers the mess

> Jul 14 23:20:28 filesrv2 kernel: raid5:md3: read error corrected (8 sectors at 76388336 on sdd)
> Jul 14 23:20:28 filesrv2 kernel: raid5:md3: read error corrected (8 sectors at 76388344 on sdd)
> Jul 14 23:38:48 filesrv2 -- MARK --
> CPU 5: Machine Check Exception: 0000000000000004
> CPU 4: Machine Check Exception: 0000000000000004

And at some point at least 18 minutes after the raid incident you log
CPU problems.

Are you sure the box or the room it is in didn't get excessively hot ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/