| 1 |
Am 03.05.2014 13:19, schrieb J. Roeleveld: |
| 2 |
|
| 3 |
> Sounds like an issue with the mdadm-raid devices. |
| 4 |
> Try setting those up WITHOUT systemctl (or init.d-scripts) |
| 5 |
> |
| 6 |
> Then checking |
| 7 |
> - /proc/mdstat |
| 8 |
> - dmesg |
| 9 |
> - logging |
| 10 |
> Any of those might show an error. |
| 11 |
> Maybe ssh-in from a seperate machine to enable the raid-devices and have the |
| 12 |
> local machine show a "tail -f" of the logs to see what happens. |
| 13 |
> |
| 14 |
>> Maybe -> dracut ... tell it to assemble the arrays via kernel-option ... |
| 15 |
>> or maybe rebuild the initramfs (not so likely as it should boot with |
| 16 |
>> older kernels/initramfs then). |
| 17 |
> |
| 18 |
> Which mdadm metadata format did you use when creating them? |
| 19 |
> Only 1 or 2 support auto-detection and kernel-assembly |
| 20 |
|
| 21 |
"mdadm -A --scan" assembles both arrays correctly from within the |
| 22 |
emergency mode. Both arrays non-degraded and in sync. |
| 23 |
|
| 24 |
If I then try to change into the equivalent of runlevel 5, the system |
| 25 |
waits and waits again .. |
| 26 |
|
| 27 |
|
| 28 |
>> Yes, lunch .. thanks ;) |
| 29 |
> |
| 30 |
> 13:20, late lunch :) |
| 31 |
|
| 32 |
I am stressed by the fact that my main work machine doesn't work |
| 33 |
correctly and would prefer to have it fixed first. |
| 34 |
|
| 35 |
But yes, I should eat now. |
| 36 |
|
| 37 |
S |
Archives