rpmalouin

Members
 View Profile  See their activity

  • Posts

    13

  • Joined

  • Last visited

 Content Type 

Everything posted by rpmalouin

  1. rpmalouin
    check deluge settings, downloads. the path is the container path not the actual path. /data/incomplete
  2. rpmalouin
    Having issues with getting to deluge vpn on port 8112 on the bridge network. Will not connect. Strangely, if I move it to a custom:br0 and use the port still can't connect but if I just drop the port and just use the ip, working simply fine. It's the same with or without vpn enabled. Without port access Prowlerr will not work. Resolved, port issue duh
  3. rpmalouin
    Stop the array, go to log you will see the mount that is causing the issue. You will see an error unable to unmount mount busy then its as simple as doing this in the terminal window umount -l /dev/loop2 changing /dev/loop2 to your needs the array will now stop re-start the array and check where your copy/move got stuck.
  4. rpmalouin
    Of note I cannot change the container from anything but 8080. No matter what I try when I click webui it goes to 8080 not in my case 8086. My solution was to take lucky backups off 8080 and put it on 8086. Everythine is working now.
  5. rpmalouin
    Figured it out, the plugin creates a dataset on zfs just fine, it also creates a share but creates the share as array primary and zfs pool secondary. The fix is to go into the share and change it to zsf pool primary no secondary (in my case). In Lucky Backups I needed to change the share from /mnt/user to just /mnt this will show all my disks.
  6. rpmalouin
    Disk 1 is xsf (array disk) and Backup is zfs (stand alone) even creating sub-directories data is stored on the array.
  7. rpmalouin
    If I create a zfs dataset using the plug in on a standalone zsf formatted drive (not part of the array) why does it show as mounted on the array and the stand-alone disk? When using LuckyBackups to backup array files to a dataset on the stand-alone drive all the data is put on the array disk not the stand alone.
  8. rpmalouin
    Re-saving the settings cleared the error. Thank You. ab.debug (2).log
  9. rpmalouin
    I could have missed something really don't know I will try and resave the plug in settings.
  10. rpmalouin
    So need a little help with this warning, started 2 days ago when I swapped out my cache. "XML not found for " blank no name. ab.debug.log
  11. rpmalouin
    perfect, thank you
  12. rpmalouin
    So 8 years later this saved me after a power failure, lost all my docker containers. Who knew it was so EASY restore them not me but I do now.
  13. rpmalouin
    There is a little bit of work to do in iDrive to get this working correctly. See attached for what you need to do in iDrive.