[VU+ Uno4KSE] Crashing VU+Duo4KSE

[twol]

Thanks. I'm also extremely curious to understand what is wrong! How on earth does my last image backup reach almost 3GB?? Maybe not compressed?

Both timeshift recordings are in HDD/Movie. The large one is a .ts file but the small one is a .ts.sc file which may imply that the final closing of the 4 min file was at the time of the crash? The HDD/timeshift folder still has 11 GB of buffer files! Sounds anomalous. Probably I should delete the lot? Or disable and re-enable Timeshift?

Curiously the /etc/enigma2 folder holds less than 500 KB! I had concluded that that was the flash area, but the size is too small... So where is the damn flash image?

Other point... When back in the day I set up the NAS box I called it HDD. When crashing started and I removed the NAS I think I initially named the HD using one of the other available names - SDA SBC USB or whatever. Then, thinking that it was safer to revert to standard names once I removed the NAS so I renamed/mounted the HD as HDD. Not being a Linuxoid (at least since UNIX in 1977), I was a little out of my depth assigning devices. But I used to write device drivers in asm back in the day so I felt confident enough to guess... So maybe there is some residual path data table which is screwing things up. I realise this is a bit of flogging the proverbial dead horse, and I appreciate your help hugely, it's just that I'd really like to find the problem because it's there! Feel free to tell me to rebuild (again!).

Am I right to assume that the files in HDD/backup are settings only or do they contain incremental backup bits as well? It's just that if I load a backup it asks if I want to restore settings, when the answer is obviously yes if that is the sole purpose of the file If the message was confirm load or similar, it would be clearer...

Thanks

Image backup…maybe nice to have, but in reality providing you take a settings backup (which is the automatic default setting for ImageManager flash) - an online flash with settings restore will recover an image - I do it all the time,
Personally, I never do a software update to the next version update, I always flash and restore settings & plugins.

 

[JerryK132]

For clarity, I said you should not have two sources of EPG. I did not say anything about not having Freesat and Sky bouquets. Bouquets and EPG are different things! However, this is not relevant to your timeshift crash.

The code was previously so that you could have one device for timeshift and another for recordings. As an example a USB stick for timeshift and a mechanical HDD for recordings. This could still be possible.

Apologies if I was unclear, and yes I do get that. I was agreeing that to create bouquets containing all services from each of those two groups, in addition to those in Last scanned was unnecessarily repetitive and unnecessarily large and ultimately pointless, and that I should be creating what would be a set of favourites or favourites subsets in the form of bouquets, which in turn would enable me to reference the related EPG data in epg.dat. I understood that there was also a risk that having those three large bouquets might be using excessive space, posssibly leading to the crashes we are investigating.

I previously assumed that the Sky and Freesat services were all distinct. Now I realise that they are neither distinct nor identical, but that all services available to me are by definition already present in Last Scanned and therefore that the latter should be my goto library for channels I might wish to include in bouquets.

Re your timeshift point, it strikes me as elegant design to have the choice of placing completed recordings, timeshift buffers, and indeed epg.dat in distinct and settable locations of the user's choice. I had not realised that I could place the timeshift folder on an entirely separate device, rather than just a separate folder. Thank you very much - that way I might keep the ever-changing timeshift data on a (fast?) solid state usb device, while allowing the HDD to remain cool on standby unless access to recordings was specifically required, as per your example.

But you say "The code was previously..."? Looking at the timeshift menu, it seems I can still specify a different device not just a different folder for timeshift, so I will try that once the crashing problem has been resolved. Does the "Stop timeshift during recording" stop timeshift during a scheduled recording of the same service (perhaps relatively unneccessary), or during a scheduled background recording of a different service/channel?

 

[abu baniaz]

You are missing the point. EPG is correlated by service reference. A channel can be in a billion bouquets if you want. It has no bearing on the EPG.

You have not said how you are scanning. I am presuming that you are using ABM. It only takes a about a minute. I sometimes scan freesat, Sky UK and Sky ROI. I enable the not indexed options for the sky providers, so all services are added to my lamedb file. Most of the channels are identical barring the names on the SI tables.

Anyway, we better leave your confusing/mixing up of EPG/bouquets alone or start a different thread for it so that we can focus on the timeshift crash.

 

[JerryK132]

You are missing the point. EPG is correlated by service reference. A channel can be in a billion bouquets if you want. It has no bearing on the EPG.

