Vu+
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Timeshift error after today's update

Discussion in 'OpenBH Plugins' started by Alexwilmac, Aug 11, 2017.

  1. Alexwilmac

    Alexwilmac BH Lover

    Messages:
    3,731
    After the online update it was available today morning, timeshift started displaying a strange error (strange because my HDD has always been formatted as extfs4 and, above all, because this error has never occurred before.
    As I have daily backups, I restored the yesterday's one and all it's fine now.
     

    Attached Files:

  2. Alexwilmac

    Alexwilmac BH Lover

    Messages:
    3,731
    Has anyone else experienced this issue or is it just me to have it?
     
  3. bogdanm

    bogdanm Moderator

    Messages:
    2,164
    Im no have any update today and yestuday on uno4k.

    Whot was update today on your image box.
     
  4. Alexwilmac

    Alexwilmac BH Lover

    Messages:
    3,731
    But there were either yesterday and today for Solo4K, at least.
    I tried to set ts to start 10 seconds after the zapping instead of 5 and this way it hasn't had this issue, so far. But it's a pity to give up to other 5 seconds because sometimes you want to rewind as much as possible. ;)
    Let's see if it keeps working with this value.
     
  5. Alexwilmac

    Alexwilmac BH Lover

    Messages:
    3,731
    Just not to open a new thread, as the problem is the same despite a completely different OBH version (it was the 0.6 at the time), it still occurs zapping to the 4K channels, any of them.
    Obviously, as the previous times, my HDD is always formatted ExtFS4... So, it's not the file system what really causes the issue.
     

    Attached Files:

  6. Alexwilmac

    Alexwilmac BH Lover

    Messages:
    3,731
    A lot of time has passed and a lot of versions have been released since I reported this issue, but it still happens.
    I don't remember if at the time it occurred in the exactly the same way it occurs now: in 2017 I wrote it happened after zapping to whatever 4K channel.
    But, what's for sure is that (at least now) the message appears after leaving a 4K channel, it doesn't matter if you zap to another 4K one or to a HD or SD one.
    So, it doesn't appear while you zap from a non-4K to a 4K channel, but only after the following zapping, wherever you zap to.
    So, if the 2nd, 3rd, 4th zaps are all to 4K channels, you read it, until you zap to a non-4K, when you get it for the last time.

    The timeshift is set to my internal HDD and it is formatted not as ext2 or ext3 but as ext4. But I think it should not happen, as ext4 is the fs image coders advise to use.
     
  7. acinfo64

    acinfo64 Vu+ Newbie

    Messages:
    10
    I have exactly the same problem on my DUO 4k

    Also tried

    - Format as ext3
    - Changed the mount from ext4 to ext3
    - I also Initialized the harddrive,
    - Setup mount point in device manager.
    - Set the timeshift recording path

    Timeshift is working but I get the error message. I also don't know how to debug. The timeshift.py is not there. The filenames are strange in the timeshift directory. I don't know if that's right or a bug.

    How can I get it to work reliable?
     
  8. Alexwilmac

    Alexwilmac BH Lover

    Messages:
    3,731
    I also tried to use a new external device (a USB flash drive).
    The first time I re-partioned it by OBH and then it formatted it, but the only option was ext4 (or FAT, of course). Actually, I don't believe to the error message that tells you must have a ext2 or ext3 device because I think it's an old message, before the ext4 was released. So I think that every kind of extX partition is good.
    But, just to be sure, I formatted again the USB device as ext3 by Linux and then remapped it under OBH: nothing changed.
    So, this confirms is not a problem of ext2 (whom I didn't try, actually) or ext3 or ext4 but is an issue due to a different reason.
     
  9. acinfo64

    acinfo64 Vu+ Newbie

    Messages:
    10
    Yes for me it's a bug and not working stable. I only need IPTV, FTA and DVB. I loved to use Black Hole for many years, but this is not working for me. Therefore I had to switched to OpenATV. That works perfectly and looks more stable and up-to-date to me (at least for the 2 day I used it until now ;-).
     
  10. Alexwilmac

    Alexwilmac BH Lover

    Messages:
    3,731
    What has this to do with 4K timeshift issue? If you don't use satellite 4K channels, this post is OT. Otherwise, please, explain but don't post at random, please.
     
  11. acinfo64

    acinfo64 Vu+ Newbie

    Messages:
    10
    I don't understand your reaction. The title of the post is "Timeshift error after today's update". My reactions are based on the fact that I have exactly the same problem which I tried to solve.

    I don't know if it is related to 4k because I don't care about 4k (I don't think so because for me it's also happening with other not 4k channels). 4k is also not mentioned in the first posts and title anyhow. It also does not hold for satellite channels alone, it also gives this error with DVB-T2 (although I use both DVB-T2 and DVB-S(2)). Satellite channels is also not mentioned in the first posts or title.

    What I see is there is a problem with timeshift. There is a message saying things about ext3 and ext2 but it seems not be the problem (we both concluded). And, seen the first post, this problem looks to be there for more than 1.5 years.

    So the only thing I was saying is that for me it's a bug which I cannot solve (and I didn't see any solutions on the net), so I'm not on this problem anymore (for now). This all is completely related to the first posts an post title, so for me on topic.

    B.t.w my tuner is a DUO 4K with DVB-T2 and DVB-S(2).
     
    el bandido likes this.
  12. Matrix10

    Matrix10 Administrator

    Messages:
    8,708
    Do not worry ,the bug is fixed.
     

Share This Page