Jump to content

Kloudz

Members
  • Posts

    39
  • Joined

Report Comments posted by Kloudz

  1. 5 hours ago, galloglypg said:

    What does 

     

    Version 6.12.0-rc8 2023-06-10

    Changes vs. 6.12.0-rc7

    Bug fixes:

    "Fix regression error in rc.S: must install third-party drivers before first invocation of udev." mean?  I just updated to 6.12 and plex wont start due to "libusb_init failed" I believe this is some kind of issue with udev. 

    libusb_init failed can be be ignored. I think the error is related to Plex looking for USB Tuner cards. My Plex also throws this error and still works

     

    That said if you're using nvidia drivers. My Plex wouldn't start either, I had to reinstall by clicking update and download because the GPUID was empty after I upgraded from 6.11.5 to 6.12.2 rc8.

    • Thanks 1
  2. 1 hour ago, Kloudz said:

    So the Mover Scheduler did trigger but see this in the log:
    image.thumb.png.3145c36180e97cd797186de332247399.png

     

    It looks like it's possible that CA Mover Tuner may be the culprit here. That said a new version of CA Mover Tuner just got updated in the last hour and mentions RC8:

    image.png.114b81d9a3353aa7261d4da51d319323.png

     

    So instead of uninstalling the Mover Tuner, I'm just gonna update it and see if it fixes the mover scheduler

    @JorgeB confirmed, since updating CA Mover Tuner. Based on schedule, Mover was triggered and now moving files as the time of this post.

    • Like 1
  3. 52 minutes ago, Kloudz said:

    Yep, thats my next steps. Waiting for Mover to kick in after re-applying settings. And if it doesn't work, I'll uninstall the plugin to see if it's causing mover not to work

    So the Mover Scheduler did trigger but see this in the log:
    image.thumb.png.3145c36180e97cd797186de332247399.png

     

    It looks like it's possible that CA Mover Tuner may be the culprit here. That said a new version of CA Mover Tuner just got updated in the last hour and mentions RC8:

    image.png.114b81d9a3353aa7261d4da51d319323.png

     

    So instead of uninstalling the Mover Tuner, I'm just gonna update it and see if it fixes the mover scheduler

  4. 2 minutes ago, JorgeB said:

    It is working, try re-applying settings, also make sure mover logging is enabled, and you should see this logged:

     

    Jun 10 18:00:02 Tower root: mover: started
    ...
    Jun 10 18:00:02 Tower root: mover: finished

     

     

    Thanks, thats what I did earlier. So waiting for it to kick in.

    Also, do you think CA Mover Tuning has something to do with it if its not working?

  5. Is the Mover Scheduler not working on RC8? I noticed my cache drives are still populated with Data. The only time I know Mover is working is when I manually click "Move Now" in Main tab.

    I have the scheduler set to run every 2 hours and I still see a file that was I created yesterday around 3pm in the drive.

  6. Just updated from 6.11.5 to 6.12.0 rc8 and Wanting to know if this is normal: image.png.114c6e6286719adbad79ec813899cf26.png

    Media is set to go from a 'cache' share then to the array. Right now, there are files in the 'cache' and set to move to the array when mover is running.

     

    Why does it say 'All files protected' with a green dot. It should be the yellow/orange triangle. Is it because it's in a ZFS Encrypted pool? And maybe thats why the lock is yellow/orange?is this expected? 

     

    I'm expecting this triangle and messaging: image.png.543ee40835c1eaabf2c29e03fe9fc050.png

×
×
  • Create New...