You have not said how you are scanning. I am presuming that you are using ABM. It only takes a about a minute. I sometimes scan freesat, Sky UK and Sky ROI. I enable the not indexed options for the sky providers, so all services are added to my lamedb file. Most of the channels are identical barring the names on the SI tables.

Anyway, we better leave your confusing/mixing up of EPG/bouquets alone or start a different thread for it so that we can focus on the timeshift crash.

No, I get it. They are separate! It's just that I was under the impression from my early exchanges with @twol that importing unnecessary thousands of services might be overloading the system and causing a resource/memory leak of some kind. I now totally get that epg.dat and the various lists of services are separate and indexed on references. I'm entirely happy with that!

But I've made some progress.

First I tried to set up another Boot slot and it refused, claiming no space error. Which makes sense given I only had a few MB free in Flash memory.

So I made another image backup in case and then reloaded the release 6.7.10. I accepted the Wizard and tried to restore settings. I received an error saying something like no network try later. Presumably because I use WiFi and not having settings it could not yet access it? Anyway it booted ok and I restored the settings backup again just in case. Memory was then fine again. I then upgraded to 6.7.11 and restored settings/plugins. Memory is still all fine: 1.24GB Free RAM, 0.8GB Flash in use. Great! Haven't changed my bouquets yet - we're all agreed that is irrelevant here!

I've been experimenting and looking at the crash logs.
First, if I try a timeshift record and then change a channel and I tell it to save timeshift now in response to the timeshift warning, all is well. File saved, no errors (and no crash file). However if i set a timeshift record and leave to completion, I get the usual two new recordings in the PVR list, BUT a crash log is generated. I didn't actually see a restart, but it reverts to the default channel so it probably crashed and restarted fast.

Anyway, I've tried various combinations including switch off all KODI devices, restart VU+ but same behaviour.

Looking more closely at the logs, three things strike me.

