mdadm: no arrays found in config file or automatically

  • Hi all!


    I've got the same issue, fresh OMV 5 install under Proxmox VM. I have a bit more complicated hardware: two pass-through 8TB HDDs and two pass-through 8TB USB HDDs (for backup). After a lot of research, this is what solved the issue for me:

    Code
    # echo 'RESUME=UUID=<the UUID of your boot drive here>' > /etc/initramfs-tools/conf.d/resume
    # mdadm --detail --scan >> /etc/mdadm.conf
    # omv-salt deploy run mdadm
    # update-initramfs -u
    # update-grub

    Then reboot OMV. That's it! Hope it could help someone else.

  • Hi all!


    I've got the same issue, fresh OMV 5 install under Proxmox VM. I have a bit more complicated hardware: two pass-through 8TB HDDs and two pass-through 8TB USB HDDs (for backup). After a lot of research, this is what solved the issue for me:

    Code
    # echo 'RESUME=UUID=<the UUID of your boot drive here>' > /etc/initramfs-tools/conf.d/resume
    # mdadm --detail --scan >> /etc/mdadm.conf
    # omv-salt deploy run mdadm
    # update-initramfs -u
    # update-grub

    Then reboot OMV. That's it! Hope it could help someone else.

    I have just tried that and I'm getting the same problem over and over.

    I'm running OMV5 latest ISO with only a NVME plugged as my drive OS, when I install I can reboot and all good but if I do apt upgrade then the grub reconfigures causing this issue (I guess)

    I don't get to boot I get busybox

  • Hi all!


    I've got the same issue, fresh OMV 5 install under Proxmox VM. I have a bit more complicated hardware: two pass-through 8TB HDDs and two pass-through 8TB USB HDDs (for backup). After a lot of research, this is what solved the issue for me:

    Code
    # echo 'RESUME=UUID=<the UUID of your boot drive here>' > /etc/initramfs-tools/conf.d/resume
    # mdadm --detail --scan >> /etc/mdadm.conf
    # omv-salt deploy run mdadm
    # update-initramfs -u
    # update-grub

    Then reboot OMV. That's it! Hope it could help someone else.

    This worked for me

  • Hello everyone, I have a question related to this topic because installing OMV5 on a USB-stick as boot disk (from another USB-installer-stick) still produces this "mdadm: no arrays found in config file or automatically" appearing upon boot (alongside some other error). Even on the very first boot after installation (and insists, despite omv-upgrade to latest).


    The contents of my /etc/initramfs-tools/conf.d/resume file have just the swap partition UUID which, upon installing the flash plugin has to be removed (per instructions) to "avoid mdadm errors" so not sure if the method posted yorgabr can work on USB-boot-disks?


    Moreover, following the flash-plugin instructions (which are a little unclear to me after step 4/5) did not solve this error.


    Your kind advice is very welcome; I fear yorgabr method above is not or cannot be used for non-RAID and flash-plugin-installed systems, correct? I am using a small Intel NUC with 1xSATA (AHCI) port drive for data only, and installed OMV5 on a USB-stick-as-boot-drive. Thanks.

    OpenMediaVault OMV 4.1.3x on Beelink L55 - Intel i3-5005U - 8GB RAM - Crucial MX500 M.2 (2280) 1TB - Samsung 860 QVO (2.5") 2TB

  • This error will appear once, even after making the suggested changes. If the changes are not made it has been my experience that he error will appear a about a dozen times before the boot continues.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 5.x on Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 16GB ECC RAM.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!