Timeline for How to disable systemd service manually?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 19, 2018 at 19:04 | comment | added | XP1 | @Patrick, I think that @dsstorefile's solution worked and that the time sync could be why it got stuck the first time. After I ran sudo ln -s /dev/null /media/user/%UUID%/etc/systemd/system/systemd-timesyncd.service, it was able to boot past the failed time sync. However, I ran into a completely separate, unrelated problem, but I was able to figure out how to fix it. I have documented my solution here: raspberrypi.stackexchange.com/questions/83044/… | |
| Apr 19, 2018 at 15:14 | comment | added | ajeh | At this point you are better off reinstalling the OS from scratch. Unless you want to learn a lot by just fooling around, which is perfectly fine contrary to hysterical comments you may read here. This is your system, you own it, and it is perfectly fine to fool around with it. | |
| Apr 19, 2018 at 6:37 | answer | added | Antonio Petricca | timeline score: 2 | |
| Apr 19, 2018 at 5:09 | comment | added | JdeBP | Further to Patrick: Stop! You are floundering around. In bootstrap and shutdown the last thing printed on the screen does not necessarily bear any relationship to what your computer is doing. Look at the logs. Use the rescue and emergency modes. Invoke the kbrequest login. Determine what your system is doing. Then address that. | |
| Apr 19, 2018 at 2:44 | comment | added | phemmer | If you see "Failed to start Network Time Synchronization", then that's not what it's stuck on. That message means it gave up and moved on. | |
| Apr 19, 2018 at 2:19 | history | asked | XP1 | CC BY-SA 3.0 |