Firstly all except one show disk errors. Here's a selection:
<4>[ 282.772362] [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
<4>[ 282.778484] [VID]: VIDEO_GET_SIZE aspect: 1 0
<4>[ 282.998486] [AUD]: HDMI Max Audio PCM Channels=8
<5>[ 305.240262] EXT4-fs (sda1): error count since last fsck: 386762
<5>[ 305.246201] EXT4-fs (sda1): initial error at time 1706567696: ext4_mb_generate_buddy:754
<5>[ 305.254312] EXT4-fs (sda1): last error at time 1749060973: ext4_mb_generate_buddy:754
<2>[ 885.341637] EXT4-fs error (device sda1): ext4_mb_generate_buddy:754: group 18386, block bitmap and bg descriptor inconsistent: 0 vs 32768 free clusters
<2>[ 885.355724] EXT4-fs error (device sda1): ext4_mb_generate_buddy:754: group 18387, block bitmap and bg descriptor inconsistent: 0 vs 32768 free clusters

/../

<2>[ 45.301343] EXT4-fs error (device sda1): ext4_mb_generate_buddy:754: group 14, block bitmap and bg descriptor inconsistent: 0 vs 32768 free clusters
<4>[ 46.217826] JBD2: Spotted dirty metadata buffer (dev = sda1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
<4>[ 46.231987] JBD2: Spotted dirty metadata buffer (dev = sda1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
<4>[ 51.808514] EXT4-fs error: 156 callbacks suppressed
<2>[ 51.813427] EXT4-fs error (device sda1): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 0 vs 27026 free clusters
<4>[ 52.614086] JBD2: Spotted dirty metadata buffer (dev = sda1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
<4>[ 52.627669] JBD2: Spotted dirty metadata buffer (dev = sda1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.

/../

Al;so (?):
<3>[ 3.362160] EXT3-fs (mmcblk0p9): error: couldn't mount because of unsupported optional features (2c0)
<6>[ 3.384008] EXT4-fs (mmcblk0p9): recovery complete
<6>[ 3.389046] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 4.246209] usb 5-1.2: new full-speed USB device number 3 using ehci-brcm
<6>[ 4.415194] usb 5-1.1: new high-speed USB device number 4 using ehci-brcm
<4>[ 4.552670] EXT4-fs (sda1): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 4.652198] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 4.733840] SGI XFS with security attributes, realtime, no debug enabled
<6>[ 4.967778] EXT4-fs (mmcblk0p9): re-mounted. Opts: data=ordered
<30>[ 5.249077] udevd[1075]: starting version 3.2.14
<5>[ 5.254622] random: udevd urandom read with 82 bits of entropy available
<30>[ 5.280622] udevd[1076]: starting eudev-3.2.14
<5>[ 5.530918] random: nonblocking pool is initialized
<6>[ 10.688244] usbcore: registered new interface driver dbus_usbdev
<4>[ 10.733286] bcm_event: module license 'Proprietary' taints kernel.
<4>[ 10.739491] Disabling lock debugging due to kernel taint
<6>[ 10.948997] nexus.ko: virtual irq: enabled (267)
<6>[ 10.953676] nexus.ko: shared gpio banks: enabled
<6>[ 11.734464] usb 5-1.1: USB disconnect, device number 4
<
What can/should I do with this? I have DiskMagic which readsEXT4 volumes via a PC. Odd that one crash file has no such errors. Must be recovering perhaps?

Secondly, There are lots of KODI entries as pointed out by @twol. Are these there for historical reasons or are they supporting my various Android/KODI/Firesticks? There is a .kodi folder in media/hdd/ and it has various subfolders including addons. Like I said, I don't use KODI but I just noticed that KODIO was installed on my main (Android) TV. I've just uninstalled it and restarted the TV. The .kodi folder and contents are still there....

Thirdly, and this looks more interesting,
19:35:15.0736 Traceback (most recent call last):
19:35:15.0736 File "/usr/lib/enigma2/python/Components/Timeshift.py", line 948, in ptsMergeRecords
19:35:15.0742 FileNotFoundError: [Errno 2] No such file or directory: "/media/hdd/movie/20240129 1854 - CNEWS - Face à l'info.ts.meta"
19:35:15.0743 [ePyObject] (CallObject(<bound method InfoBarTimeshift.ptsMergeRecords of <class 'Screens.InfoBar.InfoBar'>>,()) failed)

Where does the bold filename come from?? It was deleted many months ago from movies, so where is it picked up from? Had a look at timeshift.pyc, but couldn't determine much... My guess is that this is the culprit and that some ancient default filename parameter is being supplied perhaps via the KODI stuff... Can't think why though. Over to you...

 

[twol]

No, I get it. They are separate! It's just that I was under the impression from my early exchanges with @twol that importing unnecessary thousands of services might be overloading the system and causing a resource/memory leak of some kind. I now totally get that epg.dat and the various lists of services are separate and indexed on references. I'm entirely happy with that!

But I've made some progress.

First I tried to set up another Boot slot and it refused, claiming no space error. Which makes sense given I only had a few MB free in Flash memory.

So I made another image backup in case and then reloaded the release 6.7.10. I accepted the Wizard and tried to restore settings. I received an error saying something like no network try later. Presumably because I use WiFi and not having settings it could not yet access it? Anyway it booted ok and I restored the settings backup again just in case. Memory was then fine again. I then upgraded to 6.7.11 and restored settings/plugins. Memory is still all fine: 1.24GB Free RAM, 0.8GB Flash in use. Great! Haven't changed my bouquets yet - we're all agreed that is irrelevant here!

I've been experimenting and looking at the crash logs.
First, if I try a timeshift record and then change a channel and I tell it to save timeshift now in response to the timeshift warning, all is well. File saved, no errors (and no crash file). However if i set a timeshift record and leave to completion, I get the usual two new recordings in the PVR list, BUT a crash log is generated. I didn't actually see a restart, but it reverts to the default channel so it probably crashed and restarted fast.

Anyway, I've tried various combinations including switch off all KODI devices, restart VU+ but same behaviour.

Looking more closely at the logs, three things strike me.

Firstly all except one show disk errors. Here's a selection:
<4>[ 282.772362] [VID]: VIDEO_GET_SIZE src w: 0 h:0 display w:0 h:0
<4>[ 282.778484] [VID]: VIDEO_GET_SIZE aspect: 1 0
<4>[ 282.998486] [AUD]: HDMI Max Audio PCM Channels=8
<5>[ 305.240262] EXT4-fs (sda1): error count since last fsck: 386762
<5>[ 305.246201] EXT4-fs (sda1): initial error at time 1706567696: ext4_mb_generate_buddy:754
<5>[ 305.254312] EXT4-fs (sda1): last error at time 1749060973: ext4_mb_generate_buddy:754
<2>[ 885.341637] EXT4-fs error (device sda1): ext4_mb_generate_buddy:754: group 18386, block bitmap and bg descriptor inconsistent: 0 vs 32768 free clusters
<2>[ 885.355724] EXT4-fs error (device sda1): ext4_mb_generate_buddy:754: group 18387, block bitmap and bg descriptor inconsistent: 0 vs 32768 free clusters

/../

<2>[ 45.301343] EXT4-fs error (device sda1): ext4_mb_generate_buddy:754: group 14, block bitmap and bg descriptor inconsistent: 0 vs 32768 free clusters
<4>[ 46.217826] JBD2: Spotted dirty metadata buffer (dev = sda1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
<4>[ 46.231987] JBD2: Spotted dirty metadata buffer (dev = sda1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
<4>[ 51.808514] EXT4-fs error: 156 callbacks suppressed
<2>[ 51.813427] EXT4-fs error (device sda1): ext4_mb_generate_buddy:754: group 0, block bitmap and bg descriptor inconsistent: 0 vs 27026 free clusters
<4>[ 52.614086] JBD2: Spotted dirty metadata buffer (dev = sda1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
<4>[ 52.627669] JBD2: Spotted dirty metadata buffer (dev = sda1, blocknr = 0). There's a risk of filesystem corruption in case of system crash.

/../

Al;so (?):
<3>[ 3.362160] EXT3-fs (mmcblk0p9): error: couldn't mount because of unsupported optional features (2c0)
<6>[ 3.384008] EXT4-fs (mmcblk0p9): recovery complete
<6>[ 3.389046] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 4.246209] usb 5-1.2: new full-speed USB device number 3 using ehci-brcm
<6>[ 4.415194] usb 5-1.1: new high-speed USB device number 4 using ehci-brcm
<4>[ 4.552670] EXT4-fs (sda1): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 4.652198] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 4.733840] SGI XFS with security attributes, realtime, no debug enabled
<6>[ 4.967778] EXT4-fs (mmcblk0p9): re-mounted. Opts: data=ordered
<30>[ 5.249077] udevd[1075]: starting version 3.2.14
<5>[ 5.254622] random: udevd urandom read with 82 bits of entropy available
<30>[ 5.280622] udevd[1076]: starting eudev-3.2.14
<5>[ 5.530918] random: nonblocking pool is initialized
<6>[ 10.688244] usbcore: registered new interface driver dbus_usbdev
<4>[ 10.733286] bcm_event: module license 'Proprietary' taints kernel.
<4>[ 10.739491] Disabling lock debugging due to kernel taint
<6>[ 10.948997] nexus.ko: virtual irq: enabled (267)
<6>[ 10.953676] nexus.ko: shared gpio banks: enabled
<6>[ 11.734464] usb 5-1.1: USB disconnect, device number 4
<
What can/should I do with this? I have DiskMagic which readsEXT4 volumes via a PC. Odd that one crash file has no such errors. Must be recovering perhaps?

Secondly, There are lots of KODI entries as pointed out by @twol. Are these there for historical reasons or are they supporting my various Android/KODI/Firesticks? There is a .kodi folder in media/hdd/ and it has various subfolders including addons. Like I said, I don't use KODI but I just noticed that KODIO was installed on my main (Android) TV. I've just uninstalled it and restarted the TV. The .kodi folder and contents are still there....

Thirdly, and this looks more interesting,
19:35:15.0736 Traceback (most recent call last):
19:35:15.0736 File "/usr/lib/enigma2/python/Components/Timeshift.py", line 948, in ptsMergeRecords
19:35:15.0742 FileNotFoundError: [Errno 2] No such file or directory: "/media/hdd/movie/20240129 1854 - CNEWS - Face à l'info.ts.meta"
19:35:15.0743 [ePyObject] (CallObject(<bound method InfoBarTimeshift.ptsMergeRecords of <class 'Screens.InfoBar.InfoBar'>>,()) failed)

Where does the bold filename come from?? It was deleted many months ago from movies, so where is it picked up from? Had a look at timeshift.pyc, but couldn't determine much... My guess is that this is the culprit and that some ancient default filename parameter is being supplied perhaps via the KODI stuff... Can't think why though. Over to you...

So that filename is picked up by listdir…so “The“ file exists BUT it looks like we get an encoding error, so when the code goes to open it, the filename is not found. We try to sanitize filenames so there are not encoding errors, but obviously there are non utf-8 characters somewhere in the filename that is causing this issue. So probably the issue starts by having sources from Kodi(?) with non utf-8 characters - which is quite possible with different platforms providing the information.
This was fixed in another module by reading in the filename without decoding (that is the name in binary) but in this case where it opens, extracts other filenames from the data and then merges files, it becomes really complex.

So there is a file on your disk with “almost“ that filename in bold but somewhere in that name are non utf-8 characters that makes it different.

 

[twol]

@JerryK132 -maybe you install the Kodi plugin from the feeds and use that - I am not a Kodi user so have no idea if that will work for you.

 

[JerryK132]

You are missing the point. EPG is correlated by service reference. A channel can be in a billion bouquets if you want. It has no bearing on the EPG.

You have not said how you are scanning. I am presuming that you are using ABM. It only takes a about a minute. I sometimes scan freesat, Sky UK and Sky ROI. I enable the not indexed options for the sky providers, so all services are added to my lamedb file. Most of the channels are identical barring the names on the SI tables.

Anyway, we better leave your confusing/mixing up of EPG/bouquets alone or start a different thread for it so that we can focus on the timeshift crash.

Sorry - I missed part of yr Q! I do use ABM. It happens every day at 4am. I also enable the non-indexed channels option, although I thought this applies to all providers. I scan Sky, FreeSat and F-Terrestrial. Is daily too often - I guess these changes happen infrequently although I know one channel is changing tomorrow!

I noticed the handy new(?) Logs and About options in ABM. Great!

 

[JerryK132]

So that filename is picked up by listdir…so “The“ file exists BUT it looks like we get an encoding error, so when the code goes to open it, the filename is not found. We try to sanitize filenames so there are not encoding errors, but obviously there are non utf-8 characters somewhere in the filename that is causing this issue. So probably the issue starts by having sources from Kodi(?) with non utf-8 characters - which is quite possible with different platforms providing the information.
This was fixed in another module by reading in the filename without decoding (that is the name in binary) but in this case where it opens, extracts other filenames from the data and then merges files, it becomes really complex.

So there is a file on your disk with “almost“ that filename in bold but somewhere in that name are non utf-8 characters that makes it different.

I did wonder. Last night I had downloaded and searched all the .kodi folder contents. No part of the filename appeared. I had already searched Media/HDD/Movie/ with a similar result. Looking a bit more at KODI, it is clear that the .kodi folder on the box is a PVR plugin from KODI put there to serve data to networked KODI devices. Some interwebs chatter about instability, but no obvious alternatives or issues. Clearly a lot of scraping sometimes goes on there...

Just searched all filenames in HDD - nothing like it appears. The culprit (in the log) is dated 20240129 and contains an apostrophe and an a with a grave accent, so a character set issue is possible. I then searched the whole filesystem (/) the only files with that date in the filename are old releases of vix! (6.4.011). Can we look at the uncompiled source file timeshift.py? I could try renaming the .kodi folder and re-installing KODI's PVR plugins from one of my TV clients...

So where/when is listdir picking up the filename? Could my Filezilla be missing a hidden file? I'm assuming all files would be listed, no?

Btw, any thoughts on the disk allocation table errors reported in the crash?

 

[twol]

listdir is on /media/hdd/movie .... but just noticed your Trashcan - it looks huge
I am guessing the file is in the Trashcan ------> /media/hdd/movie/.Trash
I am not sure why its not clearing down - have a look

 

[JerryK132]

listdir is on /media/hdd/movie .... but just noticed your Trashcan - it looks huge
I am guessing the file is in the Trashcan ------> /media/hdd/movie/.Trash
I am not sure why its not clearing down - have a look

Yeah. 2.2GB! Contents of a couple of videos I deleted in the last few days. I think movies persist a bit longer on that folder (is that possible?) as it appears on PVR recordings list. I had been checking the .trash in HDD, but forgotten there was another. Great spot, but sadly no cigar

When you say listdir is on ...movie, what do you mean is it a file, or a function?

 

[twol]

Yeah. 2.2GB! Contents of a couple of videos I deleted in the last few days. I think movies persist a bit longer on that folder (is that possible?) as it appears on PVR recordings list. I had been checking the .trash in HDD, but forgotten there was another. Great spot, but sadly no cigar

When you say listdir is on ...movie, what do you mean is it a file, or a function?

listdir produces a list of all files in that directory - but filenames for use in python are converted to Unicode expecting names to be utf-8.

 

[JerryK132]

Thanks. So what can we conclude? I've looked at all the folders in HDD, especially /movie and the file is not just absent but there are none even remotely like it. Would be good to put the question to the dev who built timeshift.py

I'm tempted to delete folder .kodi - I gather (from ancient vix forum chats) KODI will recreate it, but using the latest plugin version, and from scratch.

I'm also tempted to take the EXT-4 drive out and see if I can remove any errors via my pc.

 

[JerryK132]

Thanks. So what can we conclude? I've looked at all the folders in HDD, especially /movie and the file is not just absent but there are none even remotely like it. Would be good to put the question to the dev who built timeshift.py

I'm tempted to delete folder .kodi - I gather (from ancient vix forum chats) KODI will recreate it, but using the latest plugin version, and from scratch.

I'm also tempted to take the EXT-4 drive out and see if I can remove any errors via my pc.

I've renamed the .kodi folder on HDD and tried a KODI remote client and it's working fine. But no new .kodi folder in sight!!

Just tested a timeshift record. Usual crash although movie files produced fine. Crash file shows no filesystem allocation errors (must have cleared automatically as I didn't). A lot of Kodi activity but the only error was the usual obsolete and unfindable filename!

Still no .kodi folder. I reckon the are using some kind of web system calls/services instead of the old folder based system. Just a guess. I'll do some more KODI research...

 

[abu baniaz]

Re ABM:
I don know what F-Terrestrial is. UK Terrestrial does not change that often. For satellite, once a week is fine, Thursday may be the better day. There is no set day they make the changes, but historically, it was mainly Tuesday and Thursday. Best after 06:30.

 

[JerryK132]

Re ABM:
I don know what F-Terrestrial is. UK Terrestrial does not change that often. For satellite, once a week is fine, Thursday may be the better day. There is no set day they make the changes, but historically, it was mainly Tuesday and Thursday. Best after 06:30.

F-Terrestrial is the French TNT broadcast TV network and they've said they are changing a channel tomorrow. But thanks for that, I'll change my settings accordingly.

 

[JerryK132]

Sorry to hear of your disk problems! Glad it's over.

I've tidied up my system and I'm on 6.7.011. Crash problem still there. Would be good to get a look at the Timeshift.py file mentioned in the crash files and what happens when it is called. The file being requested and giving the error is always the same name and is a file which will have been deleted at least a year ago. I cannot imagine where the name is picked up from!

I've attached a couple more error files in case that helps. Just for the record, doing a timeshift recording always causes a crash, and reboot but other crashes just happen anytime and the stb clock stops and I have to power down. Usually no crash file then either

 

[JerryK132]

Sorry to hear of your disk problems! Glad it's over.

I've tidied up my system and I'm on 6.7.011. Crash problem still there. Would be good to get a look at the Timeshift.py file mentioned in the crash files and what happens when it is called. The file being requested and giving the error is always the same name and is a file which will have been deleted at least a year ago. I cannot imagine where the name is picked up from!

I've attached a couple more error files in case that helps. Just for the record, doing a timeshift recording always causes a crash, and reboot but other crashes just happen anytime and the stb clock stops and I have to power down. Usually no crash file then either

 

[JerryK132]

Files for my previous msg - they would not attach for some reason.

 

[twol]

Files for my previous msg - they would not attach for some reason.

so lets initially try this ......
would be easier if you use something like putty & filezilla to stop the box and copy whilst installing the attached file.
1, use putty to establish session and type init 4 (space between)
2. in /usr/lib/enigma2/python/Components rename Timeshift.pyc to xTimeshift.pyc
3. copy file (Timeshift.py) to /usr/lib/enigma2/python/Components
4. in putty enter init 3 (space between)

hopefully will not crash but would like to see debug log if you have debug entries with "[Timeshift][Timeshift] filelist:" at start of entry .. you might also see this message ....... [Timeshift] Merging records failed!"

 

[paintanddent]

for what its worth==== had similar probs with my duo2--- ended up purchasing new ssd and doing a completely fresh install not using image backup or settings backup--- on my linux pc I copied all recordings from original disk and pasted to new drive-- bit of a bugger setting up from scratch but felt errors were being carried forward with backups.--- solved the problems though, but have NEVER managed to access webif on any duo2 i have