Mutant hd51 crashing

[Sicilian]

I think so.
I can give it another formatting to see if changes anything and let you know

Sent from my Moto G (4) using Tapatalk

Check it’s formatted for ext4.


Sent from my iPhone using Tapatalk

[cargen]

Check it’s formatted for ext4.


Sent from my iPhone using Tapatalk

This is what I get from mtab file.
It looks like ext4. Am I right?

.  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:~#

Sent from my Moto G (4) using Tapatalk

[cargen]

This is what I get from mtab file.
It looks like ext4. Am I right?

.  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:~#

Sent from my Moto G (4) using Tapatalk

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

.  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:~#

Sent from my Moto G (4) using Tapatalk

[ccs]

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]

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?

Thanks.
I will have a look this evening. Not near the box at the moment and I haven't installed Kodi since the error.

Sent from my Moto G (4) using Tapatalk

[Andy_Hazza]

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

[birdman]

after the installation of Kodi, bang!! the error is there.

That make no sense.
The only thing that should ever create file-system errors is a system crash in the middle of writing to the disk.

[cargen]

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

	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

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

[ccs]

This might be relevant...

After a huge update over the last 2 weekend, Kodi 17.0 is now capable of running on the HD51................ depending on the Image.

The EMMC has been reworked to contain room for 4 images plus a Kodi swap file.

From comments, it runs apparently faster than the Vu+ Ultimo 4K Kodi implementation........ so something to look forward to....................

I have just run an image build, so will let you know what I think later!!!

For those daring people that run the HD51 multiboot (not the multiboot plugin frig) you will have to clean flash the receiver, due to the reflash of the EMMC.

There will also be changes necessary to ViX to support this change.

As other receivers update their drivers it is likely (eg Octagon) will also support this change

Thread...

http://www.world-of-satellite.com/sh...568#post442568

[cargen]

i think you are right.

this morning i checked with Openpli and i get the same error as dmesg output.

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.