D I S C L A I M E R
My right to post information is protected under the rights for freedom act. In all instances, information discussed here on my posts are either hypothetical in nature, out of general curiosity, common knowledge, public knowledge, or role-play. Any use of the collective descriptions and shared knowledge from any of my posts are at the sole discretion of the reader. I am not responsible for what you do with it!
Please help keep OpenViX online, donate HERE.
Rules can be found HERE
Support our sponsor World-Of-Satellite HERE
GIGABLUE UHD QUAD 4K, VU+ DUO 4K SE, ZGEMMA H7S, VU+ UNO 4K SE
Triax 1.1m Powered by TM2600, Fixed 28.2 Zone 2 dish with GT-SAT Unicable
This is what I get from mtab file.
It looks like ext4. Am I right?
Sent from my Moto G (4) using TapatalkCode:. root@mutant51:~# cat /etc/mtab /dev/root / ext4 rw,relatime,data=ordered 0 0 devtmpfs /dev devtmpfs rw,relatime,size=190276k,nr_inodes=47569,mode=755 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 debugfs /sys/kernel/debug debugfs rw,relatime 0 0 tmpfs /media tmpfs rw,relatime,size=64k 0 0 /dev/mmcblk0p1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0 tmpfs /var/volatile tmpfs rw,relatime 0 0 /dev/sda1 /media/hdd ext4 rw,relatime,data=ordered 0 0 devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0 /etc/auto.network /media/autofs autofs rw,relatime,fd=6,pgrp=1950,timeout=5,minproto=5,maxproto=5,indirect 0 0 root@mutant51:~#
Just a quick addition.
If I run dmesg | grep mmcblk0p3
I get the following output.
Does it look right. Not sure about the ext3 message
Sent from my Moto G (4) using TapatalkCode:. root@mutant51:~# dmesg | grep mmcblk0p3 [ 0.000000] Kernel command line: brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p3 rw rootwait hd51_4.boxmode=1 brcm_cma=440M@328M brcm_cma=192M@768M console=ttyS0,115200 [ 1.603156] EXT4-fs (mmcblk0p3): couldn't mount as ext3 due to feature incompatibilities [ 1.618167] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) [ 9.651512] EXT4-fs (mmcblk0p3): re-mounted. Opts: data=ordered root@mutant51:~#
Kodi creates a hidden folder called .Kodi on your HD. Maybe it's trying to use a boot partition for some reason instead?
Can you see a .Kodi folder anywhere?
cargen (16-03-18)
The hidden .kodi folder will always remain on your HDD until it’s either deleted via using an ftp client or if you initialise the HDD.
Sent from my iPhone using Tapatalk
Vu+ Ultimo 4K with 3TB HDD, Dual FBC (Sat) tuners, 1x Twin Hybrid DVB-C/T/T2 tuner
Vu+ Solo 4K with 1TB HDD, Dual FBC (Sat) tuners, 1x Hybrid DVB-C/T/T2 tuner
Vu+ Solo 2 with 1TB HDD 'White Edition', 2x DVB-S2 tuners
Mut@nt HD2400 with 1TB HDD, 4x DVB-S2 tuners
Fixed 28.2E Technomate 65cm Mesh Satellite Dish with Inverto Unicable II/JESS LNB and Inverto Unicable Splitter
Fixed 28.2E Sky Zone 1 45cm Satellite Dish with Octo LNB
(All receivers installed with the latest Dev build)
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
not sure why it is happening.
i have just attached two dmesg log files, before and after Kodi is installed.
if someone else could try to replicated it would be good to see if it is my problem or a general problem.
I have mutant hd51
two tuners DVB2+DVBS2x
lates openvix image available
before
Code:Line 22: [ 0.000000] Kernel command line: brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p3 rw rootwait hd51_4.boxmode=1 brcm_cma=440M@328M brcm_cma=192M@768M console=ttyS0,115200 Line 238: [ 1.603156] EXT4-fs (mmcblk0p3): couldn't mount as ext3 due to feature incompatibilities Line 239: [ 1.618167] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) Line 278: [ 9.651512] EXT4-fs (mmcblk0p3): re-mounted. Opts: data=ordered
after
Code:Line 22: [ 0.000000] Kernel command line: brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p3 rw rootwait hd51_4.boxmode=1 brcm_cma=440M@328M brcm_cma=192M@768M console=ttyS0,115200 Line 231: [ 1.599108] Waiting for root device /dev/mmcblk0p3... Line 239: [ 1.734928] EXT4-fs (mmcblk0p3): couldn't mount as ext3 due to feature incompatibilities Line 240: [ 1.745975] EXT4-fs (mmcblk0p3): warning: mounting fs with errors, running e2fsck is recommended Line 241: [ 1.758497] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) Line 283: [ 9.836872] EXT4-fs (mmcblk0p3): re-mounted. Opts: data=ordered
before.logafter.log
This might be relevant...
Thread...
http://www.world-of-satellite.com/sh...568#post442568
i think you are right.
this morning i checked with Openpli and i get the same error as dmesg output.
Code:Line 22: [ 0.000000] Kernel command line: brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p3 rw rootwait hd51_4.boxmode=1 brcm_cma=440M@328M brcm_cma=192M@768M console=ttyS0,115200 Line 231: [ 1.599108] Waiting for root device /dev/mmcblk0p3... Line 239: [ 1.734928] EXT4-fs (mmcblk0p3): couldn't mount as ext3 due to feature incompatibilities Line 240: [ 1.745975] EXT4-fs (mmcblk0p3): warning: mounting fs with errors, running e2fsck is recommended Line 241: [ 1.758497] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) Line 283: [ 9.836872] EXT4-fs (mmcblk0p3): re-mounted. Opts: data=ordered
i need separate it from the crash problem.
i think this is caused by the additional usb vtuner DVB-T.
the tuner is a RTL2882U (a cheap one)
for some reason it is causing a conflict with the system.
any suggestion on how to troubleshoot this would be great.
thanks all again for the great support.