So basically, after the november update the mediacenter.
I’m not sure if I’m facing similar technical problems as November update: Unhappy face loop at boot , but these are the steps that I’ve tried:
press ‘esc’ on frownieface, gained shell → logged in:
- mount -o rw /boot
- nano /boot/cmdline.txt
- appended init=/bin/bash to file mentioned above
- rebooted, directly went into shell
- fsck’ed mmcblk0p2, all seemed good
- fsck’ed mmcblk0p1, removed sticky/dirty bit (can’t remember, think it’s sticky)
- mount -o rw /boot
- nano /boot/cmdline.txt
- removed the init=/bin/bash part
- echo s >/proc/sysrq-trigger
- echo u >/proc/sysrq-trigger
- echo b >/proc/sysrq-trigger
- system booted, still had crashing mediacenter
- noticed while starting up that transmission had failed to load
- sudo systemctl disable mediacenter
- sudo systemctl disable transmission
- sudo reboot
- system booting, halted at:
[TIME] Timed out waiting for device dev-disk-by …randomidblabla
[DEPEND] Dependency failed for /mnt/TOSHIBA
[DEPEND]Dependency failed for File System Check on /dev/disk…differentidthanabove
now it’s just sitting there. Any clue how to at least get me back in to a shell, and even better - fix the mediacenter crashing? I’m aware of the paste-log command, just need to get into a shell first
p.s. re-installing is not an option, unfortunately
edit:
- put SD card in pc, added init=/bin/bash manually
- put back in raspberry
- mount -o rw /
- systemctl enable mediacenter
- mount -o rw /boot
- nano /boot/cmdline.txt
- removed init=/bin/bash
- echo s >/proc/sysrq-trigger
- echo u >/proc/sysrq-trigger
- echo b >/proc/sysrq-trigger
- booted into mediacenter again, still crashing
- sudo journalctl | paste-log = “contained link, not relevant anymore”
- paste-log /home/osmc/.kodi/temp/kodi.log = “contained link, not relevant anymore”
this seems relevant:
Dec 11 23:29:16 OSMC mediacenter[338]: Could not init logging classes. Permission errors on ~/.kodi (/home/osmc/.kodi/temp/)
Dec 11 23:29:16 OSMC mediacenter[338]: ERROR: Unable to create application. Exiting
Dec 11 23:29:16 OSMC sudo[401]: pam_unix(sudo:session): session closed for user osmc
Dec 11 23:29:16 OSMC mediacenter[338]: Kodi exited with return code 255 after 0 hours, 0 minutes and 4 seconds
fixed. For some reason I probably entered a wrong command, but my whole /home/osmc/ folder was owned by www-data. Such Linux pro, much wow.