lost raid5 after upgrade

Plato · 22. Februar 2017

Hello,
I lost my raid 5 after upgrade from 3x 3TB WD RED to 4x 3TB WD RED.

What can I do ?

thanks

Code

root@homeserver:~# cat /proc/mdstat
Personalities : 
unused devices: <none>

Code

root@homeserver:~# blkid
/dev/sda1: UUID="ae3814b4-8d73-42ba-9753-147b8bde8b51" TYPE="ext4" PARTUUID="021fa056-01"
/dev/sda5: UUID="dd9e6b44-2cf2-449b-8d73-4f22c1cd42ef" TYPE="swap" PARTUUID="021fa056-05"
/dev/sdc: UUID="2ea7d2ce-18e9-a774-0cd3-1ec1faec10e6" UUID_SUB="340e5ad9-9a84-fc29-586b-556426b5213e" LABEL="homeserver:home" TYPE="linux_raid_member"
/dev/sdb: UUID="2ea7d2ce-18e9-a774-0cd3-1ec1faec10e6" UUID_SUB="86dd334c-7935-a967-076b-498f71bcb020" LABEL="homeserver:home" TYPE="linux_raid_member"
/dev/sdd: UUID="2ea7d2ce-18e9-a774-0cd3-1ec1faec10e6" UUID_SUB="85df4f7f-2767-277e-1973-ed632390a732" LABEL="homeserver:home" TYPE="linux_raid_member"
/dev/sde: UUID="2ea7d2ce-18e9-a774-0cd3-1ec1faec10e6" UUID_SUB="15ffcf7f-6dae-d734-ceb2-bb5a6efd1250" LABEL="homeserver:home" TYPE="linux_raid_member"
root@homeserver:~#

Code

root@homeserver:~# fdisk -l | grep "Disk "
The primary GPT table is corrupt, but the backup appears OK, so that will be used.
The primary GPT table is corrupt, but the backup appears OK, so that will be used.
The primary GPT table is corrupt, but the backup appears OK, so that will be used.
Disk /dev/sda: 7,5 GiB, 8019099648 bytes, 15662304 sectors
Disk identifier: 0x021fa056
Disk /dev/sdc: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk identifier: 96F8561E-BC29-4020-AADB-85DBEA44302D
Disk /dev/sdb: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk identifier: BAE1AF78-6E5B-475B-9310-555C9FDAB418
Disk /dev/sdd: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk /dev/sde: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk identifier: 65002F4F-C6CD-4F47-A468-F303695798B7
root@homeserver:~#

Alles anzeigen

Code: cat /etc/mdadm/mdadm.conf

root@homeserver:~# 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

Alles anzeigen

Code

root@homeserver:~# mdadm --detail --scan --verbose
root@homeserver:~#

HerrVorragend · 23. Februar 2017

Stop raid (maybe not necessary):
mdadm --stop /dev/md0

Put the raid together:
mdadm --assemble /dev/md0 /dev/sdb /dev/sdc /dev/sdd /dev/sde --force

Plato · 23. Februar 2017

root@homeserver:~# mdadm --assemble /dev/md0 /dev/sdb /dev/sdc /dev/sdd /dev/sde --force
mdadm: Failed to restore critical section for reshape, sorry.
Possibly you needed to specify the --backup-file
root@homeserver:~#

he wanted always the backup file

HerrVorragend · 23. Februar 2017

Is the superblock okay?

mdadm --examine /dev/sdb
mdadm --examine /dev/sdc
mdadm --examine /dev/sdd
mdadm --examine /dev/sde

Plato · 23. Februar 2017

here is the data

Code

