My OSMC won’t boot properly anymore since the automatic update. Booting loops at the unhappy face every time any time I reboot from the shell. Disk space seems no problem (840MB free on SD). sudo apt-get update && sudo apt-get dist-upgrade && sudo apt-get install -f didn’t help.
Your update has not completed successfully and you are not running an up to date kernel. According to your apt log:
rbp1-image-4.3.0-10-osmc (10) wird eingerichtet ...
However your system journal clearly shows you are booting an old kernel version:
Nov 30 20:02:44 osmc kernel: Linux version 4.2.3-3-osmc (root@vero) (gcc version 4.9.2 (Raspbian 4.9.2-10) ) #1 PREEMPT Tue Oct 13 17:58:31 UTC 2015
Are you sure you took your log files after updating ? Did you reboot since updating ? If you do dist-upgrade from the command line you need to reboot for the new kernel to take effect.
osmc@osmc:~$ ls -al /boot
insgesamt 49851
drwxr-xr-x 10 root root 3584 Jan 1 1970 .
drwxr-xr-x 23 root root 4096 Nov 30 21:54 ..
-rwxr-xr-x 1 root root 10199 Nov 29 20:10 bcm2708-rpi-b.dtb
-rwxr-xr-x 1 root root 10478 Nov 29 20:10 bcm2708-rpi-b-plus.dtb
-rwxr-xr-x 1 root root 17900 Nov 26 14:03 bootcode.bin
-rwxr-xr-x 1 root root 58 Jan 1 1980 cmdline.txt
-rwxr-xr-x 1 root root 101600 Mai 17 2015 config-3.18.13-1-osmc
-rwxr-xr-x 1 root root 104545 Aug 19 23:37 config-4.1.5-1-osmc
-rwxr-xr-x 1 root root 107455 Sep 23 22:21 config-4.2.1-1-osmc
-rwxr-xr-x 1 root root 107476 Okt 13 19:26 config-4.2.3-3-osmc
-rwxr-xr-x 1 root root 113878 Nov 29 17:33 config-4.3.0-10-osmc
-rwxr-xr-x 1 root root 229 Nov 2 19:59 config.txt
drwxr-xr-x 3 root root 512 Jan 1 1980 dtb-3.18.13-1-osmc
drwxr-xr-x 3 root root 512 Sep 12 09:48 dtb-4.1.5-1-osmc
drwxr-xr-x 3 root root 512 Okt 1 21:11 dtb-4.2.1-1-osmc
drwxr-xr-x 3 root root 512 Okt 18 23:38 dtb-4.2.3-3-osmc
drwxr-xr-x 3 root root 512 Nov 30 20:31 dtb-4.3.0-10-osmc
-rwxr-xr-x 1 root root 9684 Nov 26 14:03 fixup_x.dat
-rwxr-xr-x 1 root root 2316 Jan 1 1980 install.log
-rwxr-xr-x 1 root root 7271464 Nov 30 20:57 kernel.img
-rwxr-xr-x 1 root root 1494 Nov 26 14:03 LICENCE.broadcom
drwxr-xr-x 2 root root 2560 Nov 30 20:31 overlays
-rwxr-xr-x 1 root root 215 Mai 24 2015 preseed.cfg
drwxr-xr-x 4 root root 512 Mai 24 2015 .Spotlight-V100
-rwxr-xr-x 1 root root 3811112 Nov 26 14:03 start_x.elf
-rwxr-xr-x 1 root root 1832152 Mai 17 2015 System.map-3.18.13-1-osmc
-rwxr-xr-x 1 root root 1912534 Aug 20 01:26 System.map-4.1.5-1-osmc
-rwxr-xr-x 1 root root 1939896 Sep 24 00:10 System.map-4.2.1-1-osmc
-rwxr-xr-x 1 root root 1941213 Okt 13 21:15 System.map-4.2.3-3-osmc
-rwxr-xr-x 1 root root 1962114 Nov 29 19:25 System.map-4.3.0-10-osmc
drwxr-xr-x 2 root root 512 Mai 24 2015 .Trashes
-rwxr-xr-x 1 root root 4096 Mai 24 2015 ._.Trashes
-rwxr-xr-x 1 root root 5452672 Mai 17 2015 vmlinuz-3.18.13-1-osmc
-rwxr-xr-x 1 root root 5625528 Aug 20 01:26 vmlinuz-4.1.5-1-osmc
-rwxr-xr-x 1 root root 5705832 Sep 24 00:10 vmlinuz-4.2.1-1-osmc
-rwxr-xr-x 1 root root 5710048 Okt 13 21:15 vmlinuz-4.2.3-3-osmc
-rwxr-xr-x 1 root root 7271424 Nov 29 19:25 vmlinuz-4.3.0-10-osmc
osmc@osmc:~$ cat /proc/version
Linux version 4.3.0-10-osmc (root@vero) (gcc version 4.9.2 (Raspbian 4.9.2-10) ) #1 PREEMPT Sun Nov 29 17:03:54 UTC 2015
Thank you for helping, DBMandrake. Unfortunately I noticed your kind response only now.
To your question: I’m quite sure that I had rebooted after dist-upgrade. Repeating the procedure with a reboot resulted in 3 updated packages now but still a sadface boot loop, messaging "Failed to start Authenticate and Authorize Users to run Privileged Tasks".
I then ran systemctl status polkitd.service and journalctl -xn, here’s the result:
osmc@osmc:~$ sudo systemctl status polkitd.service
● polkitd.service - Authenticate and Authorize Users to Run Privileged Tasks
Loaded: loaded (/lib/systemd/system/polkitd.service; static)
Active: failed (Result: signal) since Sa 2015-12-05 18:46:41 CET; 17s ago
Process: 623 ExecStart=/usr/lib/policykit-1/polkitd --no-debug (code=killed, signal=SEGV)
Main PID: 623 (code=killed, signal=SEGV)
Dez 05 18:46:41 osmc systemd[1]: polkitd.service: main process exited, code=killed, status=11/SEGV
Dez 05 18:46:41 osmc systemd[1]: Failed to start Authenticate and Authorize Users to Run Privileged Tasks.
Dez 05 18:46:41 osmc systemd[1]: Unit polkitd.service entered failed state.
osmc@osmc:~$ sudo journalctl -xn
– Logs begin at Sa 2015-12-05 18:44:50 CET, end at Sa 2015-12-05 18:47:13 CET. –
Dez 05 18:46:58 osmc sudo[661]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)
Dez 05 18:46:58 osmc sudo[661]: pam_unix(sudo:session): session closed for user root
Dez 05 18:47:07 osmc mediacenter[413]: Starting Kodi…
Dez 05 18:47:07 osmc sudo[667]: root : TTY=unknown ; PWD=/ ; USER=osmc ; COMMAND=/usr/lib/kodi/kodi.bin --standalone -fs --lirc
Dez 05 18:47:07 osmc sudo[667]: pam_unix(sudo:session): session opened for user osmc by (uid=0)
Dez 05 18:47:07 osmc mediacenter[413]: [131B blob data]
Dez 05 18:47:07 osmc sudo[667]: pam_unix(sudo:session): session closed for user osmc
Dez 05 18:47:07 osmc mediacenter[413]: Kodi exited with return code 127 after 0 hours, 0 minutes and 0 seconds
Dez 05 18:47:13 osmc sudo[681]: osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/journalctl -xn
Dez 05 18:47:13 osmc sudo[681]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)
We’ve never heard of the polkit service crashing before, given the other symptoms and clues I would say that your system has suffered from significant filesystem corruption, so I would recommend backing up any crucial data and doing a fresh install of the latest version of OSMC.
Thank you for responding, DBMandrake. Hmm… are you sure it’s a filesystem corruption? How can I best test for it?
My original idea for this thread was to revert OSMC to an earlier version. What’s the best to do this? I had tried to find instructions on this website, did I overlook something?
I would like to keep as much of the system as possible and just revert to an earlier version of OSMC if possible.
The problem is not going to be with the November update, the problem will be that file system corruption has caused the update process to fail, and seemingly in a fairly peculiar way.
There are at least two signs of corruption - the issue with the wrong kernel booting despite the package supposedly installing, and the polkit service getting corrupted, which as I’ve said, has never been reported before.
This suggests to me underlying corruption and that you are better off starting fresh with the latest version. If you continue to have problems you might have an SD card that is on the way out.
I’m booting OSMC from a USB stick. The SD card is just for the initial boot. This was one of the standard installation options at the time I installed OSMC, maybe it’s related to our problem?