Having a strange issue with systemd.
I had my ssd fail the other day and finally got around to replacing it.
I replaced it with the newer revision of what I originally had but I switched up my install a bit to save room for the Windows install since this is a dual boot machine. Normally I would put root, home and swap all on the same drive but today I just put my root partition on the ssd and home and swap on a secondary 7200rpm hdd.
As normal I did all my video driver and kernel installing through smxi and the installed systemd by running
get systemd
Install was fine so I then added
init=/lib/systemd/systemd
to grub and then ran
sudo update-grub
Everything seemed just fine until I reboot and the boot process stalled out on
(http://en.zimagez.com/miniature/download67.jpg) (http://en.zimagez.com/zimage/download67.php)
I seem to remember someone else (maybe Jedi) having a similar issue. Did this ever get figured out?
Could this be caused by having root and home on seperate physical drives?
When I rebooted and edit grub and removed
init=/lib/systemd/systemd
the boot process was perfect with no errors and it booted right up.
Edit:
I should mention that although the boot process stalls with systemd enabled it does finally boot after about 5-7 min of waiting and wheeping.
I believe you have to install systemd before Liquorix or any smxi activity... I ran into that same thing when I first tested it
Right on. Ill reinstall and let you know if that fixes it
In this How To (http://vsido.org/index.php/topic,306.0.html) is where I stated...
Quote from: VastOne on April 07, 2013, 02:18:09 PM
This should only be done on a Debian Kernel install. If you try it on Liquorix, you will see a Kernel Panic[/url]