root@homeserver:~# mdadm --examine /dev/sdb
/dev/sdb:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x5
     Array UUID : 2ea7d2ce:18e9a774:0cd31ec1:faec10e6
           Name : homeserver:home  (local to host homeserver)
  Creation Time : Tue Feb 14 20:42:44 2017
     Raid Level : raid5
   Raid Devices : 4


 Avail Dev Size : 5860271024 (2794.40 GiB 3000.46 GB)
     Array Size : 8790405120 (8383.18 GiB 9001.37 GB)
  Used Dev Size : 5860270080 (2794.39 GiB 3000.46 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262056 sectors, after=944 sectors
          State : clean
    Device UUID : 86dd334c:7935a967:076b498f:71bcb020


Internal Bitmap : 8 sectors from superblock
  Reshape pos'n : 0
  Delta Devices : 1 (3->4)


    Update Time : Wed Feb 22 01:12:11 2017
  Bad Block Log : 512 entries available at offset 72 sectors
       Checksum : a7e82d80 - correct
         Events : 7573


         Layout : left-symmetric
     Chunk Size : 512K


   Device Role : Active device 0
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
root@homeserver:~#

Alles anzeigen

Code

root@homeserver:~# mdadm --examine /dev/sdc
/dev/sdc:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x5
     Array UUID : 2ea7d2ce:18e9a774:0cd31ec1:faec10e6
           Name : homeserver:home  (local to host homeserver)
  Creation Time : Tue Feb 14 20:42:44 2017
     Raid Level : raid5
   Raid Devices : 4


 Avail Dev Size : 5860271024 (2794.40 GiB 3000.46 GB)
     Array Size : 8790405120 (8383.18 GiB 9001.37 GB)
  Used Dev Size : 5860270080 (2794.39 GiB 3000.46 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262056 sectors, after=944 sectors
          State : clean
    Device UUID : 340e5ad9:9a84fc29:586b5564:26b5213e


Internal Bitmap : 8 sectors from superblock
  Reshape pos'n : 0
  Delta Devices : 1 (3->4)


    Update Time : Wed Feb 22 01:12:11 2017
  Bad Block Log : 512 entries available at offset 72 sectors
       Checksum : e9dea656 - correct
         Events : 7573


         Layout : left-symmetric
     Chunk Size : 512K


   Device Role : Active device 1
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
root@homeserver:~#

Alles anzeigen

Code

root@homeserver:~# mdadm --examine /dev/sdd
/dev/sdd:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x5
     Array UUID : 2ea7d2ce:18e9a774:0cd31ec1:faec10e6
           Name : homeserver:home  (local to host homeserver)
  Creation Time : Tue Feb 14 20:42:44 2017
     Raid Level : raid5
   Raid Devices : 4


 Avail Dev Size : 5860271024 (2794.40 GiB 3000.46 GB)
     Array Size : 8790405120 (8383.18 GiB 9001.37 GB)
  Used Dev Size : 5860270080 (2794.39 GiB 3000.46 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262056 sectors, after=944 sectors
          State : clean
    Device UUID : 85df4f7f:2767277e:1973ed63:2390a732


Internal Bitmap : 8 sectors from superblock
  Reshape pos'n : 0
  Delta Devices : 1 (3->4)


    Update Time : Wed Feb 22 01:12:11 2017
  Bad Block Log : 512 entries available at offset 72 sectors
       Checksum : d81d3cf4 - correct
         Events : 7573


         Layout : left-symmetric
     Chunk Size : 512K


   Device Role : Active device 3
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
root@homeserver:~#

Alles anzeigen

Code

root@homeserver:~# mdadm --examine /dev/sde
/dev/sde:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x5
     Array UUID : 2ea7d2ce:18e9a774:0cd31ec1:faec10e6
           Name : homeserver:home  (local to host homeserver)
  Creation Time : Tue Feb 14 20:42:44 2017
     Raid Level : raid5
   Raid Devices : 4


 Avail Dev Size : 5860271024 (2794.40 GiB 3000.46 GB)
     Array Size : 8790405120 (8383.18 GiB 9001.37 GB)
  Used Dev Size : 5860270080 (2794.39 GiB 3000.46 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262056 sectors, after=944 sectors
          State : clean
    Device UUID : 15ffcf7f:6daed734:ceb2bb5a:6efd1250


Internal Bitmap : 8 sectors from superblock
  Reshape pos'n : 0
  Delta Devices : 1 (3->4)


    Update Time : Wed Feb 22 01:12:11 2017
  Bad Block Log : 512 entries available at offset 72 sectors
       Checksum : a38750c9 - correct
         Events : 7573


         Layout : left-symmetric
     Chunk Size : 512K


   Device Role : Active device 2
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
root@homeserver:~#

Alles anzeigen

ryecoaaron · 23. Februar 2017

Use the --force flag when re-asssembling.

Plato · 23. Februar 2017

sorry, what do you meen ? I am noob for linux system...

ryecoaaron · 23. Februar 2017

Nevermind. I didn't see the force flag at the end of the command.

Plato · 23. Februar 2017

any ideas ???

Code

root@homeserver:~# mdadm --assemble /dev/md0 --verbose --invalid-backup --force --uuid=2ea7d2ce:18e9a774:0cd31ec1:faec10e6
mdadm: looking for devices for /dev/md0
mdadm: no RAID superblock on /dev/sda5
mdadm: no RAID superblock on /dev/sda2
mdadm: no RAID superblock on /dev/sda1
mdadm: no RAID superblock on /dev/sda
mdadm: /dev/sdc is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sde is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdd is identified as a member of /dev/md0, slot 3.
mdadm: /dev/sdb is identified as a member of /dev/md0, slot 0.
mdadm: :/dev/md0 has an active reshape - checking if critical section needs to be restored
mdadm: No backup metadata on device-3
mdadm: Failed to find backup of critical section
mdadm: continuing without restoring backup
mdadm: added /dev/sdc to /dev/md0 as 1
mdadm: added /dev/sde to /dev/md0 as 2
mdadm: added /dev/sdd to /dev/md0 as 3
mdadm: added /dev/sdb to /dev/md0 as 0
mdadm: failed to RUN_ARRAY /dev/md0: Invalid argument
root@homeserver:~#

Alles anzeigen

Code

root@homeserver:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] 
unused devices: <none>
root@homeserver:~

HerrVorragend · 23. Februar 2017

https://www.cyberciti.biz/faq/…-devmd0-invalid-argument/

Plato · 23. Februar 2017

thanks, but doesn't help

Jetzt mitmachen!