RAID 1 N/A after upgrade from 3.x

    • OMV 4.x (stable)

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

    • RAID 1 N/A after upgrade from 3.x

      Hi!

      Well i really shouldn't upgrade....

      My RAID array is still there after the upgrade, but it's N/A in the file system menu (pointed to /dev/disk/by-label/xxx ,but after the upgrade there was no /dev/disk/by-label dir) and mount points ware not working. I couldn't remove it.
      I did try to remove my array then make a new , later omv-mkconf mdadm, reboot...
      So i simply did make a clean install of 4.0.14.
      Now i can add a new file system through OMV GUI but this way i'll loose my data.
      I there another way to add it to OMV ?
      I can mount it manually , and it's working fine. But this way i can't share my data...






      fstab:
      UUID=0d47bf16-9226-42ec-ac84-25112153fa1d / ext4 errors=remount-ro 0 1
      UUID=f1f05230-fc89-487d-9310-f8ab9ed7209e none swap sw 0 0
      tmpfs /tmp tmpfs defaults 0 0


      blkid:
      /dev/sdb: UUID="a1e39509-9a63-f4df-4958-515066402951" UUID_SUB="3c37d5b6-d807-a535-d206-a14e57633060" LABEL="OMV:WDPURPLE" TYPE="linux_raid_member"
      /dev/sdc: UUID="a1e39509-9a63-f4df-4958-515066402951" UUID_SUB="e14c00b0-c618-5654-8bca-022dc65e47e5" LABEL="OMV:WDPURPLE" TYPE="linux_raid_member"
      /dev/sda1: UUID="0d47bf16-9226-42ec-ac84-25112153fa1d" TYPE="ext4" PARTUUID="7e9eb0e5-01"
      /dev/sda5: UUID="f1f05230-fc89-487d-9310-f8ab9ed7209e" TYPE="swap" PARTUUID="7e9eb0e5-05"

      mdadm.conf
      ARRAY /dev/md/md0 metadata=1.2 name=OMV:WDPURPLE UUID=a1e39509:9a63f4df:49585150:66402951

      mdadm --detail --scan --verbose
      ARRAY /dev/md/md0 level=raid1 num-devices=2 metadata=1.2 name=OMV:WDPURPLE UUID=a1e39509:9a63f4df:49585150:66402951 devices=/dev/sdb,/dev/sdc

      fdisk -l | grep "Disk "
      Disk /dev/sdb: 3,7 TiB, 4000787030016 bytes, 7814037168 sectors
      Disk /dev/sdc: 3,7 TiB, 4000787030016 bytes, 7814037168 sectors
      Disk /dev/sda: 298,1 GiB, 320072933376 bytes, 625142448 sectors
      Disk identifier: 0x7e9eb0e5
      Disk /dev/md127: 3,7 TiB, 4000652787712 bytes, 7813774976 sectors
    • so you upgraded your OMV3->OMV4, clean install on your system drive and kept your Array. Did you try do mount this array within OMV web gui?

      N/A usually means, array is detected and present, but not mounted yet.
      Chaos is found in greatest abundance wherever order is being sought.
      It always defeats order, because it is better organized.
      Terry Pratchett
    • You got it right.
      I can't simply mount it in OMV GUI after clean install while it is no longer listed in file systems.
      When i try to add my array via OMV GUI (file systems menu) it wants to format it, a warning appears that all data will be lost...

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

    • It should be auto-detected within file system. I'll check this in a VM. did you remove/deattach the drives during OMV4 clean install?

      Edit: I have 2 VMs within XEN here, OMV3 and OMV4, so I set up a Raid 1 of 2 discs, EXT4 and created a shared folder on it within OMV3. The disks were attached to port 2 and 3. After that I removed the drives from OMV3 and attached them to OMV4, even changed ports to 1 and 2. Raid was detected instantly. Did you try to reboot your system?
      Chaos is found in greatest abundance wherever order is being sought.
      It always defeats order, because it is better organized.
      Terry Pratchett

      The post was edited 2 times, last by riff-raff ().

    • It's not the first time I had to do a clean install, i didn't remove anything while installing. It was always working. Now I think it must be something with the OMV4 , and not with my array? Maybe I should go back to OMV3...

      Yes , I did reboot it, many times.

      The post was edited 2 times, last by Setu ().

    • Thank You for any help.

      Sorry to say but i give up on OMV and choose a different path.
      No clue what happened, but I'm sure it's because of that upgrade from 3 to 4.
      So beware of doing so if you are not experienced enough. Also the RRDTool crashed after upgrade but that's a different story.
    • I did again, when you mentioned it.
      This time i found exactly the same problem:

      "Missing" RAID filesystem

      If I understood correctly, when my md0 is not listed in blkid then OMV will not show it and kernel 4.13 is the problem.
      But now i'm using Debian 4.9.65-3+deb9u2 (2018-01-04) and still blkid doesn't show my array and it's working just fine mounted vis fstab.


      Thank You

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