Can0n

Members
 View Profile  See their activity

  • Posts

    617

  • Joined

  • Last visited

 Content Type 

Everything posted by Can0n

  1. Can0n
    I was able to resolve by uninstalling recycle bin, deleting all the .Recycle Bin hidden directories on my shares, and rebooting the server and re-installing recyclebin, i had to reboot as unRAID was stuck in a perpetual mover (over 15 hours and no reading or writing to or from the ssd cache or array) and in my bottom status bar it was stuck on starting services....recyclebin is back and running thanks again @dlandon awesome little plugin
  2. Can0n
    i downgraded two of my servers both having same issue ill report that to the unraid guys the downgrade option seems to break mover among other things.. yeah i left it the bin was only about 30GB on Thot, Sif was having same issue nginx crashed after a few minutes of waiting and i used the command line to restore the web GUI...and i noticed mover is stuck on but not actually moving anything as well as "services starting" stuck at the bottom
  3. Can0n
    Hi again @dlandon I had to downgrade my main server (Thor) back to 6.6.6 due to some issues i was having with dockers on my Fedora VM used for a reverse proxy,and since downgrading i get a blank screen on Recycle Bin and this in the main logs Feb 8 23:35:04 Thor nginx: 2019/02/08 23:35:04 [error] 6729#6729: *1209407 upstream timed out (110: Connection timed out) while reading upstream, client: 10.0.0.12, server: , request: "GET /Settings/RecycleBin HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "myserver.unraid.net", referrer: "https://myserver.unraid.net/Settings" Feb 8 23:35:04 Thor nginx: 2019/02/08 23:35:04 [error] 6729#6729: *1209407 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.0.12, server: , request: "GET /plugins/dynamix.local.master/include/LocalMaster.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "https://myserver.unraid.net", referrer: "https://myserver.unraid.net/Settings/RecycleBin" Feb 8 23:35:04 Thor nginx: 2019/02/08 23:35:04 [error] 6729#6729: *1209407 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.0.12, server: , request: "POST /plugins/dynamix.system.temp/include/SystemTemp.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "https://myserver.unraid.net", referrer: "https://myserver.unraid.net/Settings/RecycleBin" I have tried removing and re-adding the plugin. I haven't tried restarting the server yet but will when my client load is lower than it is. Any other suggestions??
  4. Can0n
    Thanks for the update, works great but might have found a bug... I had appdata, system and flash excluded with the commands 'appdata', 'system', 'flash' the shares tab still shows it all and the main empty all trash button still clears all despite the exclusion
  5. Can0n
    I do have that setting on No on all three servers as you can see in the screenshots (Green is Sif, Red is Freya, Blue is Thor). I do expect that if Enable on UD is set to no that the recycle bin only shows files stored on the server you are actively viewing, I also expect if i exclude a share name mounted by UD that it would also exclude looking at the recycle bin files in that share (mounted locally or remotely) just by its wording.
  6. Can0n
    i guess my point is flexibility to exclude remotely mounted disks....UD assigns all mounted volumes to /mnt/disks not /mnt/disk<#> an option to exclude that could simplify the interface and only show what on the the servers local recycle bin i see the main icon at the top one does indeed kind of currently work as a one click solution where all is removed even on remotely mounted servers, where the shares tab below is more finely grained control of only deleting off the current server you are in the interface for. i could adapt but i was initially confused when i deleted a 3MB file on one server and a 168MB on another why the first server is showing 172MB in the recycling bin??...then saw same amount on other server when i emptied on one both servers were cleared. it makes for an easy ooopsie if you mean to check the recycle bin on one server but are ready to empty the other and the main empty button will empty all recycle bins if the remote shares are mounted
  7. Can0n
    maybe the recyle bin could have an option to exclude anything mounted to /mnt/disks/ (not to be confused with local array disks being stored on /mnt/disk#
  8. Can0n
    Ok this might make it easier to understand Freya has the red banner and Thor has the Blue one to tell them apart I have the main tab, shares tab and recycle bin settings for the two im mostly concered with (Sif is Green but not listed) I see that the users tab in recycle bin shows only the bin for the server its being viewed on so my question is with the mounts i have on the main page is there a way to exclude Thor on Freya and Sif, Exclude Freya on Thor etc? i have tried with: partial share name 'full sharename' (as Unraid see it where its mounted to /mnt/disks/
  9. Can0n
    I am little confused. I do want the recycle bin for the 4K share on Freya and the Media share on Thor the main thing im seeing is if i mount a Thor share on Freya i see that the main Recycle bin sees the totals of both recycle bins (the one on Media for Thor and the 4K one on Freya) i found did the upgrade back to Thor for rc2 to be able to mount "remote" SMB shares let me grab some new screenshots and post
  10. Can0n
    Hello @dlandon me again different issue......Unassigned Devices doesn't play well on 6.7.0 rc2 when using the black theme the pop up when mounting a remote smb/nfs connection it comes up white with white font the other three theme (White, Gray, Azure) are not impacted as they all use a black/gray font, but the black theme uses a white font
  11. Can0n
    Hello @dlandon here are a couple annotated screenshots...I am troubleshooting thor right now as i cannot mount anything from 6.7.0rc2 onto 6.6.6 Freya has only one share not for system use thats a share named 4K Thor has a few shares but the one i mount on Thor is Freya_Media (maps to /mnt/user/4K on Freya) Freya has a mount of THOR_Media (mapped to /mnt/user/Media on Thor)
  12. Can0n
    Hi I would love to but i downgraded one of my servers back to 6.6.6 and now i cant mount any shares from 6.7.0 rc2 and the recyle bin plugin isnt loading at all on the one i downgraded. im going to remove unassigned devices as that seems to be what hanging Recyclebin up ill try and get you screenshots once i duplicated it
  13. Can0n
    Hello @dlandon I am having some issues with this plugin on unRaid 6.7.0 rc2 (wasnt paying attention on rc1 sorry) I run three unraid server all with the recycle bin plugin and a couple shares mapped (using unassigned devices) from and two each ill try and explain the server names are this Thor Sif Freya Thor has two mapped shares /mnt/disks/Sif_Backup and /mnt/disks/Freya_Media Freya has one mapped back to Thor with /mnt/disks/THOR_Media the issue is if i delete files on Freya both Thor and Freya see the same recycle bin size. and vice versa if i delete on thor Freya see the files in its recycle bin, if the files reside on Thor and i empty on Freya both recycle bins empty I have use unassigned devices set to no on all server and even set the shares mounted to be excluded but both still show each others and combined recycle bin can you take a look please and if you need anything else let em know
  14. Can0n
    I see RC 2 fixed the on colour thank fro that but we lost the delay start up under dockers and presumably VM's could we get that back please????
  15. Can0n
    Hello @binhex I noticed on unRaid 6.7.0 both rc1 and rc2 i no longer see a webgui option for plexpass version of your docker when clicking on the icon you only get console and the reset below...manually entering the url (ip:32400) works though so the docker itself is loading up
  16. Can0n
    reboot corrected the odd behavior thanks @johnnie.black
  17. Can0n
    i did have a 256GB SSD on there from 6.6.6 and kept it until the 6.7.0-rc1 install I then stopped the array removed the 256GB one (hated loosing 500GB to the raid 1 setup) and started the array (did not use New Config)...there was a check box to allow the missing cache by the start array option... thanks for the advice ill reboot after the mover is done and current downloads from sabnzbd are completed.
  18. Can0n
    sorry wasnt sure needed to add diags for a GUI issue will add to OP
  19. Can0n
    just took the plunge on 6.7.0-rc1 on 1 server with a 1TB SSD for Cache and thought I read somewhere else someone is seeing the same issue but cant find it (sorry if this is a duplicate). my 1TB is being reported as a 8.3GB drive showing an unsually low amount of used and free I have tried the BTRS balance and Scrub without a change My disk Log: Jan 24 04:44:40 Freya kernel: ata2: SATA max UDMA/133 abar m2048@0xfe705000 port 0xfe705180 irq 35 Jan 24 04:44:40 Freya kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jan 24 04:44:40 Freya kernel: ata2.00: supports DRM functions and may not be fully accessible Jan 24 04:44:40 Freya kernel: ata2.00: ATA-11: Samsung SSD 860 EVO 1TB, S3Z8NB1KB27695A, RVT02B6Q, max UDMA/133 Jan 24 04:44:40 Freya kernel: ata2.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32), AA Jan 24 04:44:40 Freya kernel: ata2.00: supports DRM functions and may not be fully accessible Jan 24 04:44:40 Freya kernel: ata2.00: configured for UDMA/133 Jan 24 04:44:40 Freya kernel: ata2.00: Enabling discard_zeroes_data Jan 24 04:44:40 Freya kernel: sd 2:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) Jan 24 04:44:40 Freya kernel: sd 2:0:0:0: [sdc] Write Protect is off Jan 24 04:44:40 Freya kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Jan 24 04:44:40 Freya kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 24 04:44:40 Freya kernel: ata2.00: Enabling discard_zeroes_data Jan 24 04:44:40 Freya kernel: sdc: sdc1 Jan 24 04:44:40 Freya kernel: ata2.00: Enabling discard_zeroes_data Jan 24 04:44:40 Freya kernel: sd 2:0:0:0: [sdc] Attached SCSI disk Jan 24 04:44:40 Freya kernel: BTRFS: device fsid 9b666354-df3d-4e58-a3a7-f79a6d727f7b devid 1 transid 2889 /dev/sdc1 Jan 24 04:44:57 Freya emhttpd: Samsung_SSD_860_EVO_1TB_S3Z8NB1KB27695A (sdc) 512 1953525168 Jan 24 04:44:57 Freya emhttpd: import 30 cache device: (sdc) Samsung_SSD_860_EVO_1TB_S3Z8NB1KB27695A Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): disk space caching is enabled Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): has skinny extents Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): enabling ssd optimizations Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): resizing devid 1 Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): new size for /dev/sdc1 is 1000204853248 Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): resizing devid 2 Jan 24 04:45:01 Freya kernel: BTRFS info (device sdc1): new size for /dev/sdd1 is 256060481536 Jan 24 04:50:47 Freya emhttpd: shcmd (113): /usr/sbin/hdparm -S0 /dev/sdc Jan 24 04:50:47 Freya root: /dev/sdc: Jan 24 04:51:26 Freya emhttpd: Samsung_SSD_860_EVO_1TB_S3Z8NB1KB27695A (sdc) 512 1953525168 Jan 24 04:51:26 Freya emhttpd: import 30 cache device: (sdc) Samsung_SSD_860_EVO_1TB_S3Z8NB1KB27695A Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): allowing degraded mounts Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): disk space caching is enabled Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): has skinny extents Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): enabling ssd optimizations Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): resizing devid 1 Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): new size for /dev/sdc1 is 1000204853248 Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): resizing devid 2 Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): new size for /dev/sdd1 is 256060481536 Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): balance: force reducing metadata integrity Jan 24 04:51:42 Freya kernel: BTRFS info (device sdc1): relocating block group 4316987392 flags system|raid1 Jan 24 04:51:43 Freya kernel: BTRFS info (device sdc1): relocating block group 2169503744 flags data|raid1 Jan 24 04:51:43 Freya kernel: BTRFS info (device sdc1): found 66 extents Jan 24 04:51:43 Freya kernel: BTRFS info (device sdc1): found 66 extents Jan 24 04:51:43 Freya kernel: BTRFS info (device sdc1): relocating block group 1095761920 flags metadata|raid1 Jan 24 04:51:43 Freya kernel: BTRFS info (device sdc1): found 8 extents Jan 24 04:51:43 Freya kernel: BTRFS info (device sdc1): device deleted: /dev/sdd1 DONE freya-diagnostics-20190124-0546.zip
  20. Can0n
    it seems at least one plugin requires 6.7.0 RC1 !!! Dynamix System Statistics plugin: updating: dynamix.system.stats.plg plugin: installed Unraid version is too low, require at least version 6.7.0-rc0i
  21. Can0n
    Hello @limetechand @eschultz...New dash looks awesome wondering if this current rc has the Mellanox Infiniband drivers baked in yet? I sent 5 cards for testing to get integrated last year and Eric said it might have to wait for 6.7.x thanks cant wait to try this but I dont have a spare server that isnt mission critical at this time and reports of cache pool failure and docker failure scares me a bit too much for RC1
  22. Can0n
    I realize this is more a browser specific issue than unRaid but thought i'd put it here as well as report it to Google since its their update that broke it and will break in Chrome soon if not fixed in time
  23. Can0n
    Changed Status to Open Changed Priority to Urgent
  24. Can0n
    ***Edit*** Google updated Canary again and the interface loads now ***Edit*** I found out last night Google Canary wont load the Unraid interface Google Chrome is up to date Version 73.0.3677.0 (Official Build) canary (64-bit) Chrome Google Chrome is up to date Version 71.0.3578.98 (Official Build) (64-bit) does without issues I get I see that Canary is running two versions newer than Chrome so just more of a heads up I have reported this to Google already and in case Chrome stops working for anyone
  25. Can0n
    gotcha