• \[SOLVED\] Software RAID0 refuses to boot


    System refuses to boot after /usr/bin changes these days (see also [http://forum.antergos.com/viewtopic.php?f=5&t=1004][0]">viewtopic.php?f=5&t=1004 topic). System reinstall makes no difference. I am now unable to boot Arch systems with swap and /root on software RAID0 md0 and md1. Boot fails with ERROR: unable to find root device…

    Tried also Manjaro - no difference. Has anyone ecountered this?
    Thanks.

    [0]: <a href=

  • System refuses to boot after /usr/bin changes these days (see also [http://forum.antergos.com/viewtopic.php?f=5&t=1004][0]">viewtopic.php?f=5&t=1004 topic). System reinstall makes no difference. I am now unable to boot Arch systems with swap and /root on software RAID0 md0 and md1. Boot fails with ERROR: unable to find root device…

    Tried also Manjaro - no difference. Has anyone ecountered this?
    Thanks.

    [0]: <a href=

  • Try changing your fstab from using the device nodes to device labels like this user did:
    [https://bugs.archlinux.org/task/34706][0]">[https://bugs.archlinux.org/task/34706][1]

    Hopefully that helps!

    [0]: <a href=
    [1]: https://bugs.archlinux.org/task/34706

  • @“lots.0.logs”:1xfnrvnz said:

    Try changing your fstab from using the device nodes to device labels like this user did:
    [https://bugs.archlinux.org/task/34706][0]">[https://bugs.archlinux.org/task/34706][1]

    Hopefully that helps![/quote:1xfnrvnz]

    Thanks for help. Unfortunately, the article exceeds for now my Linux knowledge. Meanwhile I gave up software RAID for swap & root, kept it only for /home and everything works.
    Anyway, it’s not the first time I had a non-booting PC due to software RAID bugs. I had them in Arch and in openSUSE. From my experience, the only distro handling these without a hitch is Fedora. As so, I always wondered (maybe foolishly) why this great tool named Anaconda is Fedora only.

    Thanks again.

    [0]: <a href=
    [1]: https://bugs.archlinux.org/task/34706

  • I think this issue may have something to do with the systemd boot process. Fedora has been using systemd for more time than any other distro and must have work out the kinks. As systemd matures it will get more consistent across distros, Glad to hear you are up and running though!

Posts 5Views 1671
Log in to reply