Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 2 of 2 FirstFirst 12
Results 16 to 25 of 25

Thread: Mutant hd51 crashing

  1. #16
    Sicilian's Avatar
    Title
    The Boss
    Join Date
    Mar 2010
    Posts
    29,666
    Thanks
    23,604
    Thanked 26,081 Times in 7,641 Posts
    Quote Originally Posted by cargen View Post
    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
    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





  2. #17

    Title
    Senior Member
    Join Date
    Jul 2013
    Posts
    105
    Thanks
    34
    Thanked 17 Times in 11 Posts
    Quote Originally Posted by Sicilian View Post
    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?

    Code:
    .  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

  3. #18

    Title
    Senior Member
    Join Date
    Jul 2013
    Posts
    105
    Thanks
    34
    Thanked 17 Times in 11 Posts
    Quote Originally Posted by cargen View Post
    This is what I get from mtab file.
    It looks like ext4. Am I right?

    Code:
    .  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


    Code:
    .  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

  4. #19
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,277 Times in 1,089 Posts
    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?

  5. The Following User Says Thank You to ccs For This Useful Post:

    cargen (16-03-18)

  6. #20

    Title
    Senior Member
    Join Date
    Jul 2013
    Posts
    105
    Thanks
    34
    Thanked 17 Times in 11 Posts
    Quote Originally Posted by ccs View Post
    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

  7. #21
    Andy_Hazza's Avatar
    Title
    Moderator
    Join Date
    Oct 2012
    Location
    Derbyshire, UK
    Posts
    7,287
    Thanks
    2,855
    Thanked 2,126 Times in 1,752 Posts
    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)

  8. #22
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,858
    Thanks
    239
    Thanked 1,673 Times in 1,318 Posts
    Quote Originally Posted by cargen View Post
    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.
    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

  9. #23

    Title
    Senior Member
    Join Date
    Jul 2013
    Posts
    105
    Thanks
    34
    Thanked 17 Times in 11 Posts
    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

  10. #24
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,277 Times in 1,089 Posts
    This might be relevant...

    Quote Originally Posted by twol View Post
    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

  11. #25

    Title
    Senior Member
    Join Date
    Jul 2013
    Posts
    105
    Thanks
    34
    Thanked 17 Times in 11 Posts
    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.

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.