RAID5 has disappeared after reboot

    • OMV 4.x

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

    • RAID5 has disappeared after reboot

      Hi all,
      after reboot I don't see anymore RAID5 composed by 3 disks.
      This is my report:


      Display Spoiler

      Personalities :

      md127 : inactive sdc1[3](S)

      3906886468 blocks super 1.2



      unused devices: <none>



      /dev/mmcblk0: PTUUID="c5ac05a5" PTTYPE="dos"

      /dev/mmcblk0p1: LABEL="boot" UUID="CE83-8CE1" TYPE="vfat" PARTUUID="c5ac05a5-01"

      /dev/mmcblk0p2: UUID="2666ed46-1bb6-4ad7-ab5d-2ccde455c5e5" TYPE="ext4" PARTUUID="c5ac05a5-02"

      /dev/mmcblk0p3: PARTUUID="c5ac05a5-03"

      /dev/sdc1: UUID="8ea9547f-3a74-da29-87b4-6f6e1e4aa17e" UUID_SUB="467a3fc3-3df4-4f2d-377c-62a81da7RTUUID="35003986-b0a4-48f0-8d48-031554c5f602"

      /dev/zram0: UUID="fa80a098-4f15-4c7c-96e4-74cd1bd5d870" TYPE="swap"

      /dev/zram1: UUID="f2489ed5-a499-4fef-896f-c306b65ba805" TYPE="swap"

      /dev/zram2: UUID="5f0f9b42-3b43-42c9-8d50-44077cd8293b" TYPE="swap"

      /dev/zram3: UUID="f0554863-be69-4fc8-9a3e-9c0fcf8002be" TYPE="swap"


      Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors
      Disk /dev/mmcblk0: 29.8 GiB, 32010928128 bytes, 62521344 sectors
      Disk identifier: 0xc5ac05a5
      Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 976754646 sectors
      Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 976754646 sectors
      Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 976754646 sectors
      Disk identifier: 68CDF598-69D9-40F4-AA21-193B49D07C5D
      Disk /dev/zram0: 115.8 MiB, 121384960 bytes, 29635 sectors
      Disk /dev/zram1: 115.8 MiB, 121384960 bytes, 29635 sectors
      Disk /dev/zram2: 115.8 MiB, 121384960 bytes, 29635 sectors
      Disk /dev/zram3: 115.8 MiB, 121384960 bytes, 29635 sectors


      # 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


      INACTIVE-ARRAY /dev/md127 num-devices=1 metadata=1.2 name=raspberrypi:NAS8Tb UUID=8ea9547f:3a74da29:87b46f6e:1e4aa17e
      devices=/dev/sdc1


      Thanks in advance to everyone wants help me.
    • This is on a Rasp Pi, using USB for raid purposes was disabled in OMV4.

      Can anyone help, highly unlikely;
      1) mdstat only references one drive
      2) blkid is missing relevant information
      3) mdadm.conf contains no raid information
      4) the last output which I assume is --detail --scan lists one device
      5) fdisk does appear to list all three drives

      There is no information on the type of drive or how they are connected i.e own power supply etc, nor what Pi version.

      If there was any data on that raid chances are it's gone, you could search for references regarding mdadm (software raid) and start from there.
      Raid is not a backup! Would you go skydiving without a parachute?
    • bertol0 wrote:

      Can you tell me other suggestions?
      Not really, you could start with mdadm --detail /dev/sda do that with all three drives and see what information is returned, but as to re assembling it, highly unlikely.
      My guess is you completed this from the command line, hence the empty mdadm.conf as this step was not done.
      Raid is not a backup! Would you go skydiving without a parachute?
    • When i send this command:

      Source Code

      1. #mdadm --examine /dev/sdc1
      I obtain this:
      Display Spoiler

      /dev/sdc1:
      Magic : a92b4efc
      Version : 1.2
      Feature Map : 0x1
      Array UUID : 8ea9547f:3a74da29:87b46f6e:1e4aa17e
      Name : raspberrypi:NAS8Tb (local to host raspberrypi)
      Creation Time : Sat Nov 16 22:31:23 2019
      Raid Level : raid5
      Raid Devices : 3

      Avail Dev Size : 7813772936 (3725.90 GiB 4000.65 GB)
      Array Size : 7813772288 (7451.79 GiB 8001.30 GB)
      Used Dev Size : 7813772288 (3725.90 GiB 4000.65 GB)
      Data Offset : 262144 sectors
      Super Offset : 8 sectors
      Unused Space : before=262056 sectors, after=648 sectors
      State : clean
      Device UUID : 467a3fc3:3df44f2d:377c62a8:1da7d31b

      Internal Bitmap : 8 sectors from superblock
      Update Time : Sat Nov 23 22:55:51 2019
      Bad Block Log : 512 entries available at offset 72 sectors
      Checksum : a9082025 - correct
      Events : 49901

      Layout : left-symmetric
      Chunk Size : 512K

      Device Role : Active device 2
      Array State : AAA ('A' == active, '.' == missing, 'R' == replacing)


      So I guess the RAID5 still exist. Any suggests?
    • --examine /dev/md127
      nothing appear

      mdadm --examine on /dev/sda
      No md superblock detected on /dev/sda

      The same for /sdb

      At this point I would try to send this command found in other post in similar case:
      mdadm --create /dev/md127 --level=5 --assume-clean --verbose --raid-devices=3 /dev/sd[abc]
      Do you agree?
    • the steps to config a raid are:

      #apt-get install mdadm parted
      #parted /dev/sdX mklabel gpt
      or
      #parted /dev/sdX mklabel msdos
      depends on bios and uefi
      #parted /dev/sdX set 1 raid on
      do it on all raid disks XYZ
      next single step is optional and depends if you want raid disks (jump) or raid patitions (do it).
      #parted -a optimal -- /dev/sdX mkpart primary 0% 99%
      on partition raids do a
      #mdadm --create /dev/md0 --auto md --level=5 --raid-devices=3 /dev/sdX1 /dev/sdY1 /dev/sdZ1
      on disk raids do a
      #mdadm --create /dev/md0 --auto md --level=5 --raid-devices=3 /dev/sdX /dev/sdY /dev/sdZ
      this will take a looooong time.
      watch about it at
      #watch cat /proc/mdstat
      if its ready and up, take a look at
      #cat /etc/mdadm/mdadm.conf
      it shoud contain a line like
      ARRAY /dev/md/md0 metadata=1.2 name=nas:md0 UUID=264....bla blub
      if not, do a
      #mdadm --detail --scan >> /etc/mdadm/mdadm.conf
      now your raid appear and is hopefully fine, view it with
      #mdadm --detail /dev/md/md_test
      if you break the (re)assmebly... what i think, you need to reassemble.
      ##mdadm --assemble /dev/md0 /dev/sdX(1) /dev/sdY(1) /dev/sdZ(1) --force
      (depends on Disk or Partition arrays) and think about.. it needs lot of time!
      if the array was ready and gone, try
      #mdadm --assemble --run --force --update=resync /dev/md0 /dev/sdX(1) /dev/sdY(1) /dev/sdZ(1)
      if the array is fine, you can set up a FS.
      maybe this one.
      #mkfs.ext4 -b 4096 -E stride=128,stripe-width=384 /dev/md0
      and mount it via omv or by hand in /etc/fstab
      if you wanna boot from, install grub and, make a
      #update-initramfs -u
      sometimes raids appear as md0 or md127, i dont know why.
      and last but not least...read a good mdadm howto!
      Equipment: a few Computers, lot's of waste heat, little time and a Pile of work.

      When solving problems, dig at the root instead of hacking at the leaves.

      The post was edited 5 times, last by Rd65: some corrections ().

    • Rd65 wrote:

      depends on bios and uefi
      do it on all raid disks XYZ
      Did you actually read any of this thread! The OP is using a Raspberry Pi 3B+ the option for creating a raid using USB devices was disabled on OMV4. Does the Pi have a bios no! Does it have uefi no!

      bertol0 wrote:

      Do you agree?
      I don't agree with doing anything like this on a Raspberry Pi least of all a Pi 3B+ and as I have said to others who have attempted this, don't call us, we'll call you :D it is simply a bad idea. Also, as far as I can remember the USB ports share the same chipset as the Ethernet.
      Raid is not a backup! Would you go skydiving without a parachute?
    • geaves wrote:

      Rd65 wrote:

      depends on bios and uefi
      do it on all raid disks XYZ
      Did you actually read any of this thread! The OP is using a Raspberry Pi 3B+ the option for creating a raid using USB devices was disabled on OMV4. Does the Pi have a bios no! Does it have uefi no!
      yes i read and decide to write a system independend minihowto about setup/rescue a raid.
      as the title describe:

      the steps to config a raid are:

      but no.. on pi there is no uefi.... so i must be wrong...

      thank you geaves
      Equipment: a few Computers, lot's of waste heat, little time and a Pile of work.

      When solving problems, dig at the root instead of hacking at the leaves.
    • Rd65 wrote:

      the steps to config a raid are:
      :) I did read that, but setting up a Raid on OMV can be, and is recommended to be completed within the GUI (makes it easier for home users)
      But the Pi is a PITA when it comes to this due to issues regarding under powering, that's why a Raid setup using USB drives was removed from OMV. Yes, as you have shown in your minihowto it can be achieved/done from the command line, but on the Pi or any SBC using USB for this is not really a good idea. :)
      Raid is not a backup! Would you go skydiving without a parachute?
    • i agree, that it is not a good idea to raid via usb. absolutly!
      but its not impossible, for learning and testing scenarios... why not?
      In my view the pi is invented as a educational computer!
      so what is the problem testing raid5 with 3 usbsticks??
      you may use it for other challeges...like pi-hole, a bt-seeder, tv/media/plex head or whatever.. but as a pi user you are always at your own. Most people.. even the guys with a pi.. are able to use a shell too.

      But about omv and Raid as (Linux) principe, you are simply wrong.
      The tool to admin softraids is not omv, it is mdadm.
      show me in omv how to insert a spare drive to a raid.. or manage a rebuild, stripe sizes, and so on...
      its nice to see how easy it is to klick a simple raid together in omv ... but thats not all. And i think you know that too.

      So why do you dont tell the poeople where to find knowledge about raids, even if you cant or will not help?
      Is omv your only way to get access to a system? Why you try to hide things on a open system and tell people to use omv instead learning using the right shell commands? You try to protect people from the system but you make the people dependent!
      I would understand it if you work on a better version of omv-raid ... but ...
      Equipment: a few Computers, lot's of waste heat, little time and a Pile of work.

      When solving problems, dig at the root instead of hacking at the leaves.
    • Rd65 wrote:

      Why you try to hide things on a open system and tell people to use omv instead learning using the right shell commands?
      If you have been around here as long as geaves has been, you would know that many people do not want to learn shell commands. No one is hiding anything. If they want to know how to work with raid on an OMV box, just google for debian/ubuntu tutorials. But you will find that they want to use the web interface. If something is missing, I guess it is strange it isn't in more demand.

      Rd65 wrote:

      So why do you dont tell the poeople where to find knowledge about raids, even if you cant or will not help?
      Why do you treat people so poorly who are just trying to help? If he can't help, how would he tell people where to find knowledge? Pretty sure everyone knows about google. Most people find this forum very helpful. You seem to think it and OMV itself are terrible. Not sure why you use it if everything is done wrong. I've been a Linux admin for over 20 years and I find OMV very time saving. Is everything perfect? no but it does a damn good job for the targeted user.

      Rd65 wrote:

      Most people.. even the guys with a pi.. are able to use a shell too.
      Definitely not on this forum. Most pi users are Windows users who have never used the command line.

      Rd65 wrote:

      so what is the problem testing raid5 with 3 usbsticks??
      You will have to create it from the command line. The web interface purposely blocks users from create raid arrays with usb devices. If you want to learn about raid, you should start with the command line anyway. But testing on the RPi is still a terrible idea (maybe not as bad with usb sticks) because the usb ports don't always activate early enough and/or the usb drives aren't spun up at boot assembly time.

      Rd65 wrote:

      show me in omv how to insert a spare drive to a raid.. or manage a rebuild, stripe sizes, and so on...
      The grow command can add a spare. Ideally you shouldn't have to manage a rebuild and it is probably had to do that from the web interface since the system will boot to single user. Very few users need to manage stripe sizes. Some decisions to not show settings are made to keep the web interface simple.
      omv 5.1.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.11
      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!
    • Maybe I value the abilities of the audience wrong, yes.
      but this is more a philosohic point because you can not treat everyone the way you do the stupidest.
      I know what I'm writing about, I'm a supporter to, but in a different environment and i know the phrases that needed to survive.
      but this is offtopic.
      Equipment: a few Computers, lot's of waste heat, little time and a Pile of work.

      When solving problems, dig at the root instead of hacking at the leaves.
    • Rd65 wrote:

      you can not treat everyone the way you do the stupidest.
      Wrong. I don't treat anyone like they are stupid. I try to match my support to their skill level. If they ask for more advanced help, I give it to them.
      omv 5.1.3 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.11
      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!
    • thats my view of things too and i agree with your statement. in general and related to your support.
      But the thread starts with geavis... my criticism was for him.
      Equipment: a few Computers, lot's of waste heat, little time and a Pile of work.

      When solving problems, dig at the root instead of hacking at the leaves.
    • ryecoaaron wrote:

      Wrong. I don't treat anyone like they are stupid. I try to match my support to their skill level. If they ask for more advanced help, I give it to them.
      This is difficult to do on a regular basis, while taking into account the unknown philosophies of all comers and near endless possibilities.

      ryecoaaron wrote:

      Is everything perfect? no but it does a damn good job for the targeted user.
      That's just sacrilege. :D

      Rd65 wrote:

      But the thread starts with geavis... my criticism was for him.
      I get on @geaves myself, from time to time, for being such a nice guy.

      The post was edited 1 time, last by crashtest ().