# Re-adding failed drive in mdadm

DevFeed: [Re-adding failed drive in mdadm](<https://devfeed.tech/articles/re-adding-failed-drive-in-mdadm-27600.md>)

Original publisher: [Read original article](<https://gagor.pro/2013/12/re-adding-failed-drive-in-mdadm/>)

Author: Tom

Published: 2013-12-12T00:00:00Z

Content type: tutorial

Language: en

Sources: [Tomasz Gągor](<https://devfeed.tech/sources/tomasz-gagor.md>)

Topics: [Mdadm](<https://devfeed.tech/topics/mdadm.md>), [DRIVE](<https://devfeed.tech/topics/drive.md>)

Tags: [array](<https://devfeed.tech/tags/array.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [failed](<https://devfeed.tech/tags/failed.md>), [i](<https://devfeed.tech/tags/i.md>), [issue](<https://devfeed.tech/tags/issue.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mdadm](<https://devfeed.tech/tags/mdadm.md>), [raid](<https://devfeed.tech/tags/raid.md>)

## AI overview

A practical account of re-adding a previously failed drive to an mdadm RAID5 array after a hot spare had rebuilt the array. The author reports testing the drive, adding it as a spare, failing the slower replacement drive, removing it, and re-adding the tested drive.

## Source excerpt

Yesterday I have problem with fglrx witch cause ugly system reset. After that, one of my drives was marked as failed in RAID5 array. Hotspare was automatically used to rebuild array. But this hotspare is the oldest and slowest drive I've got... After rebuild I've tested failed drive and it was fine - no bad block, no any other issue - so I wanted it running back in array. What I do: