Thanks :)
I got this yesterday
#################
This is an automatically generated mail message from mdadm running on cu.dgreaves.com
A Fail event had been detected on md device /dev/md0.
#################
Looking at it tonight:
Oct 22 18:09:44 cu kernel: Current sdd: sense key Medium Error Oct 22 18:09:44 cu kernel: Additional sense: Unrecovered read error - auto realloca te failed Oct 22 18:09:44 cu kernel: end_request: I/O error, dev sdd, sector 196988598 Oct 22 18:09:45 cu kernel: scsi3: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 0 0 0b bd ce b7 00 00 01 00 Oct 22 18:09:45 cu kernel: Current sdd: sense key Medium Error Oct 22 18:09:45 cu kernel: Additional sense: Unrecovered read error - auto realloca te failed Oct 22 18:09:45 cu kernel: end_request: I/O error, dev sdd, sector 196988599
The Maxtor Maxline+II 250Gb SATA drive (mfg date: feb 2004) is now out and I'm starting the RMA procedure.
No data lost (yet) so we can still watch TV - thanks everyone (especially Neil)
David
Quoted 8 lines · David Greaves
I got this yesterday
#################
This is an automatically generated mail message from mdadm running on cu.dgreaves.comA Fail event had been detected on md device
/dev/md0.
#################
David,
How have you set things up to achieve this?
R.
Signature · 1 line
http://robinbowes.com
Quoted 7 lines · Robin Bowes
Quoted 6 lines · David Greaves
I got this yesterday
#################
This is an automatically generated mail message from mdadm running on cu.dgreaves.com
Quoted 6 lines
Quoted 2 lines
A Fail event had been detected on md device
/dev/md0.
#################David,
How have you set things up to achieve this?
See the section on Monitor mode (-F option) in the mdadm man page. Debian's mdadm package, for example, sets it up so mdadm -F gets run automatically at boot time to monitor your arrays.
-Steve
Quoted 13 lines · Steven Ihde
Quoted 11 lines · Robin Bowes
Quoted 8 lines · David Greaves
I got this yesterday
#################
This is an automatically generated mail message from mdadm running on cu.dgreaves.comA Fail event had been detected on md device
/dev/md0.
#################
Quoted 8 lines
Quoted 3 lines
David,
How have you set things up to achieve this?
See the section on Monitor mode (-F option) in the mdadm man page. Debian's mdadm package, for example, sets it up so mdadm -F gets run automatically at boot time to monitor your arrays.
Sorry, I wasn't clear enough in my question...
I am aware of mdadms' monitor mode; in fact, I'm sure it used to run when I first started using mdadm (on Fedora Core 2 installed from rpm built myself from src rpm).
I seem to remember that this was disabled at some stage but can't remember the detail - possibly something to do with preventing the array from shutting down cleanly because mdadm -F was open on it.
I am hoping that someone can suggest how best to run mdadm -F on Fedora Core 2. Perhaps it could be as simple as creating a script in /etc/init.d/ which would terminate before the array is shutdown?
R.
Signature · 1 line
http://robinbowes.com