OMV 3 only default settings I have 10discs in a raid 6 array or i had... Now when i boot up i get an error saying .not enough discs to build array. 4/10

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

    • OMV 3 only default settings I have 10discs in a raid 6 array or i had... Now when i boot up i get an error saying .not enough discs to build array. 4/10

      Hello all dear OMV users
      So i would like to get some help before i get real sad...
      I installed OMV version 3.
      I have 10discs in a raid 6 array or i had...
      Now when i boot up i get an error saying .not enough discs to build array. 4/10

      please help out :(...

      I should say i have installed OMV on a fast USB 32GB sandisk key .
      My plan was to make a copy of the key to another key if one fails.
      Did not come that far....

      Is my data gone?
      It happend after i turned the PC off , while it was in sleep mode i think.
      All discs show when i boot up in bios and so on.
      I have installed OMV on another disc.
      During install all drives pop up.

      I am in a bit of panic...

      I can reach webgui, so thats ok..., just no array...
    • i looked at some older posts here .

      here is the output of : blkid

      root@xeonmedia:~# blkid
      /dev/sda: UUID="7b6938c4-0773-385e-8266-4ae327d728f1" UUID_SUB="bdb8341d-5282-53cd-bc2a-e5ac88937c91" LABEL="openxeon:0" TYPE="linux_raid_member"
      /dev/sdb: UUID="7b6938c4-0773-385e-8266-4ae327d728f1" UUID_SUB="1f1be1d1-54c3-9559-fcfa-dcf6f42575b7" LABEL="openxeon:0" TYPE="linux_raid_member"
      /dev/sdc: UUID="7b6938c4-0773-385e-8266-4ae327d728f1" UUID_SUB="95cc09fd-3944-a248-a090-ca3668bacd22" LABEL="openxeon:0" TYPE="linux_raid_member"
      /dev/sdd: UUID="7b6938c4-0773-385e-8266-4ae327d728f1" UUID_SUB="217d0b07-3c5b-f3f5-c460-204ebbdb2b1f" LABEL="openxeon:0" TYPE="linux_raid_member"
      /dev/sde: UUID="7b6938c4-0773-385e-8266-4ae327d728f1" UUID_SUB="f53f2705-87f2-3351-961c-56e544914db6" LABEL="openxeon:0" TYPE="linux_raid_member"
      /dev/sdf: UUID="7b6938c4-0773-385e-8266-4ae327d728f1" UUID_SUB="2aed4d21-481b-cbb4-81a1-afe6f6af7df5" LABEL="openxeon:0" TYPE="linux_raid_member"
      /dev/sdg: UUID="7b6938c4-0773-385e-8266-4ae327d728f1" UUID_SUB="eb907ec5-1bcc-e13c-4b2c-4b86fb9ceaa0" LABEL="openxeon:0" TYPE="linux_raid_member"
      /dev/sdh: UUID="7b6938c4-0773-385e-8266-4ae327d728f1" UUID_SUB="d1e05b3c-b898-99c9-a1ac-4455a593f8c7" LABEL="openxeon:0" TYPE="linux_raid_member"
      /dev/sdi: UUID="7b6938c4-0773-385e-8266-4ae327d728f1" UUID_SUB="d5334031-9a32-d457-9af5-a2e080ff2437" LABEL="openxeon:0" TYPE="linux_raid_member"
      /dev/sdj: UUID="7b6938c4-0773-385e-8266-4ae327d728f1" UUID_SUB="746bd731-f2cf-e3ed-2544-221b83de71a0" LABEL="openxeon:0" TYPE="linux_raid_member"
      /dev/sdk1: UUID="6386a07f-090f-4992-8f4e-3a548389a5b0" TYPE="ext4" PARTUUID="0b496f8a-01"
      /dev/sdk5: UUID="f0d2c92d-912f-4899-a5f6-4763fb0d56e7" TYPE="swap" PARTUUID="0b496f8a-05"
    • root@xeonmedia:~# cat /etc/mdadm/mdadm.conf
      # 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
      ARRAY /dev/md0 metadata=1.2 name=openxeon:0 UUID=7b6938c4:0773385e:82664ae3:27d728f1
      root@xeonmedia:~# # definitions of existing MD arrays
      root@xeonmedia:~# ARRAY /dev/md0 metadata=1.2 name=openxeon:0 UUID=7b6938c4:0773385e:82664ae3:27d728f1
      -bash: ARRAY: kommandot finns inte


      root@xeonmedia:~# fdisk -l

      Disk /dev/sda: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk /dev/sdb: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk /dev/sdc: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk /dev/sdd: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk /dev/sde: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk /dev/sdf: 3,7 TiB, 4000787030016 bytes, 7814037168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk /dev/sdg: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk /dev/sdh: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk /dev/sdi: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk /dev/sdj: 2,7 TiB, 3000592982016 bytes, 5860533168 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      Disk /dev/sdk: 29,2 GiB, 31376707072 bytes, 61282631 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: dos
      Disk identifier: 0x0b496f8a
    • I really hope you have the flashmemory plugin installed. I'm guessing the 6 discs are connected to a different controller (or hopefully not usb)? This probably is delay issue where the drives aren't recognized at the time the system and mdadm is started. Look for bios delays. Check cables.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • There must be a delay in the system recognizing them before mdadm starts. Like I said, check the bios for delays. You might have to get a different controller to move the motherboard connected drives.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • hm well i cant find so much to change regarding delay in bios . even tho i takes some time for the bios to work .
      tried to check speed it up , but no change .
      will post pictures from my boot later on.

      . next thing is to check cables.
      i bought a intel pci expresscard , that fixed the speedissue i had .first 100mbit .now 1000mbit . local that is .

      as long i can get my data back , i am ok . but did not expect this.

      can i get my data back?
    • Thomasraid6 wrote:

      can i get my data back?
      Maybe. Hard to say with info I have. I am guessing your usb stick is failing. We highly recommend using the flash memory plugin with flash media installs. I would boot a bootable linux distro like systemrescuecd or even the Ubuntu desktop installer to see if it recognizes your array.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Ok , i really hope so .
      The machine is a HP Z400 so no shit.
      You mean like a new Ubuntu install on new usb/disc ?

      webhallen.com/se-sv/datorer_oc…Kr2lZPvvs8CFanUcgod-xkDDA
      that link goes to the USB i use . no shit memory either. i have 2of them.

      I will post some pics so moderators can see how my boot look , and what errors i got.
      I want to try alot of things before.... , point of no return.
      Thankful for commands that i can use to sort things out.
    • Thomasraid6 wrote:

      You mean like a new Ubuntu install on new usb/disc ?
      Not install. Just start the ISO live. It will give you a full desktop and you can check to see if array is detected.

      Thomasraid6 wrote:

      that link goes to the USB i use . no shit memory either. i have 2of them.
      I would still use the flashmemory on those. I even use it on my Samsung 850 Pro SSD...
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • i have tried alot of different cables and stuff
      will there be any differens i buy a new motherboard with enough sataports
      a discs are found in bios so..
      is it really the usb? I HAVE CLONED THE USB TO AN SSD
      DAMN..

      Tell me all info u need to help me out , please
      Images
      • FullSizeRender13.jpg

        557.38 kB, 3,264×1,018, viewed 91 times
      • FullSizeRender12.jpg

        579.61 kB, 1,454×890, viewed 77 times
      • 123.JPG

        446.03 kB, 1,632×1,224, viewed 74 times

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

    • Thomasraid6 wrote:

      is it really the usb? I HAVE CLONED THE USB TO AN SSD
      If the usb stick is damaged, you can't clone it to an SSD. That will just clone the problem.

      What are the screenshots of? Did you boot a live distro or is that OMV booting?
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • That is omv booting
      I Did try Ubuntu , that Did not seem to mount .
      Rescuecd , Did not mount the array either
      Would like som tool to diagnos the USB

      Can i repair Or serch for the array ?
      Had a mdadm problem 2 years Ago you help me Then Or zubzero
      You Schould have that on first page of omv
      Dont install on USB . In this case , My setup lastad 4days
    • Thomasraid6 wrote:

      I Did try Ubuntu , that Did not seem to mount .
      It shouldn't mount if you boot a live distro. You just want to check cat /proc/mdstat to see if it recognizes all the drives.
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!
    • Assuming sdk is still the boot drive, I would try:

      mdadm --stop /dev/md0
      mdadm --assemble --force --verbose /dev/md127 /dev/sd[abcdefghij]
      omv 4.0.14 arrakis | 64 bit | 4.13 backports kernel | omvextrasorg 4.1.1
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please don't PM for support... Too many PMs!