Raid 5 with 3 X 2TB with one faulty drive. By accident removed working drive. Now i cannot add it no more

pjdw · 6. Mai 2016

See subject.

By accident i have replace an ok drive (sdb) instead of the faulty one (sdc). I have removed the new drive from sdb and replace it with the old working one, but i cannot add it to my raid again

Code

cat /proc/mdstat


Personalities : [raid6] [raid5] [raid4] 


md126 : inactive sdb[3](S)
      1953513560 blocks super 1.2



md127 : active raid5 sda[4] sdc[5]
      3907025920 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [U_U]



unused devices: <none>


blkid


/dev/sda: UUID="aa789f1f-9ada-cd98-0f24-ecb1ee193f29" UUID_SUB="ddbb5d98-40e4-becb-8d35-296b8fb57461" LABEL="openmediavault:Raid3x2TB" TYPE="linux_raid_member" 


/dev/sdd1: LABEL="EFI" UUID="70D6-1701" TYPE="vfat" 


/dev/md127: LABEL="Raid3x2TB" UUID="ae878cf6-eeae-4bce-83ac-10a1493c58f4" TYPE="ext4" 


/dev/sdd2: UUID="5be99670-56a0-3841-8f30-c92b109c15ee" TYPE="hfsplus" 


/dev/sde1: UUID="1d55a892-e06a-452c-a488-c2c6781eb4be" TYPE="ext4" 


/dev/sde5: UUID="712c0e11-e1a3-4156-bf5f-b8766f47dcf8" TYPE="swap" 


/dev/sdc: UUID="aa789f1f-9ada-cd98-0f24-ecb1ee193f29" UUID_SUB="4943294b-49d8-1e03-efe9-f98a3ea30e42" LABEL="openmediavault:Raid3x2TB" TYPE="linux_raid_member" 


/dev/sdb: UUID="aa789f1f-9ada-cd98-0f24-ecb1ee193f29" UUID_SUB="50a8e98d-7f3e-e899-4fac-dd2eb344320a" LABEL="openmediavault:Raid3x2TB" TYPE="linux_raid_member" 


fdisk -l


WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes


256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System


/dev/sda1               1  3907029167  1953514583+  ee  GPT


Partition 1 does not start on physical sector boundary.


Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes


255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x00000000


Disk /dev/sdb doesn't contain a valid partition table


Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes


255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x00000000


Disk /dev/sdc doesn't contain a valid partition table


WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdd: 4000.8 GB, 4000787030016 bytes


255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System


/dev/sdd1               1  4294967294  2147483647   ee  GPT


Partition 1 does not start on physical sector boundary.


Disk /dev/sde: 60.0 GB, 60022480896 bytes


255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 512 bytes


I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk identifier: 0x000ae97d


   Device Boot      Start         End      Blocks   Id  System


/dev/sde1   *        2048   112383999    56190976   83  Linux


/dev/sde2       112386046   117229567     2421761    5  Extended


/dev/sde5       112386048   117229567     2421760   82  Linux swap / Solaris


Disk /dev/md127: 4000.8 GB, 4000794542080 bytes


2 heads, 4 sectors/track, 976756480 cylinders, total 7814051840 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 524288 bytes / 1048576 bytes


Disk identifier: 0x00000000


Disk /dev/md127 doesn't contain a valid partition table


cat /etc/mdadm/mdadm.conf


# mdadm.conf


#


# Please refer to mdadm.conf(5) for information about this file.


#


# by default, scan all partitions (/proc/partitions) for MD superblocks.


# alternatively, specify devices to scan, using wildcards if desired.


# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.


# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is


# used if no RAID devices are configured.


DEVICE partitions


# auto-create devices with Debian standard permissions


CREATE owner=root group=disk mode=0660 auto=yes


# automatically tag new arrays as belonging to the local system


HOMEHOST <system>


# definitions of existing MD arrays


ARRAY /dev/md/Raid3x2TB metadata=1.2 spares=1 name=openmediavault:Raid3x2TB UUID=aa789f1f:9adacd98:0f24ecb1:ee193f29


mdadm --detail --scan --verbose


ARRAY /dev/md/Raid3x2TB level=raid5 num-devices=3 metadata=1.2 name=openmediavault:Raid3x2TB UUID=aa789f1f:9adacd98:0f24ecb1:ee193f29
   devices=/dev/sda,/dev/sdc


ARRAY /dev/md/Raid3x2TB level=raid5 num-devices=3 metadata=1.2 name=openmediavault:Raid3x2TB UUID=aa789f1f:9adacd98:0f24ecb1:ee193f29
   devices=/dev/sda,/dev/sdc

Alles anzeigen

ryecoaaron · 6. Mai 2016

mdadm --stop /dev/md126
mdadm --stop /dev/md127
mdadm --assemble --force --verbose /dev/md127 /dev/sd[abc]

pjdw · 6. Mai 2016

unmount before stopping worked to stop, but i still have only a & c in my raid hmmmmm

Code

umount /dev/md127


root@n40lomv:/# sudo mdadm --stop /dev/md127


mdadm: stopped /dev/md127


root@n40lomv:/# mdadm --assemble --force --verbose /dev/md127 /dev/sd[abc]


mdadm: looking for devices for /dev/md127


mdadm: /dev/sda is identified as a member of /dev/md127, slot 0.


mdadm: /dev/sdb is identified as a member of /dev/md127, slot 1.


mdadm: /dev/sdc is identified as a member of /dev/md127, slot 2.


mdadm: added /dev/sdb to /dev/md127 as 1 (possibly out of date)


mdadm: added /dev/sdc to /dev/md127 as 2


mdadm: added /dev/sda to /dev/md127 as 0


mdadm: /dev/md127 has been started with 2 drives (out of 3).

Alles anzeigen

ryecoaaron · 7. Mai 2016

Must be something wrong with sdb then. You don't have to use sudo when you are logged in as root either.

Assuming you have a backup, you could try:

mdadm --stop /dev/md127
dd if=/dev/zero of=/dev/sdb bs=512 count=100000
mdadm --assemble --force --verbose /dev/md127 /dev/sd[abc]

Dropkick Murphy · 7. Mai 2016

Maybe defective superblock on sdb. Look here: http://superuser.com/questions…ossibly-out-of-date-disks
Zeroing the superblock did the trick there:

Zitat

mdadm --zero-superblock

Alas, you should have a backup if you work with that stuff...

HTH

pjdw · 7. Mai 2016

I have an old backup and now in the proces of refreshing. Then i wil do the dd thing. Thanks for help again!
So when you do su and have root privileges sudo does not solve problems; keep than in mind

The suggestion from rye gave me this:

Code

umount /dev/md127


root@n40lomv:/# mdadm --stop /dev/md127


mdadm: stopped /dev/md127


root@n40lomv:/# dd if=/dev/zero of=/dev/sdb bs=512 count=100000


100000+0 records gelezen


100000+0 records geschreven


51200000 bytes (51 MB) gekopieerd, 3,70477 s, 13,8 MB/s


root@n40lomv:/# mdadm --assemble --force --verbose /dev/md127 /dev/sd[abc]


mdadm: looking for devices for /dev/md127


mdadm: no RAID superblock on /dev/sdb


mdadm: /dev/sdb has no superblock - assembly aborted

Alles anzeigen

I rebooted the system couple of times and wiped b. It is rebuilding. What happened i don't know.
SDC still has a red status. After rebuild i will swap it with a spare one.

Jetzt mitmachen!