Raspberry pi missing raid 1

    • OMV 3.x

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

    • Raspberry pi missing raid 1 - mdraid issue

      Hi,

      So, I have been happily using OMV 3.0.99 for a while to store my family photos but the raid 1 has disappeared.

      I have a pi3 and two 1tb USB drives.

      Having read a few posts it seems my first mistake was using raid 1 and I would have been better using rsync.

      Hopefully someone can assist in reviving my raid setup. I have attached below the information that I see requested in other posts. Let me know if any extra is required.

      cat /proc/mdstat
      Personalities :
      unused devices:

      blkid
      Display Spoiler

      /dev/mmcblk0p1: LABEL="boot" UUID="CE83-8CE1" TYPE="vfat" PARTUUID="c5ac05a5-01"
      /dev/mmcblk0p2: UUID="ae708a4d-982a-4a20-965c-01ec7e1f32b3" TYPE="ext4" PARTUUID="c5ac05a5-02"
      /dev/sda: UUID="e3de5b12-fc31-aaab-7735-09ee56164cbf" UUID_SUB="b4a984cd-a145-4348-1257-1515e464fc74" LABEL="mediavault:MyArray" TYPE="linux_raid_member"
      /dev/sdb: UUID="e3de5b12-fc31-aaab-7735-09ee56164cbf" UUID_SUB="47ed50bc-b676-fbf6-b865-485c39e2f382" LABEL="mediavault:MyArray" TYPE="linux_raid_member"
      /dev/mmcblk0: PTUUID="c5ac05a5" PTTYPE="dos"
      /dev/mmcblk0p3: PARTUUID="c5ac05a5-03"


      fdisk -l | grep "Disk "
      Display Spoiler

      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: 14.9 GiB, 15931539456 bytes, 31116288 sectors
      Disk identifier: 0xc5ac05a5
      Disk /dev/sda: 931.5 GiB, 1000170586112 bytes, 1953458176 sectors
      Disk /dev/sdb: 931.5 GiB, 1000170586112 bytes, 1953458176 sectors


      cat /etc/mdadm/mdadm.conf
      Display Spoiler

      # 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

      # definitions of existing MD arrays
      ARRAY /dev/md0 metadata=1.2 name=mediavault:MyArray UUID=e3de5b12:fc31aaab:773509ee:56164cbf


      mdadm --detail --scan --verbose
      This command returned no information.

      Hopefully this info can help identify and fix the problem.

      Thanks in advance,
      Mike

      The post was edited 4 times, last by Teamllama: Altered title and formatting ().

    • Teamllama wrote:

      he response from the command is here
      Nothing suspicious except that your board runs somewhat hot (not relevant) and is still on kernel 4.9 (should be on 4.14 if you installed all updates).

      The disks seem to be ok but there's no raid occurence whatsoever in your dmesg output. I don't use mdraid for a number of reasons so unfortunately can't help any further...
    • mdraid does seem to be an issue.

      It is running rather hot at the moment, mostly because the temperature in the room isn't dropping below 27C, even at night.

      Thank you for taking a look through all of the data i posted. Hopefully someone else will see this post and be able to assist.

      At least i now know the issue is with mdraid so i can research that.
    • It looks like there might be a possible root to a solution in this post - superuser.com/questions/801826…-raid-vanish-after-reboot

      I just don't understand it! Hopefully someone else will be able to translate.

      When i get home later i will try running

      Source Code

      1. # update-initramfs -u

      and see what that does.

      My main concern is loosing all my photos of my children. They were also saved on my laptop but it's hard drive died last week!

      I think i will also try adding the follow i found on the raspberry pi forum. The boot delay might dive everything time to settle down in time to load correctly.


      Source Code

      1. Anyway, yes you can pause, the boot process by adding a line to the /boot/config.txt
      2. Run this command:
      3. sudo nano /boot/config.txt
      4. And add the line
      5. boot_delay=5

      The post was edited 1 time, last by Teamllama: added boot delay info ().

    • Update for anyone reading this in future who has the same problem.

      Adding a boot delay had no effect.

      Running update-initramfs -u had no effect

      However running the following two commands got one of the drives reconnected to the raid array and i was able to access the data. Inside OMV it is now reporting that the array is "Clean, degraded".

      mdadm --stop --scan
      mdadm --assemble --scan

      I am currently copying the contents to another drive. Once that is complete i will experiment some more to see if I can fix the array.

      If not at least i will be able to wipe it and start again, maybe not using raid 1.
    • Teamllama wrote:

      at least i will be able to wipe it and start again, maybe not using raid 1
      You should really keep in mind what RAID-1 is for. It's data availability only and not related to anything related to data security or protection. It's 'business continuity' and you certainly don't need this at home and especially it's a joke if you try to do this with such a lousy hardware as any Raspberry Pi (with some better ARM boards you can play RAID but not with those lousy Raspberries).
      1. Usually you don't want RAID-1 (especially not the primitive mdraid variant)
      2. If you want to play RAID you probably want server grade hardware but need at least reliable hardware since RAID is designed with 'underlying hardware works flawlessly' in mind. That prevents RAID in situations where underpowering and sudden power losses can occur
      3. You never want USB RAID
      4. You never ever want USB RAID where all disks are behind one single point of failure called USB hub (this is always the case with any Raspberry Pi since those devices only have one single USB port so all USB receptacles are behind one or even two internal USB hubs -- yeah, they managed to make things even worse with their latest RPi 3B+)
      So please do yourself a favour and forget about RAID with a Raspberry Pi (better forget about this lousy hardware at all and choose one of the many better options)
    • Users Online 2

      2 Guests