fred44nl
Posts: 292
Joined: Sat Jun 25, 2016 11:59 am
Location: Scharendijke, NL

no reboot after "sudo touch /forcefsck"

Wed Jun 13, 2018 8:24 am

so, I did "sudo rpi-update", which gave me kernel 4.14.48-v7+
next, I did "sudo reboot now", which resulted in a proper reboot.
after that, I did "sudo touch /forcefsck", rebooted and my RPi did not come back.
waited like 15 mins. there was no usb-HD activity.
so I pulled the power-supply.
re-applied power and the RPi booted properly.

this problem also showed itself with kernel 4.14.34

pls. note: I boot from the SD-card and run from an usb-HD.
:
the last entries in /var/log/syslog, before I pulled the power-supply, are:
Jun 12 11:49:34 raspberrypi ntpd[577]: Soliciting pool server 87.233.197.123
Jun 12 11:49:34 raspberrypi ntpd[577]: Soliciting pool server 83.162.251.163
Jun 12 11:49:34 raspberrypi ntpd[577]: Soliciting pool server 94.228.220.14
Jun 12 11:49:34 raspberrypi ntpd[577]: Soliciting pool server 149.210.199.182
Jun 12 11:49:35 raspberrypi ntpd[577]: Soliciting pool server 83.247.2.80
Jun 12 11:49:35 raspberrypi ntpd[577]: Soliciting pool server 217.23.3.234
Jun 12 11:49:35 raspberrypi ntpd[577]: Soliciting pool server 5.39.184.5
Jun 12 11:49:35 raspberrypi dhcpcd[504]: eth0: no IPv6 Routers available
Jun 12 11:49:36 raspberrypi ntpd[577]: Soliciting pool server 45.32.4.67
Jun 12 11:49:36 raspberrypi ntpd[577]: Soliciting pool server 83.98.155.30
Jun 12 11:49:37 raspberrypi ntpd[577]: Soliciting pool server 85.255.214.66
Jun 12 11:49:37 raspberrypi ntpd[577]: Soliciting pool server 2001:bc8:2bf2;100::
note: the semi-colon in the last line was a colon, but that displays something strange.

where does it go wrong ??
headless RPi 3B running from usbhdd.

epoch1970
Posts: 2019
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: no reboot after "sudo touch /forcefsck"

Wed Jun 13, 2018 9:56 am

I would advise against using "rpi-update".
That pulls development firmware and kernels:
- you have no guarantee either will work,
- only a few users will ever run the same system as you.

If you want a good running system and community support use only released versions (from apt-get upgrade)
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

fred44nl
Posts: 292
Joined: Sat Jun 25, 2016 11:59 am
Location: Scharendijke, NL

Re: no reboot after "sudo touch /forcefsck"

Wed Jun 13, 2018 10:20 am

epoch1970 wrote:
Wed Jun 13, 2018 9:56 am
I would advise against using "rpi-update".
That pulls development firmware and kernels:
yes, I know, but this was advised in this topic:

viewtopic.php?f=28&t=215625
headless RPi 3B running from usbhdd.

epoch1970
Posts: 2019
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: no reboot after "sudo touch /forcefsck"

Wed Jun 13, 2018 10:56 am

Why change thread then?
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

fred44nl
Posts: 292
Joined: Sat Jun 25, 2016 11:59 am
Location: Scharendijke, NL

Re: no reboot after "sudo touch /forcefsck"

Thu Jun 14, 2018 9:24 am

well, because my problem is not the same as what the original poster had.
headless RPi 3B running from usbhdd.

epoch1970
Posts: 2019
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: no reboot after "sudo touch /forcefsck"

Thu Jun 14, 2018 9:07 pm

The "problem" can't be solved by anybody not running that version.
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

Return to “Troubleshooting”

Who is online

Users browsing this forum: Bing [Bot] and 72 guests