I have a Pi 3b which now just boots as far as the OSMC blue screen with the OSMC in the O in the middle then the screen goes black and that is it. It does not get as far as networking as I cannot see it trying to get a lease either by Ethernet or Wireless. How can I troubleshoot further? Can I interrupt the boot process somehow to watch a text boot? Can I read the microSD elsewhere or perhaps try an fsck on it. I do have access to other Linux servers it it helps with troubleshooting.
Have you tried another display?
I hadn’t as it was a working TV but I have done now with a different cable. It didn’t help. I’ve also tried 3 PSUs.
I don’'t know if it helps but when it boots I see a couple of lines, one of which is “Recovering journal” before the OSMC splash screen appears.
I’ve stuck the microSD in a debian machine. fsck shows it clean so I’ve mounted it and am trying to copy stuff off and I am seeing errors;
root@pve:/# cp -a /mnt/pi /mnt/nfs-raid
cp: error reading '/mnt/pi/usr/share/kodi/system/keyboardlayouts/portuguese.xml': Input/output error
cp: error reading '/mnt/pi/usr/share/kodi/system/keyboardlayouts/romanian.xml': Input/output error
cp: error reading '/mnt/pi/usr/share/kodi/system/keyboardlayouts/russian.xml': Input/output error
cp: error reading '/mnt/pi/usr/share/kodi/system/keyboardlayouts/silesian.xml': Input/output error
cp: error reading '/mnt/pi/usr/share/kodi/addons/vfs.libarchive/resources/language/resource.language.ta_in/strings.po': Input/output error
cp: error reading '/mnt/pi/usr/share/kodi/addons/vfs.libarchive/resources/language/resource.language.te_in/strings.po': Input/output error
It is going dreadfully slowly, but I’ll let it keep going. It seems to be stuck atm so it has probably hit another bad file.
What is the point in trying to recover anything but ~/.kodi? Clearly your going to have to do a clean install, probably on a new SD. I would test the card after recovery using h2testw. There seems to be plenty of fakes out there nowadays.
1 Like
Hi,
It seems like your SD card may be problematic.
Some SD cards are not genuine or have a lower capacity than advertised. Some simply fail over time.
Symptoms of SD cards not working correctly are:
- Read-only behaviour, or changes made not persisting
- A filesystem corruption error
Symptoms of counterfeit SD cards are:
- Writing works until a certain filesystem size is reached, thereafter, writes seem to cause issues where existing data is lost or newly written data is not preserved.
- SD card fails after a short amount of time.
Counterfeit cards are usually found on Amazon and eBay.
SD cards have a limited lifespan. I recommend you change SD card and suspect that issues will no longer persist with a good card. If you would like to be a good quality SD card purpose manufactured for OSMC, then you can find one in the Store.
1 Like
Thanks for the responses.
The tip about ~/.kodi is great. I was pretty certain there was a config somewhere I needed if I was rebuilding. There are other bits I need as well like /etc/fstab because I mount a remote smb share for my streaming rather than use DLNA. I also use it as an rsync target for remote backups of my main server. I found rsync could skip faulty files which is good. I think I have the essentials, but I can go through what I have in slow time.
The card is a 400GB card I’ve been using for a few years. The problem only started when I tripped the mains switch so I was hoping it was a damaged file system rather than a faulty card.
I’ve reinstalled on the same MicroSD card as I am waiting for a new one to arrive. I struggled with networking. I pre-entered my WiFi data but the WiFi never connected. In the end I connected by ethernet and copied in the WiFi settings file from the salvaged files and it connected.
I bumped into something on the Wiki about autofs and I though I’d try it for my smb share. I’d already mounted the share through /etc/fstab which was problematic as mount -a didn’t reload the /etcfstab, but the file loaded correctly on boot.
How do I unmount the drive now to try /etc/fstab? If I try to umount it, it fails as the drive is in use. Presumably this is kodi locking it? How can I temporarily unmount the mount?
You can stop Kodi using…
systemctl stop mediacenter
Assuming you meant to disable to ftab mount to try autofs you can also just comment out (pound sign in front of the entry) in your fstab and reboot. For the regular umount and whatnot you can just google Debian terminal instructions to find working commands.
Thanks. I am comfortable with umount and use it often. I know it fails if files are in use. Rather than digging with lsof, I thought I’d just ask.
I still don’t understand why mount -a didn’t work but rebooting did. Wierd.
And yes, I would like to experiment with autofs as I’ve never used it before. I don’t want to reboot as it takes over the TV when my son is playing Switch games on it. Stopping mediacenter will probably do it.
I now have autofs working thanks.
I now have another problem. The old installation had Disney+ installed and this is not working in the new installation. I remembered to install python3-pycryptodome. I have been through the instructions to install Disney+ again, using https://www.makeuseof.com/tag/netflix-amazon-video-plex-raspberry-pi/. I can run Disney+. When I first tried to play a movie, I had to upgrade Widevine again and this seems OK. Now when I try to play a movie, after selecting the required resolution and bitrate, I get an OSMC sad face. I have to wait a bit and it then goes back to the main screen. It does this every time. I have tried rebooting, but it didn’t help/
I have tried looking in the journal and, I think every time it crashes (gives the sad face), I am gettng a segfault:
Apr 16 21:30:32 osmc mediacenter[343]: /usr/bin/mediacenter: line 149: 660 Segmentation fault sudo -u osmc LIRC_SOCKET_PATH=/var/run/lirc/lircd $KODI --standalone -fs
Apr 16 21:30:32 osmc mediacenter[343]: Kodi exited with return code 139 after 0 hours, 0 minutes and 46 seconds
Apr 16 21:30:32 osmc mediacenter[759]: mode "1920x1080"
Apr 16 21:30:32 osmc mediacenter[759]: geometry 1920 1080 1920 1080 16
Apr 16 21:30:32 osmc mediacenter[759]: timings 0 0 0 0 0 0 0
Apr 16 21:30:32 osmc mediacenter[759]: accel true
Apr 16 21:30:32 osmc mediacenter[759]: rgba 5/11,6/5,5/0,0/0
Apr 16 21:30:32 osmc mediacenter[759]: endmode
Apr 16 21:30:44 osmc mediacenter[343]: Starting Kodi...
Also, once I got:
Apr 16 21:32:24 osmc kernel: BUG: using smp_processor_id() in preemptible [00000000] code: VideoPlayer/990
Apr 16 21:32:24 osmc kernel: caller is debug_smp_processor_id+0x20/0x24
Apr 16 21:32:24 osmc kernel: CPU: 1 PID: 990 Comm: VideoPlayer Tainted: G C 5.10.78-7-osmc #1
Apr 16 21:32:24 osmc kernel: Hardware name: BCM2835
Apr 16 21:32:24 osmc kernel: Backtrace:
Apr 16 21:32:24 osmc kernel: [<80b8ce34>] (dump_backtrace) from [<80b8d1a4>] (show_stack+0x20/0x24)
Apr 16 21:32:24 osmc kernel: r7:00000000 r6:00000000 r5:680e0113 r4:812e5fac
Apr 16 21:32:24 osmc kernel: [<80b8d184>] (show_stack) from [<80b91e0c>] (dump_stack+0xb8/0xe4)
Apr 16 21:32:24 osmc kernel: [<80b91d54>] (dump_stack) from [<80b96188>] (check_preemption_disabled+0x110/0x114)
Apr 16 21:32:24 osmc kernel: r7:81b48000 r6:00000001 r5:80b961ac r4:000003de
Apr 16 21:32:24 osmc kernel: [<80b96078>] (check_preemption_disabled) from [<80b961ac>] (debug_smp_processor_id+0x20/0x24)
Apr 16 21:32:24 osmc kernel: r7:833ef000 r6:9fb23a20 r5:0000000f r4:81b48000
Apr 16 21:32:24 osmc kernel: [<80b9618c>] (debug_smp_processor_id) from [<80b9f8d4>] (do_page_fault+0x374/0x3b8)
Apr 16 21:32:24 osmc kernel: [<80b9f560>] (do_page_fault) from [<801198b0>] (do_DataAbort+0x4c/0xcc)
Apr 16 21:32:24 osmc kernel: r10:00000007 r9:536af3dc r8:10c5387d r7:8120acc4 r6:88a87fb0 r5:9fb23a20
Apr 16 21:32:24 osmc kernel: r4:0000000f
Apr 16 21:32:24 osmc kernel: [<80119864>] (do_DataAbort) from [<80100dc4>] (__dabt_usr+0x44/0x60)
Apr 16 21:32:24 osmc kernel: Exception stack(0x88a87fb0 to 0x88a87ff8)
Apr 16 21:32:24 osmc kernel: 7fa0: 00000003 7ef4ad94 031a9710 00000014
Apr 16 21:32:24 osmc kernel: 7fc0: 536af3cc 0067adc5 4c474654 7ef4ad94 031a9710 536af3dc 00000007 5a0afdb4
Apr 16 21:32:24 osmc kernel: 7fe0: 00000006 5a0af988 76ef3f41 0067adc8 080e0030 ffffffff
Apr 16 21:32:24 osmc kernel: r8:10c5387d r7:10c5383d r6:ffffffff r5:080e0030 r4:0067adc8
Does anyone have any ideas?