Why not just --set-faulty or --fail with mdadm?
This is not about testing, but about real errors.
1) I depend on the md layer to tell me if a disk is faulty ... failing
the disk manually would only help if I already knew the disk was
faulty and just wanted to remove it.
2) If the affected arra
For ICH5 and all other controllers (non-AHCI) of course, I've always seen
md mark it faulty on a bad disk/sector/etc.
ICH7 (ahci) does not. At least not a whole disk dieing, don't know
about bad sectors.
I thought you were just trying to mark it faulty manually for the purpose
of rebuilding it
On Tue, 11 Jul 2006, Francois Barre wrote:
2006/7/11, Justin Piszcz <[EMAIL PROTECTED]>:
Why not just --set-faulty or --fail with mdadm?
If you answer to "Bad blocks maybe, can't test that.", I'll say AFAIK,
--set-faulty will only stay at the md layer, and won't go through the
underlying d
2006/7/11, Justin Piszcz <[EMAIL PROTECTED]>:
Why not just --set-faulty or --fail with mdadm?
If you answer to "Bad blocks maybe, can't test that.", I'll say AFAIK,
--set-faulty will only stay at the md layer, and won't go through the
underlying driver (sata here, ata elsewhere, ...), so this
Why not just --set-faulty or --fail with mdadm?
On Mon, 10 Jul 2006, Christian Pernegger wrote:
I'm (still) trying to setup a md array on the ICH7 SATA controller of
an Intel SE7230NH1-E with 4 WD5000YS disks.
On this controller (in ahci mode) I have not yet managed to get a disk
mark as faile
I'm (still) trying to setup a md array on the ICH7 SATA controller of
an Intel SE7230NH1-E with 4 WD5000YS disks.
On this controller (in ahci mode) I have not yet managed to get a disk
mark as failed.
- a bad cable just led to hangs and timeouts
- pulling the power on one of the SATA drives (whi
