RAID Array Creation Failure on RPi3

    • OMV 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • RAID Array Creation Failure on RPi3

      Hello,

      Goal: To make a RAID5 NAS and seedbox out of 3 usb sticks after HD died on RPi3.

      When trying to create a RAID5 array on the web interface with USB sticks I encounter following error:

      Source Code

      1. Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; omv-mkraid /dev/md0 -l stripe -n 3 -N DISK /dev/sda /dev/sdb /dev/sdc 2>&1' with exit code '1': mdadm: chunk size defaults to 512K mdadm: Defaulting to version 1.2 metadata mdadm: failed to open /dev/sdc after earlier success - aborting
      Details are the following

      Source Code

      1. Error #0:
      2. exception 'OMV\ExecException' with message 'Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; omv-mkraid /dev/md0 -l stripe -n 3 -N DISK /dev/sda /dev/sdb /dev/sdc 2>&1' with exit code '1': mdadm: chunk size defaults to 512K
      3. mdadm: Defaulting to version 1.2 metadata
      4. mdadm: failed to open /dev/sdc after earlier success - aborting' in /usr/share/php/openmediavault/system/process.inc:175
      5. Stack trace:
      6. #0 /usr/share/openmediavault/engined/rpc/raidmgmt.inc(249): OMV\System\Process->execute()
      7. #1 [internal function]: OMVRpcServiceRaidMgmt->create(Array, Array)
      8. #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
      9. #3 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('create', Array, Array)
      10. #4 /usr/sbin/omv-engined(516): OMV\Rpc\Rpc::call('RaidMgmt', 'create', Array, Array, 1)
      11. #5 {main}
      Display All

      Please do not mind that the array consists of USBs. I will replace them with HDDs as soon as I can create the RAID5 array. At the moment I am lost here.
      • Should I create the array via command line instead?
      • If not then what might be the issue that OMV UI fails to create the array? I have wiped the disks. Add the disks to fstab?

      Source Code

      1. cat /proc/mdstat
      2. Personalities :
      3. unused devices: <none>
      4. blkid
      5. /dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="boot" UUID="7D5C-A285" TYPE="vfat" PARTUUID="000b5098-01"
      6. /dev/mmcblk0p2: LABEL="omv" UUID="5d18be51-3217-4679-9c72-a54e0fc53d6b" TYPE="ext4" PARTUUID="000b5098-02"
      7. /dev/mmcblk0p3: UUID="fa36508a-b3c4-4499-b30a-711dd5994225" TYPE="ext4" PARTUUID="000b5098-03"
      8. /dev/mmcblk0: PTUUID="000b5098" PTTYPE="dos"
      9. fdisk -l
      10. Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
      11. Units: sectors of 1 * 512 = 512 bytes
      12. Sector size (logical/physical): 512 bytes / 4096 bytes
      13. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      14. Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
      15. Units: sectors of 1 * 512 = 512 bytes
      16. Sector size (logical/physical): 512 bytes / 4096 bytes
      17. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      18. Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
      19. Units: sectors of 1 * 512 = 512 bytes
      20. Sector size (logical/physical): 512 bytes / 4096 bytes
      21. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      22. Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
      23. Units: sectors of 1 * 512 = 512 bytes
      24. Sector size (logical/physical): 512 bytes / 4096 bytes
      25. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      26. Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
      27. Units: sectors of 1 * 512 = 512 bytes
      28. Sector size (logical/physical): 512 bytes / 4096 bytes
      29. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      30. Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
      31. Units: sectors of 1 * 512 = 512 bytes
      32. Sector size (logical/physical): 512 bytes / 4096 bytes
      33. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      34. Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 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 /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
      39. Units: sectors of 1 * 512 = 512 bytes
      40. Sector size (logical/physical): 512 bytes / 4096 bytes
      41. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      42. Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors
      43. Units: sectors of 1 * 512 = 512 bytes
      44. Sector size (logical/physical): 512 bytes / 4096 bytes
      45. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      46. Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors
      47. Units: sectors of 1 * 512 = 512 bytes
      48. Sector size (logical/physical): 512 bytes / 4096 bytes
      49. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      50. Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors
      51. Units: sectors of 1 * 512 = 512 bytes
      52. Sector size (logical/physical): 512 bytes / 4096 bytes
      53. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      54. Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors
      55. Units: sectors of 1 * 512 = 512 bytes
      56. Sector size (logical/physical): 512 bytes / 4096 bytes
      57. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      58. Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors
      59. Units: sectors of 1 * 512 = 512 bytes
      60. Sector size (logical/physical): 512 bytes / 4096 bytes
      61. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      62. Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors
      63. Units: sectors of 1 * 512 = 512 bytes
      64. Sector size (logical/physical): 512 bytes / 4096 bytes
      65. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      66. Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors
      67. Units: sectors of 1 * 512 = 512 bytes
      68. Sector size (logical/physical): 512 bytes / 4096 bytes
      69. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      70. Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors
      71. Units: sectors of 1 * 512 = 512 bytes
      72. Sector size (logical/physical): 512 bytes / 4096 bytes
      73. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      74. Disk /dev/mmcblk0: 14.5 GiB, 15523119104 bytes, 30318592 sectors
      75. Units: sectors of 1 * 512 = 512 bytes
      76. Sector size (logical/physical): 512 bytes / 512 bytes
      77. I/O size (minimum/optimal): 512 bytes / 512 bytes
      78. Disklabel type: dos
      79. Disk identifier: 0x000b5098
      80. Device Boot Start End Sectors Size Id Type
      81. /dev/mmcblk0p1 8192 122879 114688 56M c W95 FAT32 (LBA)
      82. /dev/mmcblk0p2 122880 7028735 6905856 3.3G 83 Linux
      83. /dev/mmcblk0p3 7028736 30318591 23289856 11.1G 83 Linux
      84. Disk /dev/sda: 14.9 GiB, 16005464064 bytes, 31260672 sectors
      85. Units: sectors of 1 * 512 = 512 bytes
      86. Sector size (logical/physical): 512 bytes / 512 bytes
      87. I/O size (minimum/optimal): 512 bytes / 512 bytes
      88. Disk /dev/sdb: 7.5 GiB, 8053063680 bytes, 15728640 sectors
      89. Units: sectors of 1 * 512 = 512 bytes
      90. Sector size (logical/physical): 512 bytes / 512 bytes
      91. I/O size (minimum/optimal): 512 bytes / 512 bytes
      92. Disk /dev/sdc: 7.2 GiB, 7759462400 bytes, 15155200 sectors
      93. Units: sectors of 1 * 512 = 512 bytes
      94. Sector size (logical/physical): 512 bytes / 512 bytes
      95. I/O size (minimum/optimal): 512 bytes / 512 bytes
      96. cat /etc/mdadm/mdadm.conf
      97. # mdadm.conf
      98. #
      99. # Please refer to mdadm.conf(5) for information about this file.
      100. #
      101. # by default, scan all partitions (/proc/partitions) for MD superblocks.
      102. # alternatively, specify devices to scan, using wildcards if desired.
      103. # Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
      104. # To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
      105. # used if no RAID devices are configured.
      106. DEVICE partitions
      107. # auto-create devices with Debian standard permissions
      108. CREATE owner=root group=disk mode=0660 auto=yes
      109. # automatically tag new arrays as belonging to the local system
      110. HOMEHOST <system>
      111. # definitions of existing MD arrays
      112. mdadm --detail --scan --verbose
      Display All
      Edit: clarification
      To err is human. To compute is calculator.

      The post was edited 4 times, last by blo: clarification ().