Jump to content

qw3r7yju4n

Members
  • Posts

    80
  • Joined

  • Last visited

Posts posted by qw3r7yju4n

  1. 9 hours ago, ich777 said:

    What way? Can you share it with us?

     

    If you cannot uninstall it it is not installed.

    Are you sure that it is not in the Plugins Error tab on your Plugins page.

     

    Usually when it‘s not installed it is enough to reboot and then install it again.

    If it‘s in the Plugins Error tag then remove it from there, reboot and install it again.

    You're exactly right. It was errored plugin. I removed it and will reboot when i can. I do not use the driver currently. It is a backup for Intel QSV. Thanks for your help and concern. I will come back to this thread if your solution does not work. but it will be a few days

  2. 18 minutes ago, qw3r7yju4n said:

    I cannot uninstall it. Its not there to uninstall in the UI. But, it is clearly there according to the error. is there a manual CLI option?

    I found a way to remove it. Rebooting soon thanks for your help.

  3. 31 minutes ago, ich777 said:

    Please uninstall the driver, reboot, install the driver from the ca app and reboot again.

     

    You are also most likely on of the users who didn‘t see the line about waiting until you get a notification until its safe to reboot when upgrading to the newer Unraid version.

    I cannot uninstall it. Its not there to uninstall in the UI. But, it is clearly there according to the error. is there a manual CLI option?

  4. FIxed it!

     

    I just used the read setting feature and read the settings from the test share. I also removed all the manual disk assignments and changed it to "All" disks. Wrote a file to the share and the mover is writing to the orphaned drive. Thanks to the mods and their wisdom!  Thank you

    • Like 1
  5. 1 hour ago, JorgeB said:

    Not really, if you create a new test share and copy a couple of files there does it behave correctly?

    Ok - I created a test share and moved files to it. Invoked mover and it is writing to one of the orphaned drives. So something in the share config is borked. You know more than me.

  6. 1 minute ago, JorgeB said:

    zero is no floor set, if your biggest file is 125GB that's a good setting, but in this case is mostly to see if it changes anything, because the current config looks correct to me.

    Thanks for taking the time. I really appreciate it. I'll write back tomorrow 1200hrs EDT when mover runs

  7. 55 minutes ago, JorgeB said:

    Try setting a small share floor, a user reported that it started working after changing it.

    Mine was already set to 0. I manually set it to twice the size of my biggest file. So thats 250GB. I guess ill wait till tomorrow to see the results

  8. 1 hour ago, itimpi said:

    I must admit even on looking closer I cannot spot any reason for the behaviour you are experiencing.

     

    I notice you have not rebooted for some time - might be worth trying that just in case it applies the 'magic sauce'.   Could combine this with the upgrade to the 6.12.4 release.

    Ok, I'll give it a shot. Thanks for your help!

  9. 2 minutes ago, itimpi said:

    … and an example share name showing this behaviour?

     

    I cannot spot an obvious issue so would like to focus more sharply if possible

     

    BTW:   You seem to have a lot of .cfg files in the config/shares folder on the flash drive for shares that no longer exist.    It might be worth deleting these to tidy up the diagnostics.

    Sorry bout that. Share is Media 

  10. My mover is not writing to 2 of my drives. It just skipped a drive with 1.41tb left, in order and in favor of a drive with 1.11tb. 

     

    Is there logic i dont know of? Because I have a 2 drives one with 1.53tb and one with 1.41tb free. The mover is skipping these drives in favor of fuller drives. I thought the mover is spossed to write to least full device to certain levels, ie. 1.12tb and 550gb.

     

    Any info and help is appreciated

     

    EDIT - Share is set to High-Water. But doesnt seem to be choosing the highest

  11. I have a container that is stuck in removing. My docker page will not stop refreshing and the offending container is visible sometimes. When I do a docker rm it says it's already removing. I have stopped the docker service and restarted and still the same.

  12. I have a thought, In my reading I recall a mention that if external storage is enabled that transcoding would be effected. I use nextcloud to share my shares so this transcoding feature is something I cant use if my research was correct.

     

    WIth that said, I would like to migrate back to the Nextcloud official, I don't know what the chown command would be to set it back to nobody? Could someone help me out here? 

     

    Not this

    chown -R 33:33 /mnt/user/nextcloud/

     

    but maybe this?

    chown -R 99:100 /mnt/user/nextcloud/

×
×
  • Create New...