I’ve only had OSMC running for a week and had a message pop up that rbp2-image-4.3.3-3-osmc fails to install.
apt-get log:
Reading package lists…
Building dependency tree…
Reading state information…
The following packages were automatically installed and are no longer required:
rbp2-image-4.3.0-10-osmc rbp2-image-4.3.3-1-osmc rbp2-image-4.3.3-2-osmc
Use ‘apt-get autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up rbp2-image-4.3.3-2-osmc (2) …
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.3.3-2-osmc /boot/vmlinuz-4.3.3-2-osmc
run-parts: executing /etc/kernel/postinst.d/inform-updater 4.3.3-2-osmc /boot/vmlinuz-4.3.3-2-osmc
run-parts: executing /etc/kernel/postinst.d/process-vmlinuz-rbp 4.3.3-2-osmc /boot/vmlinuz-4.3.3-2-osmc
find: `/boot/dtb-4.3.3-2-osmc/overlays/’: No such file or directory
Aborting due to one or more missing device tree overlays.
run-parts: /etc/kernel/postinst.d/process-vmlinuz-rbp exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/rbp2-image-4.3.3-2-osmc.postinst line 391.
dpkg: error processing package rbp2-image-4.3.3-2-osmc (–configure):
subprocess installed post-installation script returned error exit status 2
Setting up rbp2-image-4.3.3-3-osmc (3) …
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.3.3-3-osmc /boot/vmlinuz-4.3.3-3-osmc
run-parts: executing /etc/kernel/postinst.d/inform-updater 4.3.3-3-osmc /boot/vmlinuz-4.3.3-3-osmc
run-parts: executing /etc/kernel/postinst.d/process-vmlinuz-rbp 4.3.3-3-osmc /boot/vmlinuz-4.3.3-3-osmc
- Failed to create ‘/boot/kernel.img’
cp: cannot remove ‘/boot/kernel.img’: Read-only file system
Reverting to previous kernel due to mkknlimg failure.
run-parts: /etc/kernel/postinst.d/process-vmlinuz-rbp exited with return code 30
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/rbp2-image-4.3.3-3-osmc.postinst line 391.
dpkg: error processing package rbp2-image-4.3.3-3-osmc (–configure):
subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of rbp2-kernel-osmc:
rbp2-kernel-osmc depends on rbp2-image-4.3.3-3-osmc; however:
Package rbp2-image-4.3.3-3-osmc is not configured yet.
dpkg: error processing package rbp2-kernel-osmc (–configure):
dependency problems - leaving unconfigured
Seems you have a problem with your boot partition.
Can you provide the URL that you get from grab-logs -A
For me it looks like you SD card is dying. But maybe wait for someone else to check the log files.
Jan 04 22:07:40 osmc kernel: FAT-fs (mmcblk0p1): error, invalid access to FAT (entry 0x00390070)
Jan 04 22:07:40 osmc kernel: FAT-fs (mmcblk0p1): Filesystem has been set read-only
Jan 04 22:07:40 osmc kernel: FAT-fs (mmcblk0p1): error, invalid access to FAT (entry 0x00390070)
Jan 04 22:07:40 osmc kernel: FAT-fs (mmcblk0p1): error, invalid access to FAT (entry 0x479f7876)
Jan 04 22:07:40 osmc kernel: FAT-fs (mmcblk0p1): error, invalid access to FAT (entry 0x479f7876)
Jan 04 22:07:40 osmc kernel: FAT-fs (mmcblk0p1): error, invalid access to FAT (entry 0x00390070)
Jan 04 22:07:40 osmc kernel: FAT-fs (mmcblk0p1): error, invalid access to FAT (entry 0x00390070)
Jan 04 22:07:40 osmc kernel: FAT-fs (mmcblk0p1): error, invalid access to FAT (entry 0x479f7876)
Jan 04 22:07:40 osmc kernel: FAT-fs (mmcblk0p1): error, invalid access to FAT (entry 0x479f7876)
Jan 04 22:07:40 osmc kernel: FAT-fs (mmcblk0p1): error, invalid access to FAT (entry 0x479f9f22)
Jan 04 22:07:40 osmc kernel: FAT-fs (mmcblk0p1): error, invalid access to FAT (entry 0x479f9f22)
Jan 04 22:07:45 osmc kernel: mmc0: unexpected transfer timeout
Jan 04 22:07:45 osmc kernel: mmc0: cmd op 24 arg 0x1e1b2 flags 0xb5 - resp 00000900 00000000 00000000 00000000, err 0
Jan 04 22:07:45 osmc kernel: mmc0: data blocks 1 blksz 200 - err 0
Jan 04 22:07:45 osmc kernel: mmc0: =========== REGISTER DUMP ===========
Jan 04 22:07:45 osmc kernel: mmc0: SDCMD 0x00000098
Jan 04 22:07:45 osmc kernel: mmc0: SDARG 0x0001e1b2
Jan 04 22:07:45 osmc kernel: mmc0: SDTOUT 0x017d7840
Jan 04 22:07:45 osmc kernel: mmc0: SDCDIV 0x00000007
Jan 04 22:07:45 osmc kernel: mmc0: SDRSP0 0x00000900
Jan 04 22:07:45 osmc kernel: mmc0: SDRSP1 0x0000182e
Jan 04 22:07:45 osmc kernel: mmc0: SDRSP2 0xffffffff
Jan 04 22:07:45 osmc kernel: mmc0: SDRSP3 0x0002400f
Jan 04 22:07:45 osmc kernel: mmc0: SDHSTS 0x00000001
Jan 04 22:07:45 osmc kernel: mmc0: SDVDD 0x00000001
Jan 04 22:07:45 osmc kernel: mmc0: SDEDM 0x00010807
Jan 04 22:07:45 osmc kernel: mmc0: SDHCFG 0x0000050e
Jan 04 22:07:45 osmc kernel: mmc0: SDHBCT 0x00047bd1
Jan 04 22:07:45 osmc kernel: mmc0: SDHBLC 0x00000000
Jan 04 22:07:45 osmc kernel: mmc0: ===========================================
Jan 04 22:07:45 osmc kernel: mmc0: unexpected command 13 error
Jan 04 22:07:45 osmc kernel: mmc0:>cmd op 13 arg 0xb3680000 flags 0x195 - resp 00000000 00000000 00000000 00000000, err 0
Jan 04 22:07:45 osmc kernel: mmc0: =========== REGISTER DUMP ===========
Hmm, it’s a brand new card. Maybe I bought a bum one. 
Thanks for looking at the log.
Your card is probably fine but appears to be affected by the sdhost compatibility issue discussed here. This has resulted in file system corruption and your /boot partition going read only.
Please try a fresh install of the November release and then updating - this will take you to the December release with the 4.3.3-3-osmc kernel, which should work fine for you. (4.3.3-1-osmc and 4.3.3-2-osmc are the problematic kernels for you)
Your problem is not with 4.3.3-3-osmc, but with the previous kernel you were running during the upgrade to 4.3.3-3-osmc having issues with the SD card thus causing corruption.
There is likely too much file system corruption for the system to be salvageable without a fresh install, even if it does appear to be booting.
Please also post the exact make and model of your SD card.
Actually I was wrong, it’s not a new card; I have been using it for some time.
It was a Lexar 8GB.
I did a fresh install on a Kingston 16GB Card and updated to the December release without issue. Thanks.
Some Lexar cards have been reported to have issues with the sdhost driver, so that was probably your original issue.