{"id":1138,"date":"2012-09-30T06:34:23","date_gmt":"2012-09-30T05:34:23","guid":{"rendered":"http:\/\/blog.spanger.org\/?p=1138"},"modified":"2012-10-09T16:40:36","modified_gmt":"2012-10-09T15:40:36","slug":"replace-failed-disk-in-raid-1","status":"publish","type":"post","link":"https:\/\/blog.spanger.org\/?p=1138","title":{"rendered":"replace failed disk in raid 1"},"content":{"rendered":"

SCENARIO:<\/p>\n

OS: linux debian 6<\/p>\n

Software Raid: raid 1 created with mdadm<\/p>\n

Failed drive: sata drive (\/dev\/sda) of size 500Gb<\/p>\n

New drive: same size or bigger sata drive. In my case 1Tb sata drive<\/p>\n

WHAT TO DO:<\/p>\n

1. Shutdown server,
\n2. Replace failed disk,
\n3. Start server,
\n4. Rebuild Raid 1,
\n5. Update grub.<\/p>\n

LOOK FOR WORKING DISK<\/p>\n

With fdisk I looked how is active disk in Raid 1 configured.<\/p>\n

\r\nroot@server:~# fdisk \/dev\/sdb <\/code>\r\nCommand (m for help): p <\/code>\r\n\r\nDevice Boot Start End Blocks Id System <\/code>\r\n\/dev\/sdb1 * 1 13 104391 fd Linux raid autodetect <\/code>\r\n\/dev\/sdb2 14 293 2249100 fd Linux raid autodetect <\/code>\r\n\/dev\/sdb3 294 60801 486030510 fd Linux raid autodetec <\/code><\/pre>\n
I used fdisk to create same size raid partitions on new disk:<\/p>\n
PREPARE NEW DISK<\/p>\n
# fdisk \/dev\/sda<\/code>\r\nn p 1 \r\nn p 2\r\nn p 3\r\n\r\nn - new partition\r\np - primary partition\r\nt - type of partition (used fd (Linux raid) for all 3 partitions on disk \/dev\/sda)\r\na - add bootable flag to first partition\r\nw - write changes to disk<\/pre>\n
REBUILD RAID 1 with MDADM:<\/p>\n
# mdadm \/dev\/md0 -a \/dev\/sda1 <\/code><\/pre>\n
NEW DISK:<\/p>\n
root@server:~# fdisk \/dev\/sda <\/code>\r\nCommand (m for help): p <\/code>\r\nDevice Boot Start End Blocks Id System <\/code>\r\n\/dev\/sda1 * 1 13 104391 fd Linux raid autodetect <\/code>\r\n\/dev\/sda2 14 293 2249100 fd Linux raid autodetect <\/code>\r\n\/dev\/sda3 294 60801 486030510 fd Linux raid autodetect <\/code><\/pre>\n
BUILDING RAID 1:<\/p>\n
\r\nroot@server:~# cat \/proc\/mdstat <\/code>\r\nPersonalities : [raid1] <\/code>\r\nmd2 : active raid1 sda3[2] sdb3[1] 486030400 blocks [2\/1] [_U] [==>..................] recovery = 14.0% (68114752\/486030400) finish=147.5min speed=47214K\/sec <\/code>\r\nmd1 : active raid1 sda2[0] sdb2[1] 2249024 blocks [2\/2] [UU] <\/code>\r\nmd0 : active raid1 sda1[0] sdb1[1] 104320 blocks [2\/2] [UU] <\/code>\r\nunused devices: <\/code><\/pre>\n
ALL DISKS UP AND RUNNING<\/p>\n
\r\nroot@server:~# cat \/proc\/mdstat Personalities : [raid1] <\/code>\r\nmd2 : active raid1 sda3[0] sdb3[1] 486030400 blocks [2\/2] [UU] <\/code>\r\nmd1 : active raid1 sda2[0] sdb2[1] 2249024 blocks [2\/2] [UU] <\/code>\r\nmd0 : active raid1 sda1[0] sdb1[1] 104320 blocks [2\/2] [UU] <\/code>\r\nunused devices: <\/code><\/pre>\n
UPDATE CONFIGURATION<\/p>\n
# mdadm --examine --scan > \/etc\/mdadm.conf<\/code><\/pre>\n
GRUB INSTALL\/UPDATE ON NEW DISK<\/p>\n
\r\n# grub-install \/dev\/sda <\/code>\r\n# update-grub \/dev\/sda <\/code><\/pre>\n
Example of howto remove a failed disk from array:<\/p>\n
\r\n# mdadm --fail \/dev\/md0 \/dev\/sdb3<\/code>\r\n# mdadm --remove \/dev\/md0 \/dev\/sdb3 <\/code><\/pre>\n
IF PROBLEMS WITH update-grub … update-grub failed with no such disk … <\/p>\n
SOLUTION <\/p>\n
# mv \/boot\/grub\/device.map \/boot\/grub\/device.map.old <\/code>\r\n# update-grub <\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"
SCENARIO: OS: linux debian 6 Software Raid: raid 1 created with mdadm Failed drive: sata drive (\/dev\/sda) of size 500Gb New drive: same size or bigger sata drive. In my case 1Tb sata drive WHAT TO DO: 1. Shutdown server, 2. Replace failed disk, 3. Start server, 4. Rebuild Raid 1, 5. Update grub. LOOK […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[122,123,121,120,119],"class_list":["post-1138","post","type-post","status-publish","format-standard","hentry","category-linux-stuff","tag-bigger-drive","tag-failed-drive","tag-fdisk","tag-mdadm","tag-raid-1"],"_links":{"self":[{"href":"https:\/\/blog.spanger.org\/index.php?rest_route=\/wp\/v2\/posts\/1138","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.spanger.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.spanger.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.spanger.org\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.spanger.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1138"}],"version-history":[{"count":58,"href":"https:\/\/blog.spanger.org\/index.php?rest_route=\/wp\/v2\/posts\/1138\/revisions"}],"predecessor-version":[{"id":1152,"href":"https:\/\/blog.spanger.org\/index.php?rest_route=\/wp\/v2\/posts\/1138\/revisions\/1152"}],"wp:attachment":[{"href":"https:\/\/blog.spanger.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1138"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.spanger.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1138"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.spanger.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1138"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}