{"id":176,"date":"2018-04-25T12:08:53","date_gmt":"2018-04-25T11:08:53","guid":{"rendered":"http:\/\/slackware.wp.w3.pt\/?p=176"},"modified":"2018-12-21T22:07:40","modified_gmt":"2018-12-21T21:07:40","slug":"176","status":"publish","type":"post","link":"http:\/\/slackware.pt\/?p=176","title":{"rendered":"Recuperar RAID 1"},"content":{"rendered":"

Tive problemas com o RAID de uma das m\u00e1quinas. Por algum motivo, um dos discos saltou fora do RAID 1.
\nFui \u00e0 procura na net e encontrei dois s\u00edtios com informa\u00e7\u00e3o importante:
\nReplacing A Failed Hard Drive In A Software RAID1 Array<\/a>
\nHow to check ‘mdadm’ RAIDs while running?<\/a><\/p>\n

Ao emitir o comando cat \/proc\/mdstat<\/code> o resultado foi o seguinte:<\/p>\n

md2 : active raid1 sdf1[1] sde1[0]\r\n      1953512400 blocks super 1.2 [2\/2] [UU]\r\n\r\nmd3 : active raid1 sdd1[1]\r\n      1953512400 blocks super 1.2 [2\/1] [_U]\r\n\r\nmd0 : active raid1 sda3[0] sdb3[1]\r\n      73939072 blocks [2\/2] [UU]<\/pre>\n
No md3<\/strong> faltava o sdc1<\/strong>. Se estivesse l\u00e1, mas com erro, teria que ser removido primeiro, com os comandos seguintes:<\/p>\n
mdadm --manage \/dev\/md3 --fail \/dev\/sdc1
\nmdadm --manage \/dev\/md3 --remove \/dev\/sdc1<\/code><\/p>\n
E depois, desligaria a m\u00e1quina e, se o disco estivesse mesmo avariado, trocaria o disco.
\n\u00c9 necess\u00e1rio criar uma parti\u00e7\u00e3o igual \u00e0 da parti\u00e7\u00e3o sdd1<\/strong>. Para comparar as parti\u00e7\u00f5es, emitir o comando fdisk -l<\/code>, cujo resultado, para os discos em causa, \u00e9:<\/p>\n
Disk \/dev\/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors\r\nUnits: sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 4096 bytes\r\nI\/O size (minimum\/optimal): 4096 bytes \/ 4096 bytes\r\nDisklabel type: dos\r\nDisk identifier: 0x98f9dba0\r\n\r\nDevice     Boot Start        End    Sectors  Size Id Type\r\n\/dev\/sdc1        2048 3907029167 3907027120  1.8T fd Linux raid autodetect\r\n\r\n\r\nDisk \/dev\/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors\r\nUnits: sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 4096 bytes\r\nI\/O size (minimum\/optimal): 4096 bytes \/ 4096 bytes\r\nDisklabel type: dos\r\nDisk identifier: 0xbe1f7c22\r\n\r\nDevice     Boot Start        End    Sectors  Size Id Type\r\n\/dev\/sdd1        2048 3907029167 3907027120  1.8T fd Linux raid autodetect<\/pre>\n
A partir da\u00ed, e para recolocar o disco novamente no RAID, o comando \u00e9 o seguinte:<\/p>\n
mdadm --manage \/dev\/md3 --add \/dev\/sdc1<\/code><\/p>\n
A reconstru\u00e7\u00e3o do RAID \u00e9 iniciada. Pode-se ir acompanhando o processo com o comando cat \/proc\/mdstat<\/code><\/p>\n
md2 : active raid1 sdf1[1] sde1[0]\r\n      1953512400 blocks super 1.2 [2\/2] [UU]\r\n\r\nmd3 : active raid1 sdc1[2] sdd1[1]\r\n      1953512400 blocks super 1.2 [2\/1] [_U]\r\n      [=============>.......]  recovery = 66.1% (1291278848\/1953512400) finish=142.0min speed=77670K\/sec\r\n\r\nmd0 : active raid1 sda3[0] sdb3[1]\r\n      73939072 blocks [2\/2] [UU]\r\n<\/pre>\n
ou ent\u00e3o com o comando mdadm -D \/dev\/md3<\/code>:<\/p>\n
\/dev\/md3:\r\n        Version : 1.2\r\n  Creation Time : Sat Mar 10 21:20:35 2012\r\n     Raid Level : raid1\r\n     Array Size : 1953512400 (1863.01 GiB 2000.40 GB)\r\n  Used Dev Size : 1953512400 (1863.01 GiB 2000.40 GB)\r\n   Raid Devices : 2\r\n  Total Devices : 2\r\n    Persistence : Superblock is persistent\r\n\r\n    Update Time : Wed Apr 25 12:51:45 2018\r\n          State : clean, degraded, recovering\r\n Active Devices : 1\r\nWorking Devices : 2\r\n Failed Devices : 0\r\n  Spare Devices : 1\r\n\r\n Rebuild Status : 65% complete\r\n\r\n           Name : tao:3\r\n           UUID : 90d1dc37:d4fd77a4:a4a1d0fe:98a3717d\r\n         Events : 68048\r\n\r\n    Number   Major   Minor   RaidDevice State\r\n       2       8       33        0      spare rebuilding   \/dev\/sdc1\r\n       1       8       49        1      active sync   \/dev\/sdd1\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"
Tive problemas com o RAID de uma das m\u00e1quinas. Por algum motivo, um dos discos saltou fora do RAID 1. Fui \u00e0 procura na net e encontrei dois s\u00edtios com informa\u00e7\u00e3o importante: Replacing A Failed Hard Drive In A Software RAID1 Array How to check ‘mdadm’ RAIDs while running? Ao emitir o comando cat \/proc\/mdstat … <\/p>\n
Continuar a ler “Recuperar RAID 1”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"http:\/\/slackware.pt\/index.php?rest_route=\/wp\/v2\/posts\/176"}],"collection":[{"href":"http:\/\/slackware.pt\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/slackware.pt\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/slackware.pt\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/slackware.pt\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=176"}],"version-history":[{"count":6,"href":"http:\/\/slackware.pt\/index.php?rest_route=\/wp\/v2\/posts\/176\/revisions"}],"predecessor-version":[{"id":250,"href":"http:\/\/slackware.pt\/index.php?rest_route=\/wp\/v2\/posts\/176\/revisions\/250"}],"wp:attachment":[{"href":"http:\/\/slackware.pt\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=176"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/slackware.pt\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=176"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/slackware.pt\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=176"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}