mdadm no arrays found errors - faulty SSD to blame!

  • Just sharing this for future reference, hopefully to save hair pulling for somebody along the line!


    I built an OMV box using a large case and a known good motherboard, CPU and memory. I was combining 10 HDDs from 2 old boxes but all drives were known good.


    I got a used Dell H310 SAS card from a reputable eBayer to host eight of the HDD's, connected the other 2 to the motherboard SATA and put the OMV operating system on a small SSD.


    I soon was getting lots of problems which I couldn't make sense of - sometimes the system booted fine, often it got to the GRUB menu but then had lots of mdadm no arrays found errors and dropped out to BusyBox. I tried various fixes relating to GRUB in case that was corrupted, but no change.


    Sometimes the system didn't find the OS drive at all. I tried changing power and data cables, but no change.


    I thought there might be an intermittent fault with the SAS card, causing some weird conflict with motherboard BIOS, and this led me on a fruitless internet goose chase.


    Finally it occurred to me that the SSD might be faulty. So I bought Crucial's smallest SSD, cloned the OS to that with Clonezilla and hey presto, everything working as it should.


    What I don't quite understand is why the system, once booted, would run for many hours without fault - suggests that SSD only had an intermittent problem at power-up I guess.

    OMV 7 on Raspberry Pi 3/4/5, Odroid C2/HC2 and three cobbled together x64 boxes running Snapraid.

    • Offizieller Beitrag

    inally it occurred to me that the SSD might be faulty. So I bought Crucial's smallest SSD, cloned the OS to that with Clonezilla and hey presto, everything working as it should.

    I'm surprised you didn't clone the problem to the new SSD. Glad it worked though.


    What I don't quite understand is why the system, once booted, would run for many hours without fault - suggests that SSD only had an intermittent problem at power-up I guess.

    If the bad block was in initramfs, I could see this happening.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!