View Entry Info: Crash at end of recording, when end margin starts

Category:
Possible Bug
What ViX Image build number are you using?
Please provide your ViX Team image build number. Menu > Information > About > Build number > ENTER THIS NUMBER e.g. 4.2.028
OpenViX 5.3.015
Have you tried a flash WITHOUT settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
No
Have you tried a flash WITH settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
Yes
Attachments
Page 1 of 4 123 ... LastLast
Results 1 to 15 of 53
  1. #1
    Senior Member

    Join Date
    Nov 2017
    Posts
    146
    Thanks
    20
    Thanked 14 Times in 13 Posts

    Crash at end of recording, when end margin starts

    I've noticed a few times so far following an update to 5.3.015 the following malfunction.

    I start watching a recorded programme while the recording is still taking place. When the recorded programme reaches its end time and the tail end margin timer starts, the Mut@nt crashes. The GUI restarts and continues recording (I have set the end margin to 5 minutes). After that event I end up with two recordings present, the main programme and the a separate tail end 5 minute recording. When it restarts following the crash it reverts to any settings I had when I first switched on the Mut@nt, rather than the settings at the time it crashed (e.g. selected channel, volume level).

    I've enabled the logs and will keep an eye on this tomorrow, but I am wondering if anyone else has observed the same thing? This did not happen with any version prior to 5.3.015.
    Kind regards,

    Mick

  2. #2
    The Boss Sicilian's Avatar

    Join Date
    Mar 2010
    Posts
    28,967
    Thanks
    22,903
    Thanked 25,475 Times in 7,395 Posts
    Not experienced this issue on any of my receivers.
    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!

    Follow us on Twitter 0penViX
    Rules can be found
    HERE
    Support our sponsor World-Of-Satellite
    HERE
    GIGABLUE UHD QUAD 4K, GIGABLUE UHD UE 4K, MUTANT HD51, VU+ ULTIMO 4K
    Triax 1.1m Powered by TM2600, Technomate 80cm Powered by TM-2600 and Fixed 28.2 Zone 2 dish





  3. #3
    Senior Member

    Join Date
    Nov 2017
    Posts
    146
    Thanks
    20
    Thanked 14 Times in 13 Posts
    OK, it happened again this morn. I couldn't find anything immediately obvious in the logs, but will post them if you think they could be useful. Nevertheless, I had a quick look in dmesg and it seems the ext4 fs on the root partition was corrupted at some point:
    Code:
    [Warning!  /dev/mmcblk0p3 is mounted.
    Warning: skipping journal recovery because doing a read-only filesystem check.
    /dev/mmcblk0p3 contains a file system with errors, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    Block bitmap differences:  +(393217--397344) +(401409--401667) +(524289--524303) +(524305--524319) +(524321--528160) +(655361--655371) +(655377--655387) +(655393--658208) +(663553--663811) +786433 +(786436--786
    437) +(786440--786696) +(787209--787464)
    Fix? no
    Free blocks count wrong for group #48 (4064, counted=8192).
    Fix? no
    Free blocks count wrong for group #49 (7933, counted=8192).
    Fix? no
    Free blocks count wrong for group #64 (4064, counted=7934).
    Fix? no
    Free blocks count wrong for group #80 (4064, counted=6902).
    Fix? no
    Free blocks count wrong for group #81 (7933, counted=8192).
    Fix? no
    Free blocks count wrong for group #96 (7160, counted=7676).
    Fix? no
    Free blocks count wrong (480867, counted=500920).
    Fix? no
    Free inodes count wrong (191182, counted=191180).
    Fix? no
    Padding at end of block bitmap is not set. Fix? no
    
    /dev/mmcblk0p3: ********** WARNING: Filesystem still has errors **********
    /dev/mmcblk0p3: 13618/204800 files (0.7% non-contiguous), 338333/819200 blocks
    What is the recommended way of repairing this fs?
    Kind regards,

    Mick

  4. #4
    ViX Beta Tester twol's Avatar

    Join Date
    Apr 2012
    Posts
    5,549
    Thanks
    739
    Thanked 1,895 Times in 1,453 Posts
    Quote Originally Posted by Mickkie View Post
    OK, it happened again this morn. I couldn't find anything immediately obvious in the logs, but will post them if you think they could be useful. Nevertheless, I had a quick look in dmesg and it seems the ext4 fs on the root partition was corrupted at some point:
    Code:
    [Warning!  /dev/mmcblk0p3 is mounted.
    Warning: skipping journal recovery because doing a read-only filesystem check.
    /dev/mmcblk0p3 contains a file system with errors, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    Block bitmap differences:  +(393217--397344) +(401409--401667) +(524289--524303) +(524305--524319) +(524321--528160) +(655361--655371) +(655377--655387) +(655393--658208) +(663553--663811) +786433 +(786436--786
    437) +(786440--786696) +(787209--787464)
    Fix? no
    Free blocks count wrong for group #48 (4064, counted=8192).
    Fix? no
    Free blocks count wrong for group #49 (7933, counted=8192).
    Fix? no
    Free blocks count wrong for group #64 (4064, counted=7934).
    Fix? no
    Free blocks count wrong for group #80 (4064, counted=6902).
    Fix? no
    Free blocks count wrong for group #81 (7933, counted=8192).
    Fix? no
    Free blocks count wrong for group #96 (7160, counted=7676).
    Fix? no
    Free blocks count wrong (480867, counted=500920).
    Fix? no
    Free inodes count wrong (191182, counted=191180).
    Fix? no
    Padding at end of block bitmap is not set. Fix? no
    
    /dev/mmcblk0p3: ********** WARNING: Filesystem still has errors **********
    /dev/mmcblk0p3: 13618/204800 files (0.7% non-contiguous), 338333/819200 blocks
    What is the recommended way of repairing this fs?
    I seem to remember this is a standard error because of the way that the 1st Emmc partition is built (and truncated) - so not your issue and nothing you can do about it.
    You need to supply crash logs
    Gigablue Quad 4K & UE 4K
    .........FBC Tuners:
    ------------------> DUR-Line DCR 5-1-8-L4 Multiswitch to 1.5M dish(28.2E)
    ------------------> Spaun SUS 5581/33 NFA Multiswitch to 80 cm dish(19.2E)
    .......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
    Edision Osmio 4K+, Zgemma H9Combo+Twin, Octagon SF8008, Multibox using Legacy ports on multiswitches
    Zgemma H9 C/S into Giga4K

  5. #5
    Senior Member

    Join Date
    Nov 2017
    Posts
    146
    Thanks
    20
    Thanked 14 Times in 13 Posts
    I've mounted the / partition ro and run a fsck.ext4 on it, fixing whatever errors it came up with. I rebooted, reflashed the latest openvix image and we'll see what this gives.

    I attach the logs of the crash from this morning. Timestamp 57430.552 shows where I suppose the box woke up to start recording '20200207 0827 - BBC NEWS HD - Worklife'.
    Then at 57433.153 the recording starts. The crash happened towards the end of this 30 minutes recording, as I was playing back a previous recording of Newsnight. Not sure when the crash happened exactly.

    Log pasted here: REMOVED LINK
    Last edited by Sicilian; 07-02-20 at 13:07. Reason: REMOVED LIVE LINK.
    Kind regards,

    Mick

  6. #6
    Forum Supporter
    Donated Member


    Join Date
    Sep 2014
    Posts
    2,713
    Thanks
    237
    Thanked 624 Times in 539 Posts
    That link has a trojan according to my virus guard - you should post them as attachments via advanced options.

  7. #7
    The Boss Sicilian's Avatar

    Join Date
    Mar 2010
    Posts
    28,967
    Thanks
    22,903
    Thanked 25,475 Times in 7,395 Posts
    I've removed the link, as above post the crash log.
    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!

    Follow us on Twitter 0penViX
    Rules can be found
    HERE
    Support our sponsor World-Of-Satellite
    HERE
    GIGABLUE UHD QUAD 4K, GIGABLUE UHD UE 4K, MUTANT HD51, VU+ ULTIMO 4K
    Triax 1.1m Powered by TM2600, Technomate 80cm Powered by TM-2600 and Fixed 28.2 Zone 2 dish





  8. #8
    Senior Member

    Join Date
    Nov 2017
    Posts
    146
    Thanks
    20
    Thanked 14 Times in 13 Posts
    Apologies, I don't know why it says there's a trojan, it's just a pastebin service and the log is plain text. Regardless, please see attached log (I hope it's not too long).
    Attached Files Attached Files
    Kind regards,

    Mick

  9. The Following User Says Thank You to Mickkie For This Useful Post:

    abu baniaz (07-02-20)

  10. #9
    Forum Supporter
    Donated Member


    Join Date
    Sep 2014
    Posts
    2,713
    Thanks
    237
    Thanked 624 Times in 539 Posts
    .... that's a debug log, there doesn't appear to be a crash, just the power button being pressed.

  11. #10
    Senior Member

    Join Date
    Nov 2017
    Posts
    146
    Thanks
    20
    Thanked 14 Times in 13 Posts
    Oops! Sorry ... here is the crash log.Enigma2_crash_2020-02-07_09-52-20.log
    Kind regards,

    Mick

  12. #11
    Forum Supporter
    Donated Member


    Join Date
    Sep 2014
    Posts
    2,713
    Thanks
    237
    Thanked 624 Times in 539 Posts
    Looks like the root partition (from your earlier post #3) is still (partially?) read-only
    Code:
    < 62538.824>   File "/usr/lib/enigma2/python/RecordTimer.py", line 1125, in saveTimer
    < 62538.824> IOError: [Errno 30] Read-only file system: '/etc/enigma2/timers.xml.writing'

  13. #12
    ViX Beta Tester twol's Avatar

    Join Date
    Apr 2012
    Posts
    5,549
    Thanks
    739
    Thanked 1,895 Times in 1,453 Posts
    You have a multiboot system, so assume you have backed up your settings use ImageManager to flash latest image into another slot and try again!!
    Gigablue Quad 4K & UE 4K
    .........FBC Tuners:
    ------------------> DUR-Line DCR 5-1-8-L4 Multiswitch to 1.5M dish(28.2E)
    ------------------> Spaun SUS 5581/33 NFA Multiswitch to 80 cm dish(19.2E)
    .......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
    Edision Osmio 4K+, Zgemma H9Combo+Twin, Octagon SF8008, Multibox using Legacy ports on multiswitches
    Zgemma H9 C/S into Giga4K

  14. #13
    Senior Member

    Join Date
    Nov 2017
    Posts
    146
    Thanks
    20
    Thanked 14 Times in 13 Posts
    Hmm ... the plot thickens.

    At the time I had not yet run fsck on the / fs. For whatever reason the crash took place, inc. the state of the fs, it seems it was remounted as ro when it errored out.

    This is what it looks like presently:
    Code:
    root@mutant51:~# mount
    /dev/mmcblk0p3 on / type ext4 (rw,relatime,data=ordered)
    proc on /proc type proc (rw,relatime)
    sysfs on /sys type sysfs (rw,relatime)
    debugfs on /sys/kernel/debug type debugfs (rw,relatime)
    devtmpfs on /dev type devtmpfs (rw,relatime,size=190260k,nr_inodes=47565,mode=755)
    tmpfs on /media type tmpfs (rw,relatime,size=64k)
    /dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
    tmpfs on /var/volatile type tmpfs (rw,relatime)
    /dev/sda1 on /media/hdd type ext4 (rw,relatime,data=ordered)
    /dev/sdb1 on /media/usb type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
    devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
    /etc/auto.network on /media/autofs type autofs (rw,relatime,fd=6,pgrp=2100,timeout=5,minproto=5,maxproto=5,indirect)
    However, the file it is looking for above is no where to be found?
    Code:
    root@mutant51:~# ls -la /etc/enigma2/timers.xml.writing
    ls: /etc/enigma2/timers.xml.writing: No such file or directory
    root@mutant51:~# ls -la /etc/enigma2/timers.xml 
    -rw-r--r--    1 root     root         32952 Feb  7 14:05 /etc/enigma2/timers.xml
    Kind regards,

    Mick

  15. #14
    ViX Beta Tester twol's Avatar

    Join Date
    Apr 2012
    Posts
    5,549
    Thanks
    739
    Thanked 1,895 Times in 1,453 Posts
    I would give up looking and just either reflash the slot or preferably flash another slot vis IMageManager
    Gigablue Quad 4K & UE 4K
    .........FBC Tuners:
    ------------------> DUR-Line DCR 5-1-8-L4 Multiswitch to 1.5M dish(28.2E)
    ------------------> Spaun SUS 5581/33 NFA Multiswitch to 80 cm dish(19.2E)
    .......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
    Edision Osmio 4K+, Zgemma H9Combo+Twin, Octagon SF8008, Multibox using Legacy ports on multiswitches
    Zgemma H9 C/S into Giga4K

  16. The Following User Says Thank You to twol For This Useful Post:

    Mickkie (08-02-20)

  17. #15
    Senior Member

    Join Date
    Nov 2017
    Posts
    146
    Thanks
    20
    Thanked 14 Times in 13 Posts
    Thanks guys,

    Since I've fsck'ed the partition and reflashed the image, the Mut@nt seems to be OK again. I hope the problem was an one off rather than a eMMC hardware failure. I guess time will tell.
    Kind regards,

    Mick

Page 1 of 4 123 ... LastLast

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.