It seems that right after local-fs.target doesn't work. Any idea what prevents it from working early in the boot process?

  • Does it spit out any errors (e.g. in journalctl) that might point towards what's missing? – Aurora0001 Jan 19 '18 at 20:22
  • Unfortunately it doesn't say much, except that my disableusb script (I placed the camera stuff there as a test) failed to start. Then it just hangs, it will never get to the serial console login, so I have to power off, put the card in my pc and comment out the camera line there. Lucky for me, I can access (r/w) file systems from my Windows machine, or else it would really suck :) – Radu Jan 19 '18 at 21:05
  • unclear what are you asking – Chetan Bhargava Jan 24 '18 at 17:00
  • You need to provide more details: the exact command that fails, the error messages (have you tried raspistill blabla 2>&1 >error.log?), relevant details about your boot process. – Dmitry Grigoryev Jan 29 '18 at 14:58

I found the problem, by manually starting the script after the log in. The camera cable moved a bit and I was getting an error, and for some reason things didn't continue after that. Now it works ok.

| improve this answer | |
  • Please accept your own answer with a click on the tick on its left side. Only this will finish the question and it will not pop up again year for year. – Ingo Mar 2 at 13:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.