| 1 |
On Mon, Jan 20, 2014 at 7:38 AM, <covici@××××××××××.com> wrote: |
| 2 |
> Hi. I am having a problem booting using systemd and an initrd generated |
| 3 |
> by genkernel. |
| 4 |
> |
| 5 |
> I get the message that says (may be slight paraphrase) that |
| 6 |
> /dev/mapper/linux--files-64--root does not appear to be a valid /, try |
| 7 |
> again. |
| 8 |
> |
| 9 |
> Now in the gentoo guide to systemd, I did what I think it wanted me to |
| 10 |
> do and wrote in my lilo append line real_init=/usr/lib/systemd/systemd |
| 11 |
> . Now looking at the linuxsrc in the initrd, /usr is not even mounted |
| 12 |
> when it is looking for its init -- after all that fuss about /usr -- and |
| 13 |
> it only seems to look in /sbin for its init and dies. |
| 14 |
> |
| 15 |
> How can I solve this problem -- I suppose I could copy systemd over, but |
| 16 |
> that seems nasty to me and I would have to remember to update it every |
| 17 |
> time systemd was updated! |
| 18 |
> |
| 19 |
> Any assistance on this would be appreciated. |
| 20 |
> |
| 21 |
|
| 22 |
This is bug 479730. https://bugs.gentoo.org/show_bug.cgi?id=479730 |
| 23 |
|
| 24 |
One solution would be to switch to genkernel-next. I recommend the |
| 25 |
latest ~arch version. |
| 26 |
|
| 27 |
Another solution would be to use dracut. |
Archives