gmc
Posts: 123
Joined: Fri Mar 09, 2012 11:31 am
Location: Cheshire, UK
Contact: Website

sudo reboot not working?

Sat Apr 05, 2014 6:26 am

My pi has been running for about a year now as a weather station and on it I schedule a weekly reboot with

Code: Select all

sudo /sbin/reboot
For the last few week now after the reboot kicks in the pi reboots but doesn't seem to startup again. I need to pull the power and then it starts up normally.

I have also now tried ssh'ing in and running a reboot. It shuts down but doesn't come back up.

Anyone know what could be causing this? Its been running fine for ages. I also do weekly updates - could that have caused a problem?

Here are the last few lines of the messages on the reboot.
Apr 5 05:07:29 weather kernel: [ 8.160795] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5390, rev 0502 detected
Apr 5 05:07:29 weather kernel: [ 8.269152] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5370 detected
Apr 5 05:07:29 weather kernel: [ 8.306674] usb_audio: Warning! Unlikely big volume range (=6144), cval->res is probably wrong.
Apr 5 05:07:29 weather kernel: [ 8.368587] usb_audio: [5] FU [Mic Capture Volume] ch = 1, val = 1536/7680/1<6>[ 8.424274] usbcore: registered new interface driver snd-usb-audio
Apr 5 05:07:29 weather kernel: [ 9.030728] usbcore: registered new interface driver rt2800usb
Apr 5 05:07:29 weather kernel: [ 20.429099] EXT4-fs (mmcblk0p6): re-mounted. Opts: (null)
Apr 5 05:07:29 weather kernel: [ 20.936484] EXT4-fs (mmcblk0p6): re-mounted. Opts: (null)
Apr 5 05:07:29 weather kernel: [ 21.758309] i2c /dev entries driver
Apr 5 05:07:29 weather kernel: [ 27.390699] FAT-fs (mmcblk0p5): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Apr 5 05:07:29 weather kernel: [ 30.284573] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
Apr 5 05:07:29 weather kernel: [ 30.291697] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.29
Apr 5 05:07:29 weather kernel: [ 30.916390] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Apr 5 05:07:29 weather kernel: [ 34.124581] wlan0: authenticate with f4:ec:38:d0:a1:5e
Apr 5 05:07:29 weather kernel: [ 34.177119] wlan0: send auth to f4:ec:38:d0:a1:5e (try 1/3)
Apr 5 05:07:29 weather kernel: [ 34.178864] wlan0: authenticated
Apr 5 05:07:29 weather kernel: [ 34.180105] rt2800usb 1-1.2.3:1.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
Apr 5 05:07:29 weather kernel: [ 34.180145] rt2800usb 1-1.2.3:1.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
Apr 5 05:07:29 weather kernel: [ 34.189558] wlan0: associate with f4:ec:38:d0:a1:5e (try 1/3)
Apr 5 05:07:29 weather kernel: [ 34.191982] wlan0: RX AssocResp from f4:ec:38:d0:a1:5e (capab=0x431 status=0 aid=30)
Apr 5 05:07:29 weather kernel: [ 34.207697] wlan0: associated
Apr 5 05:07:29 weather kernel: [ 34.331820] bcm2835-cpufreq: switching to governor ondemand
Apr 5 05:07:29 weather kernel: [ 34.331852] bcm2835-cpufreq: switching to governor ondemand
Apr 5 05:07:30 weather kernel: [ 37.108492] Adding 102396k swap on /var/swap. Priority:-1 extents:1 across:102396k SSFS

User avatar
DougieLawson
Posts: 39120
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: sudo reboot not working?

Sun Apr 06, 2014 6:51 pm

Note: Any requirement to use a crystal ball or mind reading will result in me ignoring your question.

Criticising any questions is banned on this forum.

Any DMs sent on Twitter will be answered next month.
All non-medical doctors are on my foes list.

gmc
Posts: 123
Joined: Fri Mar 09, 2012 11:31 am
Location: Cheshire, UK
Contact: Website

Re: sudo reboot not working?

Sun Apr 06, 2014 7:22 pm

Thanks. I followed the steps and am still having the same problem.

Update: Wait..I see there is more...Let me try the other steps in that thread. :)

Ok - tried the other method. Still not working :(

Code: Select all

 FAT-fs (mmcblk0p5): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Return to “Troubleshooting”