Inactive-Array RAID5

darkengel02 · 19. Oktober 2015

Hello guys, I have a serious problem with a RAID5, this content full 3x4TB HD, so I need fix without loosing data, please help me with this hard work. Some details:

Code

cat /proc/mdstat: 
Personalities : 
md0 : inactive sdd[0](S) sdc[1](S)
      7813775024 blocks super 1.2

unused devices: <none>

Code

blkid:
/dev/sda1: UUID="36b09d97-b3d9-468f-874d-cf3eced0e1da" TYPE="ext4" PARTUUID="0009e9b4-01" 
/dev/sda5: UUID="ab4934a4-850d-45be-81aa-94bd123613b2" TYPE="swap" PARTUUID="0009e9b4-05" 
/dev/sdd: UUID="c6178cc8-262f-56df-e588-2c97e7aa2e6c" UUID_SUB="4f3aba4b-d752-8496-6dab-e164f4b6d617" LABEL="PRODUCCION:Produccion" TYPE="linux_raid_member" 
/dev/sdc: UUID="c6178cc8-262f-56df-e588-2c97e7aa2e6c" UUID_SUB="bdc0334a-063d-8f1e-b3f0-519c683d01b1" LABEL="PRODUCCION:Produccion" TYPE="linux_raid_member" 
/dev/sdb1: PARTLABEL="LDM metadata partition" PARTUUID="bfad6539-ecbe-11e3-b8f5-0010c6b06aae" 
/dev/sdb2: PARTLABEL="Microsoft reserved partition" PARTUUID="986e2150-2926-4fcb-87bb-a10f7bbb93d2" 
/dev/sdb3: PARTLABEL="LDM data partition" PARTUUID="bfad653c-ecbe-11e3-b8f5-0010c6b06aae"

Code

fdisk -l


Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 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: 0x0009e9b4


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048   224860159   112429056   83  Linux
/dev/sda2       224862206   234440703     4789249    5  Extended
/dev/sda5       224862208   234440703     4789248   82  Linux swap / Solaris


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


Disk /dev/sdb: 4000.8 GB, 4000787030016 bytes
256 heads, 63 sectors/track, 484501 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: 0xfd4845fa


   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


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
256 heads, 63 sectors/track, 484501 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: 0x2daf559a


   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


Disk /dev/sdc: 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: 0x389fd616


   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1            2048   976752639   488375296    7  HPFS/NTFS/exFAT

Alles anzeigen

Thank you in advance.

ryecoaaron · 19. Oktober 2015

mdadm --stop /dev/md0
mdadm --assemble /dev/md0 /dev/sd[bcd] --verbose --force

darkengel02 · 19. Oktober 2015

Thanks @ryecoaaron always for your support, I did and show this:

Code

mdadm --assemble /dev/md0 /dev/sd[bcd] --verbose --force
mdadm: looking for devices for /dev/md0
mdadm: Cannot assemble mbr metadata on /dev/sdb
mdadm: /dev/sdb has no superblock - assembly aborted

ryecoaaron · 19. Oktober 2015

Try:

mdadm --zero-superblock /dev/sdb (probably will say it doesn't have a superblock but just in case)
dd if=/dev/zero of=/dev/sdb bs=512 count=100000
mdadm --assemble /dev/md0 /dev/sd[bcd] --verbose --force

darkengel02 · 19. Oktober 2015

No results, same message:

Code

mdadm --zero-superblock /dev/sdb
mdadm: Unrecognised md component device - /dev/sdb

Code

dd if=/dev/zero of=/dev/sdb bs=512 count=100000
100000+0 records in
100000+0 records out
51200000 bytes (51 MB) copied, 1.81299 s, 28.2 MB/s

Code

mdadm --assemble /dev/md0 /dev/sd[bcd] --verbose --force
mdadm: looking for devices for /dev/md0
mdadm: no recogniseable superblock on /dev/sdb
mdadm: /dev/sdb has no superblock - assembly aborted

sdb disc still alive?

ryecoaaron · 19. Oktober 2015

It shows up in fdisk and allows you to dd to it. Should be fine relatively ok.

Try:

mdadm --assemble /dev/md0 /dev/sd[cdb] --verbose --force

darkengel02 · 19. Oktober 2015

Same result:

Code

mdadm --assemble /dev/md0 /dev/sd[cdb] --verbose --force
mdadm: looking for devices for /dev/md0
mdadm: no recogniseable superblock on /dev/sdb
mdadm: /dev/sdb has no superblock - assembly aborted

darkengel02 · 19. Oktober 2015

@ryecoaaron I could started the array with:

Code

mdadm --assemble /dev/md0 /dev/sd[cd] --verbose --force
mdadm: looking for devices for /dev/md0
mdadm: /dev/sdc is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdd is identified as a member of /dev/md0, slot 0.
mdadm: Marking array /dev/md0 as 'clean'
mdadm: added /dev/sdd to /dev/md0 as 0
mdadm: no uptodate device for slot 4 of /dev/md0
mdadm: added /dev/sdc to /dev/md0 as 1
mdadm: /dev/md0 has been started with 2 drives (out of 3)

I think /dev/sdb has a file system problem, this drive its the first of the array (I supose), is risky work like this? What would be more advisable to do?

I Array Management I have able the Repair button, may can fix the /dev/sdb drive?

ryecoaaron · 20. Oktober 2015

raid doesn't use filesystems. The filesystems are on top of raid and that isn't your problem. The dd command I gave you should wipe the drive. If it still isn't working, I'm not sure I would trust it.

darkengel02 · 20. Oktober 2015

The RAID still working now, with 2 drives, so the /dev/sdb its clean now with the command dd? What I do now with this drive? I'd like to add to the array, to have protection, it is a new drive, 2 WDC drives are new and the ST4000 drive its 3 years old. Can i do that? How?

ryecoaaron · 20. Oktober 2015

From the web interface, click the grow button and add sdb.

darkengel02 · 20. Oktober 2015

I dont have able the grow button, but rescue yes, if I push it I will lose data? See attache please.

ryecoaaron · 20. Oktober 2015

rescue should work. If you are really worried about it, backup data from the degraded array before doing this. Remember, raid isn't backup...

Jetzt mitmachen!