Am 03.05.2014 13:26, schrieb Stefan G. Weichinger: > Am 03.05.2014 13:19, schrieb J. Roeleveld: > >> Sounds like an issue with the mdadm-raid devices. >> Try setting those up WITHOUT systemctl (or init.d-scripts) >> >> Then checking >> - /proc/mdstat >> - dmesg >> - logging >> Any of those might show an error. >> Maybe ssh-in from a seperate machine to enable the raid-devices and have the >> local machine show a "tail -f" of the logs to see what happens. >> >>> Maybe -> dracut ... tell it to assemble the arrays via kernel-option ... >>> or maybe rebuild the initramfs (not so likely as it should boot with >>> older kernels/initramfs then). >> >> Which mdadm metadata format did you use when creating them? >> Only 1 or 2 support auto-detection and kernel-assembly > > "mdadm -A --scan" assembles both arrays correctly from within the > emergency mode. Both arrays non-degraded and in sync. > > If I then try to change into the equivalent of runlevel 5, the system > waits and waits again .. > > >>> Yes, lunch .. thanks ;) >> >> 13:20, late lunch :) > > I am stressed by the fact that my main work machine doesn't work > correctly and would prefer to have it fixed first. > > But yes, I should eat now.
rebuilt mdadm, lvm2 and dracut from within emergency mode and then recompiled kernel and let dracut rebuild the initramfs. Booted with "rd.auto=1" and now I also get a funny start job running/waiting for /dev/sda1 (/ on the SSD). Oh my! :-) pasta now. Thanks so far, Stefan
