On Tue, Dec 02, 2014 at 08:14:19PM -0500, David McGuffey wrote:
Received the following message in mail to root:
Message 257:
From root@desk4.localdomain Tue Oct 28 07:25:37 2014
Return-Path: root@desk4.localdomain X-Original-To: root Delivered-To: root@desk4.localdomain From: mdadm monitoring root@desk4.localdomain To: root@desk4.localdomain Subject: DegradedArray event on /dev/md0:desk4 Date: Tue, 28 Oct 2014 07:25:27 -0400 (EDT) Status: RO
This is an automatically generated mail message from mdadm running on desk4
A DegradedArray event had been detected on md device /dev/md0.
Faithfully yours, etc.
P.S. The /proc/mdstat file currently contains the following:
Personalities : [raid1] md0 : active raid1 dm-2[1] 243682172 blocks super 1.1 [2/1] [_U] bitmap: 2/2 pages [8KB], 65536KB chunk
md1 : active raid1 dm-3[0] dm-0[1] 1953510268 blocks super 1.1 [2/2] [UU] bitmap: 3/15 pages [12KB], 65536KB chunk
unused devices: <none>
Could be a bad drive, as digimer alludes in his reply.
OTOH, I had a perfectly good drive get kicked out of my RAID-1 array a fewyears ago just because, well, I guess I could say "it felt like it".
In reality, I had (in my ignorance) purchased a pair of WD drives that aren't intended to be used in a RAID array, and once in a long while (that was actually the only such instance in the 4-5 years I've had that RAID array) it doesn't respond to some HD command or other and gets dropped.
turned out to be easy to reinsert it and it ran for a long time thereafter without trouble.
I can dig for the info on the drives and the nature of the problem if anyone wants to see it.
Fred
<huge snippage>