Hi,
I have an OSMC installation on a Raspberry Pi 3 and it was working well. I bought a 3 B+ and swapped the sd card and now it won’t boot. The installation was up to date before doing the swap. Any idea on how to solve this without reinstalling? I had several applications running on different ports, etc, and I would not want to start from scratch.
Thanks!
Hi @grahamh
I’m attaching here a couple of screenshots. One is from the rpi3b+ and the other one from the rpi3. None of them boot at the moment. I created the logs but when I insert the SD card in a computer I can’t see all the contents. I see a bunch of files but I don’t see a boot or home folders so I can not transfer the logs back to the computer in order to upload them. Besides that, the networking on both raspberry is not working.
If it’s a Windows machine, you’ll only be able to see the /boot partition and files. Th ext4 partition which holds the vast majority of files/folders will not be visible.
Derek
but the logfile is saved to the FAT partition by default, so should be readable in any computer.
It’s a mac. I’ll try again and let you know. Thanks.
my bad. You have to explicitly write the logfile to /boot with grablogs -A -C. But it seems your basic problem could be lack of a network connection.
Can you at least list the files on /boot with sizes and dates and post that here? Here’s mine (despite the name, it is a 3B+):
osmc@pi2b:/boot$ ls -l
total 35731
-rwxr-xr-x 1 root root 23311 Oct 28 16:07 bcm2708-rpi-0-w.dtb
-rwxr-xr-x 1 root root 22808 Oct 28 16:07 bcm2708-rpi-b.dtb
-rwxr-xr-x 1 root root 23067 Oct 28 16:07 bcm2708-rpi-b-plus.dtb
-rwxr-xr-x 1 root root 22585 Oct 28 16:07 bcm2708-rpi-cm.dtb
-rwxr-xr-x 1 root root 24111 Oct 28 16:07 bcm2709-rpi-2-b.dtb
-rwxr-xr-x 1 root root 25307 Oct 28 16:07 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root 25570 Oct 28 16:07 bcm2710-rpi-3-b-plus.dtb
-rwxr-xr-x 1 root root 24083 Oct 28 16:07 bcm2710-rpi-cm3.dtb
-rwxr-xr-x 1 root root 17513 Oct 28 16:07 bcm2835-rpi-a.dtb
-rwxr-xr-x 1 root root 17629 Oct 28 16:07 bcm2835-rpi-a-plus.dtb
-rwxr-xr-x 1 root root 17659 Oct 28 16:07 bcm2835-rpi-b.dtb
-rwxr-xr-x 1 root root 17916 Oct 28 16:07 bcm2835-rpi-b-plus.dtb
-rwxr-xr-x 1 root root 17792 Oct 28 16:07 bcm2835-rpi-b-rev2.dtb
-rwxr-xr-x 1 root root 17617 Oct 28 16:07 bcm2835-rpi-zero.dtb
-rwxr-xr-x 1 root root 17822 Oct 28 16:07 bcm2835-rpi-zero-w.dtb
-rwxr-xr-x 1 root root 18448 Oct 28 16:07 bcm2836-rpi-2-b.dtb
-rwxr-xr-x 1 root root 18266 Oct 28 16:07 bcm2837-rpi-3-b.dtb
-rwxr-xr-x 1 root root 52116 Oct 27 13:21 bootcode.bin
-rwxr-xr-x 1 root root 63 Jan 1 1980 cmdline.txt
-rwxr-xr-x 1 root root 137085 Jun 7 2018 config-4.14.34-2-osmc
-rwxr-xr-x 1 root root 138041 Oct 28 14:47 config-4.14.78-2-osmc
-rwxr-xr-x 1 root root 86 Dec 20 02:52 config.txt
drwxr-xr-x 3 root root 2048 Jan 1 1980 dtb-4.14.34-2-osmc
drwxr-xr-x 3 root root 2560 Dec 17 14:43 dtb-4.14.78-2-osmc
-rwxr-xr-x 1 root root 9891 Oct 27 13:21 fixup_x.dat
-rwxr-xr-x 1 root root 2260 Jan 1 1980 install.log
-rwxr-xr-x 1 root root 8340048 Dec 17 14:44 kernel.img
-rwxr-xr-x 1 root root 1494 Oct 27 13:21 LICENCE.broadcom
drwxr-xr-x 2 root root 15360 Dec 17 14:43 overlays
-rwxr-xr-x 1 root root 4057636 Oct 27 13:21 start_x.elf
-rwxr-xr-x 1 root root 2057922 Jun 7 2018 System.map-4.14.34-2-osmc
-rwxr-xr-x 1 root root 2062975 Oct 28 15:28 System.map-4.14.78-2-osmc
-rwxr-xr-x 1 root root 2686775 Dec 22 10:27 uploadlog.txt
-rwxr-xr-x 1 root root 8321320 Jun 7 2018 vmlinuz-4.14.34-2-osmc
-rwxr-xr-x 1 root root 8340048 Oct 28 15:28 vmlinuz-4.14.78-2-osmcHi again. I’m putting here the log that I finally could manually upload.
Thanks in advance. The log is for the rpi3b+.
As already noted, the network is unreachable from your Pi 3B+. This is likely a result of you having installed pihole, which has caused dhcpcd5 to be installed.
You probably need to remove the dhcpcd5 package in order to get network connectivity back. Unfortunately, unless you can attach a keyboard and get to the command line, things might be a bit tricky. AFAIK, the default systemd timeout is 90 seconds, so a bit of patience might be in order during the startup, since quite a few services will expect network access.
If you can eventually get to the command line, run this:
sudo apt-get purge dhcpcd5
then reboot.
We should work on improving the situation with PiHole as this is happening regularly.
Let’s discuss this on Comms.
Well, I uninstalled dhcpcd5, setup connman to use dhcp on that interface (I was using static ip anyway), configured my router to assign the ip automatically to that mac address, did apt update, dist-upgrade, etc, and so far so good. I have recovered all my applications and they seem to be running as expected.
Thank you all for your help and comments.