Please report this on the OSMC forum.
Log code: kimabasoho
Well, well, well
dpkg: trying script from the new package instead ... /boot is not mounted!
Not sure if this is an entertainment show but you commented out the boot drive in fstab that obviously will break OSMC
====================== fstab =================== qiE9Dtax #/dev/mmcblk0p1 /boot vfat defaults,noatime 0 0 /dev/mmcblk0p2 / ext4 defaults,noatime 0 0
Yes it was.
So I uncommented it, like this:
/dev/mmcblk0p1 /boot vfat defaults,noatime 0 0 /dev/mmcblk0p2 / ext4 defaults,noatime 0 0
But I have still the same issue.
Did you reboot?
Provide new logs!
AFAIK the root partition can be left commented
Yes I have rebooted.
This is my complete fstab:
/dev/mmcblk0p1 /boot vfat defaults,noatime 0 0 /dev/mmcblk0p2 / ext4 defaults,noatime 0 0
#UUID=9b7cb0d6-4b06-42a2-a949-17c05a3c9b94 /mnt/usbstorage ext4 nofail,defaults 0 0
#UUID=9b7cb0d6-4b06-42a2-a949-17c05a3c9b94 /mnt/usbstorage vfat nofail,defaults 0 0
//192.168.1.12/WDMYCLOUD /mnt/WDMYCLOUD cifs x-systemd.automount,noauto,rw,iocharset=utf8,guest,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770,vers=1.0 0 0
and my new log:
xuvunadila
What’s wrong?
Well looks like you wrote content to boot while it was not mounted which could mean you are in a quite messy situation.
Directory /boot to mount over is not empty, mounting anyway.
Suggest first to do “sudo umount /boot” and check what files are on /boot afterwards
does nothing:
unmount: command not found
Typo, corrected already
How can I check what files are on /boot afterwards?
Is my fstab screwed?
ls -lah /boot
Gives:
drwxr-xr-x 23 root root 4.0K Jan 10 13:57 …
-rw------- 1 root root 2.0M Apr 25 20:00 System.map-4.14.34-1-osmc
-rw-r–r-- 1 root root 22K Apr 25 20:35 bcm2708-rpi-0-w.dtb
-rw-r–r-- 1 root root 22K Apr 25 20:35 bcm2708-rpi-b-plus.dtb
-rw-r–r-- 1 root root 22K Apr 25 20:35 bcm2708-rpi-b.dtb
-rw-r–r-- 1 root root 22K Apr 25 20:35 bcm2708-rpi-cm.dtb
-rw-r–r-- 1 root root 23K Apr 25 20:35 bcm2709-rpi-2-b.dtb
-rw-r–r-- 1 root root 24K Apr 25 20:35 bcm2710-rpi-3-b-plus.dtb
-rw-r–r-- 1 root root 24K Apr 25 20:35 bcm2710-rpi-3-b.dtb
-rw-r–r-- 1 root root 23K Apr 25 20:35 bcm2710-rpi-cm3.dtb
-rw-r–r-- 1 root root 17K Apr 25 20:35 bcm2835-rpi-a-plus.dtb
-rw-r–r-- 1 root root 17K Apr 25 20:35 bcm2835-rpi-a.dtb
-rw-r–r-- 1 root root 17K Apr 25 20:35 bcm2835-rpi-b-plus.dtb
-rw-r–r-- 1 root root 17K Apr 25 20:35 bcm2835-rpi-b-rev2.dtb
-rw-r–r-- 1 root root 17K Apr 25 20:35 bcm2835-rpi-b.dtb
-rw-r–r-- 1 root root 17K Apr 25 20:35 bcm2835-rpi-zero-w.dtb
-rw-r–r-- 1 root root 17K Apr 25 20:35 bcm2835-rpi-zero.dtb
-rw-r–r-- 1 root root 18K Apr 25 20:35 bcm2836-rpi-2-b.dtb
-rw-r–r-- 1 root root 17K Apr 25 20:35 bcm2837-rpi-3-b.dtb
-rw-r–r-- 1 root root 134K Apr 25 18:32 config-4.14.34-1-osmc
drwxr-xr-x 3 root root 4.0K Apr 30 12:00 dtb-4.14.34-1-osmc
-rw------- 1 root root 7.9M Apr 30 12:59 kernel.img
drwxr-xr-x 2 root root 12K Apr 30 12:00 overlays
-rw------- 1 root root 7.9M Apr 25 20:00 vmlinuz-4.14.34-1-osmc
Well this is what I feared some of the update has been written when the boot partition hasn’t been mounted.
Will be quite some efforts to fix this.
Next step sudo mount /boot and again run ls -lah /boot and uname -a
ls -lah /boot
Gives:
total 33M
drwxr-xr-x 6 root root 4.0K Jan 1 1970 .
drwxr-xr-x 23 root root 4.0K Jan 10 13:57 …
-rwxr-xr-x 1 root root 1.5K Mar 15 19:24 LICENCE.broadcom
drwxr-xr-x 2 root root 512 Jun 28 2016 System Volume Information
-rwxr-xr-x 1 root root 2.0M Mar 13 02:41 System.map-4.14.26-1-osmc
-rwxr-xr-x 1 root root 2.0M Mar 15 19:46 System.map-4.14.26-2-osmc
-rwxr-xr-x 1 root root 22K Mar 15 20:21 bcm2708-rpi-0-w.dtb
-rwxr-xr-x 1 root root 22K Mar 15 20:21 bcm2708-rpi-b-plus.dtb
-rwxr-xr-x 1 root root 22K Mar 15 20:21 bcm2708-rpi-b.dtb
-rwxr-xr-x 1 root root 22K Mar 15 20:21 bcm2708-rpi-cm.dtb
-rwxr-xr-x 1 root root 23K Mar 15 20:21 bcm2709-rpi-2-b.dtb
-rwxr-xr-x 1 root root 24K Mar 15 20:21 bcm2710-rpi-3-b-plus.dtb
-rwxr-xr-x 1 root root 24K Mar 15 20:21 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root 23K Mar 15 20:21 bcm2710-rpi-cm3.dtb
-rwxr-xr-x 1 root root 17K Mar 15 20:21 bcm2835-rpi-a-plus.dtb
-rwxr-xr-x 1 root root 17K Mar 15 20:21 bcm2835-rpi-a.dtb
-rwxr-xr-x 1 root root 17K Mar 15 20:21 bcm2835-rpi-b-plus.dtb
-rwxr-xr-x 1 root root 17K Mar 15 20:21 bcm2835-rpi-b-rev2.dtb
-rwxr-xr-x 1 root root 17K Mar 15 20:21 bcm2835-rpi-b.dtb
-rwxr-xr-x 1 root root 17K Mar 15 20:21 bcm2835-rpi-zero-w.dtb
-rwxr-xr-x 1 root root 17K Mar 15 20:21 bcm2835-rpi-zero.dtb
-rwxr-xr-x 1 root root 18K Mar 15 20:21 bcm2836-rpi-2-b.dtb
-rwxr-xr-x 1 root root 17K Mar 15 20:21 bcm2837-rpi-3-b.dtb
-rwxr-xr-x 1 root root 51K Mar 15 19:24 bootcode.bin
-rwxr-xr-x 1 root root 77 Jun 27 2016 cmdline.txt
-rwxr-xr-x 1 root root 133K Mar 13 01:12 config-4.14.26-1-osmc
-rwxr-xr-x 1 root root 133K Mar 15 19:10 config-4.14.26-2-osmc
-rwxr-xr-x 1 root root 136 Apr 30 13:04 config.txt
drwxr-xr-x 3 root root 2.5K Mar 15 10:25 dtb-4.14.26-1-osmc
drwxr-xr-x 3 root root 2.5K Mar 22 18:49 dtb-4.14.26-2-osmc
-rwxr-xr-x 1 root root 9.5K Mar 15 19:24 fixup_x.dat
-rwxr-xr-x 1 root root 2.3K Jan 1 1980 install.log
-rwxr-xr-x 1 root root 7.9M Mar 22 18:50 kernel.img
drwxr-xr-x 2 root root 14K Mar 22 18:49 overlays
-rwxr-xr-x 1 root root 95 Jun 27 2016 preseed.cfg
-rwxr-xr-x 1 root root 3.8M Mar 15 19:24 start_x.elf
-rwxr-xr-x 1 root root 719K Feb 5 11:43 uploadlog.txt
-rwxr-xr-x 1 root root 7.9M Mar 13 02:41 vmlinuz-4.14.26-1-osmc
-rwxr-xr-x 1 root root 7.9M Mar 15 19:46 vmlinuz-4.14.26-2-osmc
uname -a
Linux osmc 4.14.26-2-osmc #1 SMP PREEMPT Thu Mar 15 18:20:26 UTC 2018 armv7l GNU/Linux
EDIT:
rebooted, made the upgrade, and now no alert.
Seems to be be working out now.
Kudos!
So this will be open heart surgery
Ok, first advice make a backup because you may end up with a non-bootable system!
sudo umount /bootcd /boottar -cvzf /home/osmc/new_boot.tgz .cd /home/osmc/sudo rm -R /boot/*sudo mount /bootcd /bootsudo tar -cvzf /home/osmc/old_boot.tgzsudo tar -xvzf /home/osmc/new_boot.tgz
After that post ls lah /boot
Oh oh…
Cross posting.
Have a look to the previous post edited…
Well suggest you upload logs again.
I think best still might be to clean up the underlying boot.
Okey.
This is it: mupuduxira
You are still running the old kernel Linux osmc 4.14.26-2-osmc
I really think a backup and reinstall would be the easiest.
How can it be possible?
I have made (since 2 years now) all the upgrades.
How can I have an old kernel?
Because you commented out your boot partition and wrote the upgrade to the wrong partition!