Software
XBian version:1.0 (knockout) (kernel: Linux 4.14.24+)
XBMC/Kodi version:17.6-Git:2017-11-18-433b93a
Overclock settings:default
Hardware
Device type and model (e.g. Raspberry Pi Model A/B 256/512 MB, CuBox-i i4Pro, ...):RPI 3
Power supply rating:Original power supply adapter
SD card size and make/type:16Gb
Network (Ethernet or wireless):Kodi using Ethernet; wireless adapter active too on different network
Connected devices (TV, USB, network storage, ...):Philips TV, External USB harddisks Seagate and Seagate Backup Plusi
Log files
-
Problem description:
After updating to latest kernel/firmware (18-3-2018) both Seagate drives don't seem to automount anymore.
df -v does not show my harddrives being mounted.
fdisk -l does show the drives but also following warning in red for both drives:
Partition 1 does not start on physical sector boundary.
Manually trying to mount gives following message:
sudo mount -t auto /dev/sda2 /media/Seagate
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.14.24+/modules.dep.bin'
modprobe: FATAL: Module fuse not found in directory /lib/modules/4.14.24+
ntfs-3g-mount: fuse device is missing, try 'modprobe fuse' as root
I don't know exactly what is missing (or maybe corrupted?).
Can anybody help me solving this problem?
(19th Mar, 2018 02:29 AM)Roy Terhaar Wrote: [ -> ]modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.14.24+/modules.dep.bin'
modprobe: FATAL: Module fuse not found in directory /lib/modules/4.14.24+
Something went wrong while kernel updating.
Does this file exist? :lib/modules/4.14.24+/modules.dep.bin
Maybe reinstalling existing kernel package or updating to 4.14.27+ helps
(19th Mar, 2018 03:47 AM)Nachteule Wrote: [ -> ] (19th Mar, 2018 02:29 AM)Roy Terhaar Wrote: [ -> ]modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.14.24+/modules.dep.bin'
modprobe: FATAL: Module fuse not found in directory /lib/modules/4.14.24+
Something went wrong while kernel updating.
Does this file exist? :lib/modules/4.14.24+/modules.dep.bin
Maybe reinstalling existing kernel package or updating to 4.14.27+ helps
4.14.24+ directory does not exist.
However lib/modules/4.14.27+/modules.dep.bin does exist.
But System Info shows 4.14.24+ is installed and so does:
uname -a
Linux xbian 4.14.24+ #1 SMP PREEMPT Thu Mar 8 03:36:23 CET 2018 armv7l GNU/Linux
What is the best way forward, because I don't see upgrade to 4.14.27+ available?
(19th Mar, 2018 04:04 AM)Roy Terhaar Wrote: [ -> ]Linux xbian 4.14.24+ #1 SMP PREEMPT Thu Mar 8 03:36:23 CET 2018 armv7l GNU/Linux
What is the best way forward, because I don't see upgrade to 4.14.27+ available?
Believe me, 4.14.27+ is avaiable
Code:
sudo apt-get upgrade; sudo apt-get update
Hmmm, so the question is: from which repo 4.14.24+ came from ???
Because you do not have
staging repo enabled, 4.14.x kernels are only available in staging repo
Terminal
root@kmxbilr2 ~ # apt-cache policy linux-image-bcm2836
linux-image-bcm2836:
Installiert: 4.9.87+-1521302875
Installationskandidat: 4.14.27+-1521326778
Versionstabelle:
4.14.27+-1521326778 500
500 http://kmcubie staging/rpi2-stretch armhf Packages
4.14.24+-1520477861 500
500 http://kmcubie staging/rpi2-stretch armhf Packages
4.14.22+-1520221171 500
500 http://kmcubie staging/rpi2-stretch armhf Packages
4.14.20+-1519068805 500
500 http://kmcubie staging/rpi2-stretch armhf Packages
4.14.18+-1518193049 500
500 http://kmcubie staging/rpi2-stretch armhf Packages
4.14.16+-1517522005 500
500 http://kmcubie staging/rpi2-stretch armhf Packages
4.14.14+-1516223002 500
500 http://kmcubie staging/rpi2-stretch armhf Packages
4.14.12+-1515430210 500
500 http://kmcubie staging/rpi2-stretch armhf Packages
*** 4.9.87+-1521302875 500
500 http://kmcubie stable/rpi2-stretch armhf Packages
100 /var/lib/dpkg/status
4.9.80+-1518196591 500
500 http://kmcubie stable/rpi2-stretch armhf Packages
4.9.78+-1516987798 500
500 http://kmcubie stable/rpi2-stretch armhf Packages
4.9.76+-1515629023 500
500 http://kmcubie stable/rpi2-stretch armhf Packages
root@kmxbilr2 ~ #
So, you have to enable
staging repo first and then try again
(19th Mar, 2018 04:18 AM)Nachteule Wrote: [ -> ]Hmmm, so the question is: from which repo 4.14.24+ came from ???
Because you do not have staging repo enabled, 4.14.x kernels are only available in staging repo
So, you have to enable staging repo first and then try again
Staging repository is switched on, devel repository is switched off.
That was already the case before the update and that's how it is showing now in xbian-config setting screen...
Hmmm, that's weird
What's your output of sudo apt-cache policy linux-image-bcm2836?
(19th Mar, 2018 04:26 AM)Nachteule Wrote: [ -> ]Hmmm, that's weird
What's your output of sudo apt-cache policy linux-image-bcm2836?
sudo apt-cache policy linux-image-bcm2836
linux-image-bcm2836:
Installed: 4.14.27+-1521326778
Candidate: 4.14.27+-1521326778
Version table:
*** 4.14.27+-1521326778 500
500
http://apt.xbian.org staging/rpi2-stretch armhf Packages
100 /var/lib/dpkg/status
4.14.24+-1520477861 500
500
http://apt.xbian.org staging/rpi2-stretch armhf Packages
4.14.22+-1520221171 500
500
http://apt.xbian.org staging/rpi2-stretch armhf Packages
4.14.20+-1519068805 500
500
http://apt.xbian.org staging/rpi2-stretch armhf Packages
4.14.18+-1518193049 500
500
http://apt.xbian.org staging/rpi2-stretch armhf Packages
4.14.16+-1517522005 500
500
http://apt.xbian.org staging/rpi2-stretch armhf Packages
4.14.14+-1516223002 500
500
http://apt.xbian.org staging/rpi2-stretch armhf Packages
4.14.12+-1515430210 500
500
http://apt.xbian.org staging/rpi2-stretch armhf Packages
4.9.87+-1521302875 500
500
http://apt.xbian.org stable/rpi2-stretch armhf Packages
4.9.80+-1518196591 500
500
http://apt.xbian.org stable/rpi2-stretch armhf Packages
4.9.78+-1516987798 500
500
http://apt.xbian.org stable/rpi2-stretch armhf Packages
4.9.76+-1515629023 500
500
http://apt.xbian.org stable/rpi2-stretch armhf Packages
Ah, now I'm understanding. You have 4.14.27+ already installed but still running 4.14.24+
Hmmm, so please try to reinstall 4.14.27+ by running
sudo apt-get install linux-image-bcm2836=4.14.27+-1521326778
(19th Mar, 2018 04:41 AM)Nachteule Wrote: [ -> ]Ah, now I'm understanding. You have 4.14.27+ already installed but still running 4.14.24+
Hmmm, so please try to reinstall 4.14.27+ by running
sudo apt-get install linux-image-bcm2836=4.14.27+-1521326778
It does not seem to do anything...
xbian@xbian ~ $ sudo apt-get install linux-image-bcm2836=4.14.27+-1521326778
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-image-bcm2836 is already the newest version (4.14.27+-1521326778).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Oops, sorry. You have to add --reinstall as parameter
sudo apt-get install --reinstall linux-image-bcm2836=4.14.27+-1521326778
(19th Mar, 2018 04:45 AM)Nachteule Wrote: [ -> ]Oops, sorry. You have to add --reinstall as parameter
sudo apt-get install --reinstall linux-image-bcm2836=4.14.27+-1521326778
I have tried this, but the script got stuck at this point:
Preparing to unpack .../linux-image-bcm2836_4.14.27+-1521326778_armhf.deb ...
Unpacking linux-image-bcm2836 (4.14.27+-1521326778) over (4.14.27+-1521326778) ...
Setting up linux-image-bcm2836 (4.14.27+-1521326778) ...
Processing triggers for xbian-package-initramfs-tools (20180317-0) ...
Progress: [ 83%] [###################################################...........]
So I think I will have to revert back to an old snapshot version and try to upgrade from there.
I will do this later as I don't have the time right now...
(19th Mar, 2018 04:21 PM)Roy Terhaar Wrote: [ -> ] (19th Mar, 2018 04:45 AM)Nachteule Wrote: [ -> ]Oops, sorry. You have to add --reinstall as parameter
sudo apt-get install --reinstall linux-image-bcm2836=4.14.27+-1521326778
I have tried this, but the script got stuck at this point:
Preparing to unpack .../linux-image-bcm2836_4.14.27+-1521326778_armhf.deb ...
Unpacking linux-image-bcm2836 (4.14.27+-1521326778) over (4.14.27+-1521326778) ...
Setting up linux-image-bcm2836 (4.14.27+-1521326778) ...
Processing triggers for xbian-package-initramfs-tools (20180317-0) ...
Progress: [ 83%] [###################################################...........]
So I think I will have to revert back to an old snapshot version and try to upgrade from there.
I will do this later as I don't have the time right now...
Please check your boot partition first. Seems that files can't be written to the boot partition (r/o monted?). And reverting to an older snapshot does not solve this.
(20th Mar, 2018 12:31 AM)Nachteule Wrote: [ -> ]Please check your boot partition first. Seems that files can't be written to the boot partition (r/o monted?). And reverting to an older snapshot does not solve this.
Looks like a rw mount to me:
root@xbian:/home/xbian# mount | grep boot
/dev/mmcblk0p1 on /boot type vfat (rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)