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.
Results 1 to 7 of 7

Thread: Zgemma7s Timer setup crash

  1. #1

    Title
    Junior Member
    Join Date
    Jan 2023
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Zgemma7s Timer setup crash

    Hi. My first post. Today when I tried to set up a timer to record a programme my box crashed with the following error:We are really sorry. Your receiver encountered a software problem, and needs to be restarted. lease send the logfile /home/root/logs/Enigma2_crash_2023-01-01_11-31-31.log to the OpenV Your STB restarts in 10 seconds! Component: Enigma2
    <942.1865 11:31:31.5383 (eDVBServiceRecord) ADD PID: 0000
    <942.1865> 11:31:31.5383 (eDVBServiceRecord ADD PID: 0916
    <942.1065 11:31:31.5383 (eDVBServiceRecord ADD PID: 0918
    <942.1865 11:31:31.5383 (eDVBServiceRecord ADD PID: 091a
    <942.1875 11:31:31.5393 (setloPriol realtime level 7 ok <942.1876 11:31:31.5393 (eFilePushThreadRecorder] THREAD START
    <942.1880> 11:31:31.5398 (RecordTimer) start recording on tuner: A <942.1927> 11:31:31.5445 Traceback (most recent call last):
    <942.1928> 11:31:31.5446 File "/usr/lib/enigma2/python/StartEnigma.py", line 259, in processDelay <942.1931> 11:31:31.5449 callback(retval)
    942.1931> 11:31:31.5449 File "/usr/lib/enigma2/python/Screens/InfoBarGenerice.py", line 3294, in recordQuestionCallback
    942.1932 11:31:31.5450 File "/usr/lib/enigma2/python/Screens/InfoBarGenerics.py", line 3213, in startinstantRecording 942.1933> 11:31:31.5451 File "/usr/lib/enigma2/python/RecordTimer.py", line 1261, in record
    942. 1934 11:31:31.5452 File "/usr/lib/enigma2/python/timer.py", line 218, in addTimerEntry 942. 1935 11:31:31.5453 File "/usr/lib/enigma2/python/timer.py", line 257, in calo NextActivation
    942. 1936 11:31:31.5454 File "/usr/lib/enigma2/python/timer.py", line 358, in processActivation
    942.1937> 11:31:31.5455 File "/usr/lib/enigma2/python/RecordTimer.py", line 1168, in save Timer <942.1938 11:31:31.5456 10Error: [Errno 28 No space left on device
    <942.1939 11:31:31.5457 (ePyObject) (CallObject(<bound method Session.processDelay of <_main_.Session instance at Oxb20bdf58>>())
    failed)

    I would be very grateful for any assistance in resolving this issue.

  2. #2
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    8,618
    Thanks
    1,009
    Thanked 2,964 Times in 2,305 Posts
    Not sure if you have a HDD attached or just using flash, but there is no space on the device
    Gigablue Quad 4K & UE 4K
    .........FBC Tuners:
    ------------------> GT-Sat unicable LNB to 1.5M dish(28.2E)
    ------------------> Gigablue unicable LNB to 80 cm dish(19.2E)
    .......................
    Vu+ Uno4KSE, Dreambox dm900
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
    Zgemma H9 C/S into Giga4K

  3. #3

    Title
    Junior Member
    Join Date
    Jan 2023
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Hi. I do have a 500 Gb HDD attached with 414 Gb free space. I can access the HDD and watch recordings with no issues.

  4. #4
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    8,618
    Thanks
    1,009
    Thanked 2,964 Times in 2,305 Posts
    Quote Originally Posted by KCON View Post
    Hi. I do have a 500 Gb HDD attached with 414 Gb free space. I can access the HDD and watch recordings with no issues.
    11:31:31.5455 File "/usr/lib/enigma2/python/RecordTimer.py", line 1168, in save Timer <942.1938 11:31:31.5456 10Error: [Errno 28 No space left on device

    So check your settings
    Gigablue Quad 4K & UE 4K
    .........FBC Tuners:
    ------------------> GT-Sat unicable LNB to 1.5M dish(28.2E)
    ------------------> Gigablue unicable LNB to 80 cm dish(19.2E)
    .......................
    Vu+ Uno4KSE, Dreambox dm900
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
    Zgemma H9 C/S into Giga4K

  5. #5

    Title
    Junior Member
    Join Date
    Jan 2023
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Went into Menu, Timers and deleted a long list of completed timers. Not sure why but this has sorted my problem. Thanks for your advice.

  6. #6

    Title
    Junior Member
    Join Date
    Jan 2023
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Hi. My issue is back again with the same boot screen only this times it's in a loop ie. keeps rebooting until "49" is displayed then starts a new reboot. Been like this now for the last 2 hours. Any way I can get out of this loop?

  7. #7
    Huevos's Avatar
    Title
    Administrator
    Join Date
    Jun 2010
    Location
    38.5N, 0.5W
    Posts
    13,945
    Thanks
    2,062
    Thanked 5,145 Times in 3,395 Posts
    You need to login to the box by command line and then type:

    Code:
    init 4
    enigma2
    That will show you the error. Then just copy it and post in here.
    Help keep OpenViX servers online.Please donate!

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.