[RAID5] Missing superblocks after restart

    • OMV 1.0
    • [RAID5] Missing superblocks after restart

      Dear community,
      another victim of RAID is hoping for your advice :)

      It is concerning RAID5 using 3 disks (sdb,sdc,sdd) which somehow disappeared :/


      Source Code

      1. root@overlord:~# cat /proc/mdstat
      2. Personalities :
      3. unused devices: <none>

      Source Code

      1. root@overlord:~# blkid
      2. /dev/mapper/overlord-swap_1: UUID="8663f4e6-7f8c-4033-885d-8d08e30104b7" TYPE="swap"
      3. /dev/sda5: UUID="f0650d86-91f3-477a-8b10-8e3ae13c712f" TYPE="crypto_LUKS"
      4. /dev/sda1: UUID="dc9db794-79b6-462d-a806-9b621bb5c9b8" TYPE="ext2"
      5. /dev/mapper/sda5_crypt: UUID="0vOaS2-131i-2Xhd-SWnu-Fo7h-1ORq-7bvYEV" TYPE="LVM2_member"
      6. /dev/mapper/overlord-root: UUID="9896bb07-cd74-49a1-9420-109ecf3eb612" TYPE="ext4"

      Source Code

      1. root@overlord:~# fdisk -l
      2. WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
      3. Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
      4. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      5. Units = sectors of 1 * 512 = 512 bytes
      6. Sector size (logical/physical): 512 bytes / 4096 bytes
      7. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      8. Disk identifier: 0x00000000
      9. Device Boot Start End Blocks Id System
      10. /dev/sdb1 1 4294967295 2147483647+ ee GPT
      11. Partition 1 does not start on physical sector boundary.
      12. Disk /dev/sda: 60.0 GB, 60022480896 bytes
      13. 255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
      14. Units = sectors of 1 * 512 = 512 bytes
      15. Sector size (logical/physical): 512 bytes / 512 bytes
      16. I/O size (minimum/optimal): 512 bytes / 512 bytes
      17. Disk identifier: 0x000f214b
      18. Device Boot Start End Blocks Id System
      19. /dev/sda1 * 2048 499711 248832 83 Linux
      20. /dev/sda2 501758 117229567 58363905 5 Extended
      21. /dev/sda5 501760 117229567 58363904 83 Linux
      22. WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.
      23. Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
      24. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      25. Units = sectors of 1 * 512 = 512 bytes
      26. Sector size (logical/physical): 512 bytes / 4096 bytes
      27. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      28. Disk identifier: 0x00000000
      29. Device Boot Start End Blocks Id System
      30. /dev/sdc1 1 4294967295 2147483647+ ee GPT
      31. Partition 1 does not start on physical sector boundary.
      32. WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.
      33. Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
      34. 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
      35. Units = sectors of 1 * 512 = 512 bytes
      36. Sector size (logical/physical): 512 bytes / 4096 bytes
      37. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      38. Disk identifier: 0x00000000
      39. Device Boot Start End Blocks Id System
      40. /dev/sdd1 1 4294967295 2147483647+ ee GPT
      41. Partition 1 does not start on physical sector boundary.
      42. Disk /dev/mapper/sda5_crypt: 59.8 GB, 59762540544 bytes
      43. 255 heads, 63 sectors/track, 7265 cylinders, total 116723712 sectors
      44. Units = sectors of 1 * 512 = 512 bytes
      45. Sector size (logical/physical): 512 bytes / 512 bytes
      46. I/O size (minimum/optimal): 512 bytes / 512 bytes
      47. Disk identifier: 0x00000000
      48. Disk /dev/mapper/sda5_crypt doesn't contain a valid partition table
      49. Disk /dev/mapper/overlord-root: 57.3 GB, 57289998336 bytes
      50. 255 heads, 63 sectors/track, 6965 cylinders, total 111894528 sectors
      51. Units = sectors of 1 * 512 = 512 bytes
      52. Sector size (logical/physical): 512 bytes / 512 bytes
      53. I/O size (minimum/optimal): 512 bytes / 512 bytes
      54. Disk identifier: 0x00000000
      55. Disk /dev/mapper/overlord-root doesn't contain a valid partition table
      56. Disk /dev/mapper/overlord-swap_1: 2470 MB, 2470445056 bytes
      57. 255 heads, 63 sectors/track, 300 cylinders, total 4825088 sectors
      58. Units = sectors of 1 * 512 = 512 bytes
      59. Sector size (logical/physical): 512 bytes / 512 bytes
      60. I/O size (minimum/optimal): 512 bytes / 512 bytes
      61. Disk identifier: 0x00000000
      62. Disk /dev/mapper/overlord-swap_1 doesn't contain a valid partition table
      Display All

      Source Code

      1. root@overlord:~# lsblk
      2. NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
      3. sdb 8:16 0 2.7T 0 disk
      4. └─sdb1 8:17 0 2.7T 0 part
      5. sda 8:0 0 55.9G 0 disk
      6. ├─sda1 8:1 0 243M 0 part /boot
      7. ├─sda2 8:2 0 1K 0 part
      8. └─sda5 8:5 0 55.7G 0 part
      9. └─sda5_crypt (dm-0) 253:0 0 55.7G 0 crypt
      10. ├─overlord-root (dm-1) 253:1 0 53.4G 0 lvm /
      11. └─overlord-swap_1 (dm-2) 253:2 0 2.3G 0 lvm [SWAP]
      12. sdc 8:32 0 2.7T 0 disk
      13. └─sdc1 8:33 0 2.7T 0 part
      14. sdd 8:48 0 2.7T 0 disk
      15. └─sdd1 8:49 0 2.7T 0 part
      Display All

      Source Code

      1. root@overlord:~# mdadm --examine /dev/sdb
      2. /dev/sdb:
      3. MBR Magic : aa55
      4. Partition[0] : 4294967295 sectors at 1 (type ee)
      5. root@overlord:~# mdadm --examine /dev/sdc
      6. /dev/sdc:
      7. MBR Magic : aa55
      8. Partition[0] : 4294967295 sectors at 1 (type ee)
      9. root@overlord:~# mdadm --examine /dev/sdd
      10. /dev/sdd:
      11. MBR Magic : aa55
      12. Partition[0] : 4294967295 sectors at 1 (type ee)
      13. root@overlord:~#
      Display All
    • There should be no harm in trying:

      mdadm --assemble /dev/md127 /dev/sd[bcd] --verbose --force
      omv 5.1.2 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.7
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • No joy :/

      Source Code

      1. root@overlord:~# mdadm --assemble /dev/md127 /dev/sd[bcd] --verbose --force
      2. mdadm: looking for devices for /dev/md127
      3. mdadm: Cannot assemble mbr metadata on /dev/sdb
      4. mdadm: /dev/sdb has no superblock - assembly aborted
      5. root@overlord:~# mdadm --assemble /dev/md0 /dev/sd[bcd] --verbose --force
      6. mdadm: looking for devices for /dev/md0
      7. mdadm: Cannot assemble mbr metadata on /dev/sdb
      8. mdadm: /dev/sdb has no superblock - assembly aborted
      9. root@overlord:~#


      Looking at the disks themselves, this seems like a mistake with the crypto setup /raid5 growing...
      What do you think?

      Brainfuck Source Code

      1. root@overlord:~# head /dev/sdb | hd
      2. 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      3. *
      4. 000001c0 01 00 ee fe ff ff 01 00 00 00 ff ff ff ff 00 00 |................|
      5. 000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      6. *
      7. 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
      8. 00000200 45 46 49 20 50 41 52 54 00 00 01 00 5c 00 00 00 |EFI PART....\...|
      9. 00000210 08 02 6b bc 00 00 00 00 01 00 00 00 00 00 00 00 |..k.............|
      10. 00000220 af a3 50 5d 01 00 00 00 22 00 00 00 00 00 00 00 |..P]....".......|
      11. 00000230 8e a3 50 5d 01 00 00 00 2e c3 85 55 93 46 82 4f |..P].......U.F.O|
      12. 00000240 92 76 a9 13 72 70 93 bf 02 00 00 00 00 00 00 00 |.v..rp..........|
      13. 00000250 80 00 00 00 80 00 00 00 70 f7 ca df 00 00 00 00 |........p.......|
      14. 00000260 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      15. *
      16. 00000400 0f 88 9d a1 fc 05 3b 4d a0 06 74 3f 0f 84 91 1e |......;M..t?....|
      17. 00000410 87 75 6d 69 41 46 21 40 95 bd ca 92 3e 86 8c 93 |.umiAF!@....>...|
      18. 00000420 00 08 00 00 00 00 00 00 ff 9f 50 5d 01 00 00 00 |..........P]....|
      19. 00000430 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      20. *
      21. 08000000 4c 55 4b 53 ba be 00 01 61 65 73 00 00 00 00 00 |LUKS....aes.....|
      22. 08000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      23. 08000020 00 00 00 00 00 00 00 00 78 74 73 2d 70 6c 61 69 |........xts-plai|
      24. 08000030 6e 36 34 00 00 00 00 00 00 00 00 00 00 00 00 00 |n64.............|
      25. 08000040 00 00 00 00 00 00 00 00 73 68 61 35 31 32 00 00 |........sha512..|
      26. 08000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      27. 08000060 00 00 00 00 00 00 00 00 00 00 10 00 00 00 00 40 |...............@|
      28. 08000070 ea af a6 a9 45 c7 92 38 ba 4e 89 6b c5 ee 07 d8 |....E..8.N.k....|
      29. 08000080 34 d7 3e 3b a2 0d d5 02 d8 69 64 be 79 e3 15 52 |4.>;.....id.y..R|
      30. 08000090 b5 15 27 80 6d e6 f7 7c 74 09 8d 45 81 4c 4f 51 |..'.m..|t..E.LOQ|
      31. 080000a0 35 1f 5a 44 00 01 00 59 37 38 64 31 63 35 38 31 |5.ZD...Y78d1c581|
      32. 080000b0 2d 30 32 65 32 2d 34 39 35 36 2d 38 31 39 31 2d |-02e2-4956-8191-|
      33. 080000c0 33 31 66 64 32 38 61 64 35 66 65 31 00 00 00 00 |31fd28ad5fe1....|
      34. 080000d0 00 ac 71 f3 00 04 03 4c e7 87 9e c2 fc 57 eb 7d |..q....L.....W.}|
      35. 080000e0 31 3e 02 a6 80 3c 1e a6 c9 ed be 0f 25 2c 29 13 |1>...<......%,).|
      36. 080000f0 8d 23 e4 87 9e 34 3f 6e 00 00 00 08 00 00 0f a0 |.#...4?n........|
      37. 08000100 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      38. 08000110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      39. 08000120 00 00 00 00 00 00 00 00 00 00 02 00 00 00 0f a0 |................|
      40. 08000130 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      41. 08000140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      42. 08000150 00 00 00 00 00 00 00 00 00 00 03 f8 00 00 0f a0 |................|
      43. 08000160 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      44. 08000170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      45. 08000180 00 00 00 00 00 00 00 00 00 00 05 f0 00 00 0f a0 |................|
      46. 08000190 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      47. 080001a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      48. 080001b0 00 00 00 00 00 00 00 00 00 00 07 e8 00 00 0f a0 |................|
      49. 080001c0 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      50. 080001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      51. 080001e0 00 00 00 00 00 00 00 00 00 00 09 e0 00 00 0f a0 |................|
      52. 080001f0 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      53. 08000200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      54. 08000210 00 00 00 00 00 00 00 00 00 00 0b d8 00 00 0f a0 |................|
      55. 08000220 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      56. 08000230 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      57. 08000240 00 00 00 00 00 00 00 00 00 00 0d d0 00 00 0f a0 |................|
      58. 08000250 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      59. *
      60. 08001000 4d 67 1e 95 70 59 03 75 7a d0 0f 7d 0d b1 1a a4 |Mg..pY.uz..}....|
      61. [DATA]
      Display All

      The post was edited 1 time, last by Tie-fighter ().

    • Brainfuck Source Code

      1. root@overlord:~# head /dev/sdc | hd
      2. 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      3. *
      4. 000001c0 01 00 ee fe ff ff 01 00 00 00 ff ff ff ff 00 00 |................|
      5. 000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      6. *
      7. 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
      8. 00000200 45 46 49 20 50 41 52 54 00 00 01 00 5c 00 00 00 |EFI PART....\...|
      9. 00000210 7c 02 15 a1 00 00 00 00 01 00 00 00 00 00 00 00 ||...............|
      10. 00000220 af a3 50 5d 01 00 00 00 22 00 00 00 00 00 00 00 |..P]....".......|
      11. 00000230 8e a3 50 5d 01 00 00 00 26 e8 84 20 24 f5 f4 4a |..P]....&.. $..J|
      12. 00000240 a5 2d 27 a5 e9 cd b6 ba 02 00 00 00 00 00 00 00 |.-'.............|
      13. 00000250 80 00 00 00 80 00 00 00 29 87 24 bb 00 00 00 00 |........).$.....|
      14. 00000260 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      15. *
      16. 00000400 0f 88 9d a1 fc 05 3b 4d a0 06 74 3f 0f 84 91 1e |......;M..t?....|
      17. 00000410 d6 39 e3 4b 79 86 2a 46 b1 4a 02 f2 90 27 91 e0 |.9.Ky.*F.J...'..|
      18. 00000420 00 08 00 00 00 00 00 00 ff 9f 50 5d 01 00 00 00 |..........P]....|
      19. 00000430 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      20. *
      21. 08080000 4c 55 4b 53 ba be 00 01 61 65 73 00 00 00 00 00 |LUKS....aes.....|
      22. 08080010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      23. 08080020 00 00 00 00 00 00 00 00 78 74 73 2d 70 6c 61 69 |........xts-plai|
      24. 08080030 6e 36 34 00 00 00 00 00 00 00 00 00 00 00 00 00 |n64.............|
      25. 08080040 00 00 00 00 00 00 00 00 73 68 61 31 00 00 00 00 |........sha1....|
      26. 08080050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      27. 08080060 00 00 00 00 00 00 00 00 00 00 10 00 00 00 00 40 |...............@|
      28. 08080070 28 b7 12 26 76 56 22 58 cb 44 52 fd b0 66 97 d4 |(..&vV"X.DR..f..|
      29. 08080080 f0 40 cb b4 3b 1e 4f 48 a2 00 f4 5b dc 07 0c 40 |.@..;.OH...[...@|
      30. 08080090 4d e6 8f 2b 7d 82 91 41 ed f3 8d 96 d8 59 99 9b |M..+}..A.....Y..|
      31. 080800a0 e3 e6 c5 ba 00 00 fc 71 34 63 61 32 61 38 35 32 |.......q4ca2a852|
      32. 080800b0 2d 63 39 63 33 2d 34 66 66 31 2d 62 39 62 34 2d |-c9c3-4ff1-b9b4-|
      33. 080800c0 35 62 32 30 34 66 64 34 66 33 38 63 00 00 00 00 |5b204fd4f38c....|
      34. 080800d0 00 ac 71 f3 00 03 f2 21 91 e8 2f 82 a4 01 8f 8e |..q....!../.....|
      35. 080800e0 8f a0 5a d9 3f 79 af 3f a0 b5 5c 22 15 06 e1 e3 |..Z.?y.?..\"....|
      36. 080800f0 56 c5 fd 37 ba 7c cb 28 00 00 00 08 00 00 0f a0 |V..7.|.(........|
      37. 08080100 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      38. 08080110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      39. 08080120 00 00 00 00 00 00 00 00 00 00 02 00 00 00 0f a0 |................|
      40. 08080130 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      41. 08080140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      42. 08080150 00 00 00 00 00 00 00 00 00 00 03 f8 00 00 0f a0 |................|
      43. 08080160 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      44. 08080170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      45. 08080180 00 00 00 00 00 00 00 00 00 00 05 f0 00 00 0f a0 |................|
      46. 08080190 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      47. 080801a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      48. 080801b0 00 00 00 00 00 00 00 00 00 00 07 e8 00 00 0f a0 |................|
      49. 080801c0 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      50. 080801d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      51. 080801e0 00 00 00 00 00 00 00 00 00 00 09 e0 00 00 0f a0 |................|
      52. 080801f0 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      53. 08080200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      54. 08080210 00 00 00 00 00 00 00 00 00 00 0b d8 00 00 0f a0 |................|
      55. 08080220 00 00 de ad 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      56. 08080230 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      57. 08080240 00 00 00 00 00 00 00 00 00 00 0d d0 00 00 0f a0 |................|
      58. 08080250 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      59. *
      60. 08081000 2e c3 2d 29 65 11 83 57 65 19 35 4e 75 29 19 af |..-)e..We.5Nu)..|
      61. 08081010 59 1d d3 b7 d0 54 ee ad a8 aa 56 76 ba 57 8a 0b |Y....T....Vv.W..|
      62. [DATA]
      Display All


      Brainfuck Source Code

      1. root@overlord:~# head /dev/sdd | hd
      2. 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      3. *
      4. 000001c0 01 00 ee fe ff ff 01 00 00 00 ff ff ff ff 00 00 |................|
      5. 000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      6. *
      7. 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
      8. 00000200 45 46 49 20 50 41 52 54 00 00 01 00 5c 00 00 00 |EFI PART....\...|
      9. 00000210 de fa ea 99 00 00 00 00 01 00 00 00 00 00 00 00 |................|
      10. 00000220 af a3 50 5d 01 00 00 00 22 00 00 00 00 00 00 00 |..P]....".......|
      11. 00000230 8e a3 50 5d 01 00 00 00 26 e8 84 20 24 f5 f4 4a |..P]....&.. $..J|
      12. 00000240 a5 2d 27 a5 e9 cd b6 ba 02 00 00 00 00 00 00 00 |.-'.............|
      13. 00000250 80 00 00 00 80 00 00 00 f0 55 fb 7e 00 00 00 00 |.........U.~....|
      14. 00000260 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      15. *
      16. 00000400 af 3d c6 0f 83 84 72 47 8e 79 3d 69 d8 47 7d e4 |.=....rG.y=i.G}.|
      17. 00000410 16 06 d4 39 c3 94 c5 4d b4 cf ea a5 51 a9 78 40 |...9...M....Q.x@|
      18. 00000420 00 08 00 00 00 00 00 00 8e a3 50 5d 01 00 00 00 |..........P]....|
      19. 00000430 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
      20. *
      21. 00004400 df fd 02 bd 95 c8 cc d3 13 e0 e0 09 72 35 22 0c |............r5".|
      22. [DATA]
      Display All


      Source Code

      1. root@overlord:~# cat /etc/mdadm/mdadm.conf
      2. # mdadm.conf
      3. #
      4. # Please refer to mdadm.conf(5) for information about this file.
      5. #
      6. # by default, scan all partitions (/proc/partitions) for MD superblocks.
      7. # alternatively, specify devices to scan, using wildcards if desired.
      8. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
      9. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
      10. # used if no RAID devices are configured.
      11. DEVICE partitions
      12. # auto-create devices with Debian standard permissions
      13. CREATE owner=root group=disk mode=0660 auto=yes
      14. # automatically tag new arrays as belonging to the local system
      15. HOMEHOST <system>
      16. # definitions of existing MD arrays
      17. ARRAY /dev/md0 metadata=1.2 name=overlord:0 UUID=e570f437:004cec99:cd88fbf0:bddf3d61
      Display All
    • I've got the same problem...
      Superblock in MBR gets wiped after every reboot [Blocked Image: http://forums.openmediavault.org/wcf/images/smilies/crying.png]

      Good news first:
      I can still access my data by re-creating the array but:
      • the drive order must be exactly the same like back then when you created the raid
        • maybe you got an old mdadm --detail or /proc/mdstat output where you can see the raiddevice number for the drive letters (given they're still in the same SATA ports and no BIOS settings like SATA mode where changed)
      • all other details like Number of drives, chunk size etc. must match as well, of course
      • assume-clean should be used so it doesnt actually touch the data
      • no guarantee this works for you, if it doesnt most probably all data is lost.
      Then define as much details as possible within the create, mine for example:
      mdadm --create /dev/md/n0rd --chunk=512 --raid-devices=4 --spare-devices=0 --assume-clean --level=5 --name=datacube:n0rd /dev/sda /dev/sdb /dev/sdc /dev/sdd --verbose

      **edit**
      Found a very nice thread at serverfault from 2012 (see 1st answer with highest score)
      This Shane Madden guy literally tries to break the data with attempts of array creations with wrong order, chunk size and so on but still could access the data after all invalid attepmts
      Wow. So, it looks like none of these actions corrupted data in any way. I was quite surprised by this result, frankly;
      I expected moderate odds of data loss on the chunk size change, and some definite loss on the layout change. I learned something today.


      The issue:
      Did you switch your mainboard/controller or even did a BIOS update recently?
      I did switch from an old ivy bridge based board to an ASRock Z87E-ITX.

      In my case I can clearly reproduce that its caused by the mainboard :
      Recreating the array as described above > can mount and access my data > reboot > all superblocks missing > mdadm --examine doesnt find anything neither on mbr nor on partition 1 on each drive

      mdadm --examine /dev/sd[abcd] wrote:

      /dev/sda:
      MBR Magic : aa55
      Partition[0] : 4294967295 sectors at 1 (type ee)
      /dev/sdb:
      MBR Magic : aa55
      Partition[0] : 4294967295 sectors at 1 (type ee)
      /dev/sdc:
      MBR Magic : aa55
      Partition[0] : 4294967295 sectors at 1 (type ee)
      /dev/sdd:
      MBR Magic : aa55
      Partition[0] : 4294967295 sectors at 1 (type ee)


      Interestingly though it somehow cleares the superblock but leaves the GPT partition table intact still showing my single FD00 Linux RAID Partition.
      Sometimes it occurs that one single drive out of the array doesnt get affected, mdadm --examine then still shows the superblock as intact and gdisk throws "corrupted GPT table" > but after another reboot this last-man-standing superblock is also wiped [Blocked Image: http://forums.openmediavault.org/wcf/images/smilies/mellow.png]

      To make sure its not OMV i've put in my ubuntu OS SSD from the previous machine (which is still running fine with another raid set) created the array/superblocks > rebooted > gone [Blocked Image: http://forums.openmediavault.org/wcf/images/smilies/sad.png]
      Now i've connected one drive via an PCI-E SATA controller > Superblock deleted again... (The same controller worked like a charm with these hard disks in the ivy system)

      Then i tried an older drive no 4k blocks, no GPT table and guess what? > Mainboard didnt wipe it ... so i guess its some weird behaviour during boot initialisation with [Blocked Image: http://forums.openmediavault.org/wcf/images/smilies/confused.png] UEFI and 4k/GPT disks [Blocked Image: http://forums.openmediavault.org/wcf/images/smilies/confused.png] no matter how the device is connected
      Now i started going crazy with the BIOS Settings, AHCI Mode, RAID Mode, even IDE mode, disabling S.M.A.R.T., disabling SATA Power Management, resetting default BIOS settings - all without success

      Drives are 4x brand-new ST8000AS0002 or let's say "almost" new, the array ran completely fine for a quarter in the ivy machine @Ubuntu
      Yes I know Seagate doesnt recommend their Archive series for NAS purposes to sell their expensive Enterprise versions but until the mainboard change I had 0 issues with them.


      Solution?
      My last idea (except using another board) would be giving the partitions /dev/sdx1/ instead of just the whole drive /dev/sdx during array creation.
      Does this write the superblock to the partition itself instead to the MBR (which seems to get wiped) of the disk?? And even more important: will this destroy my existing data on the drives?

      Greetz,
      N0rd

      The post was edited 3 times, last by Nordmann ().

    • Solved the issue for myself by revoking/cancelling the ASRock Z87E-ITX order while still possible.
      New Board is a Gigabyte GA-H97N-WIFI and it doesnt touch the drives during boot like it's supposed to be...

      Re-created the Array with same specs one last time and all data is still there :thumbup:
    • Nordmann wrote:

      Solution?
      My last idea (except using another board) would be giving the partitions /dev/sdx1/ instead of just the whole drive /dev/sdx during array creation.
      Does this write the superblock to the partition itself instead to the MBR (which seems to get wiped) of the disk?? And even more important: will this destroy my existing data on the drives?

      I can confirm the above solution.

      I had a mdadm RAID5 over four disks created on /dev/sd[abcd] instead of /dev/sd[abcd]1. This worked fine on my Jetway NF9G. However, moving the RAID to a brand new Asrock N3700 resulted in deleted superblock information. Luckily, I could reassemble knowing the exact order of drives. So no data was lost in the end. Then I degraded the RAID and created a new one using partitions. This is recommended anyway. Several days later a RAID5 is now working properly on the Asrock N3700.
      OMV 3.0.94

      Hardware:
      ASRock N3700-ITX
      1x4GB DDR3-1600 SO-DIMM
      2x4000GB WD Red and 2x4000GB WD Green in mdadm RAID5
      16 GB Mach Xtreme Technology Ultra MX-ES USB 3.0 as root
      Fractal Design Node 304 with PicoPSU