Brandonb1987

Members
  • Posts

    29
  • Joined

Everything posted by Brandonb1987

  1. I tried again from the dockers console. No go. Tried it in the unraid console using chown -R 1000:1000 /mnt/user/Appdata/Nodered/.npm This fixed the issue and allowed me to update the palletes.
  2. getting an npm error in the nodered docker. When i try to update a pallet it gives me the following: I tried running the command in the console and just denies me. Any suggetions?
  3. I never needed to open any ports before, that's the only thing I can think of that it could be.
  4. the only thing I’ve changed was I replaced duckdns with cloudflare but I did not change anything around Deluge. Again. Works totally fine with the VPN turned off. Can access it totally fine. Soon as I re-enable the VPN, can’t see the UI. my log shows it starting everything just fine. Shows webui started, vpn connected, listening to privoxy port. that’s the only issue. So do you want 2 logs one showing with vpn off and another with on? Or just on?
  5. I can confirm I have the exact same issue. I've been trying to fix it all week thinking it was maybe a port/dns/firewall issue. I've ruled it all out and lead me to here. Something is up with the VPN portion of PIA. I tried switching to the WireGuard implementation and it works without VPN turned on. Log shows no errors, just can't see the UI like reported.
  6. I've been having a problem for the last 2 weeks where I cant get Sonarr to connect to Deluge. It keeps giving me the error Unknown exception: The operation has timed out.: 'http://10.1.10.3:8112/json' Anyone else encounter this issue starting about 2 weeks ago? Was working perfectly fine up until then, and because I have automatic updates enabled I wont ever know when the issue exactly started. Any logs I can post to assist in finding a solution?
  7. No longer able to boot into GUI MODE since 6.9. Just hangs with black screen and blinking cursor. Was working fine on 6.8.3
  8. Has anyone had issues with other non-admin users not being able to stream via chromecast? (in the last 2 weeks or so) It keeps giving everyone a "too many active streams" error when they try. It works on all apps and stuff but as soon as they try and use chromecast the error appears. I've tried deleting both their profiles multiple times, made sure nobody else is using it, etc. I just can't figure this out. I feel it may be either a container issue or there's something that isn't closing itself down properly. If I go to the Dynamix Active Stream add-on, it has a list of Plex things but they can't be halted. Anyone got any theories?
  9. This thread shows you what to do. I implemented it and it works like a charm!
  10. I’ve tried to do the memtest but it seems every time I try to select it, the whole system restarts and just goes back to the boot screen. Ideas?
  11. I’m thinking it’s the marvel based HBA as everything is happening to the first 8 drives only. That HBA is likely the culprit as you say. I’m going to order an LSI card and replace them both and run the memtest as a precaution. Hopefully that will fix it.
  12. I've had quite a few issues with my unraid the last few weeks. First drive 1 pooped itself and became read-only. Managed to get everything off it and put the data onto other disks before removing the drive and resetting the pool without it. After this was completed, I ran a scrub on all the disks (15/16 disks now) and found 5 files that were not correctable. I have since replaced/removed the files in favour of good copies. Hopefully this is fixed. I felt it was prudent to do a filesystem check on all the drives today since i've had so many problems and now I'm getting a few errors on 3/15 disks. What would be the best way to fix this? Should I do the same as I did to drive 1 (pull data off and place onto the good disks and reformat the disk)? Or can I simply pull the disk, format it, and reinstall and let it rebuild from parity? Part 2 of this issue: After having a read through the log, it appears this is really isolated to my first 8 drives which is all on 1 controller. Could the HBA be the cause for all these issues lately? Would it be a good idea to get it replaced?
  13. I've tried everything to get stuff off disk 1 but i keep getting Input/output error with some files. I can't even copy certain ones out of my Snapshots because it appears they are corrupt as well. Suggestions? I purchased a new disk to replace it - suggestions?
  14. I just thought of something. I take daily snapshots of my Btrfs system. If I were to just pull disk 1, format it, and restore the files onto disk 1 from the snapshot, would that fix the issue? I’ve never had to restore files from a snapshot yet though so not entirely sure of the process
  15. I’ll move everything off the disk and reformat. I’ll also check the cables and reseat it to make sure it’s ok. I’ll let you know the results
  16. So does the diagnostics show a dead/dying drive? If so I will order a new one or is there a way to fix the file system? If I were to run a pre-clear would that correct the issues after reformatting?
  17. I'm not sure if this will show it. I may have restarted since the start. Currently rebuilding the disk to see if that corrects the issue. I did run a BTRFS system check and there are lots off errors and issues. Repaired them as much as possible but it seems like theres a ton (which is why i'm trying to rebuild) zeus-diagnostics-20190331-0529.zip
  18. Fun fact, rebooted the server and now Fix Common Problems alerted me of this error "Unable to write to disk1-Drive mounted read-only or completely full." - The disk is not full. I've had errors pop up from time to time on this disk. Could it be a disk related issue?
  19. Ok, but that doesn't solve the files/folder issue I have. That will fix the issue from getting worse. Googled for nzbget and its under UMASK and have to make it 000 to get a permission level of 777. I also found the section to change the file and folder permissions in Sonaar - set both to 777. How do I make everything in the share to 777 then? Follow my post above to change permissions then do the chown to make sure everything is under the proper nobody:users? Or is everything better to be put under root:root? I've tried "sudo chmod -R 777 /mnt/user/Media/" and all I get is this type of error for all the files "chmod: changing permissions of '/mnt/user/Media/Movies/The Mule.mp4': Read-only file system"
  20. Correct me if I'm wrong, but I believe this is what I need to do; 1) sudo chmod -R 777 /mnt/user/Media/ (and do this for the other shares like /mnt/user/Download) 2) sudo chown -R nobody:users /mnt/user/Media/ (and do this for the other shares like /mnt/user/Download) Would this fix all the issues?
  21. So i've been using Unraid for a while now with minimal issues that have come up that couldn't be fixed. I just updated to 6.7RC6 with no issues. I've been using NZBget and Transmission for downloading media along side Sonaar with no issues up until today. I downloaded a new series (Station 19) over NZBget today and something weird happened with the permissions making me unable to delete them or move them to a different share. As far as I can tell its permission related. I've tried the tools New Perms and the Docker Safe, not fixed. I'm not savy enough to figure out how to change the perms manually to allow the system to edit the title, delete files, or move them. It seems to be at a User Share level but I cant confirm. Here is the output when I list them: (both the folder level and the files within the folder causing the issue root@Zeus:~# ls -la "/mnt/user/Download/" total 32 drwxrwxr-x 1 nobody users 2832 Mar 30 14:00 ./ drwxrwxrwx 1 nobody users 26 Mar 30 15:19 ../ -rwxrwxr-x 1 nobody users 14340 Mar 30 13:35 .DS_Store* <----CANT DELETE THIS ONE EITHER AND WANT TO drwxrwxr-x 1 nobody users 0 Dec 24 11:27 13\ Reasons\ Why/ <-----COMPLETELY FINE drwxr-xr-x 1 nobody users 32 Mar 30 13:27 Station\ 19/ <-----------------------------------ISSUES THROUGHOUT (2 seasons within) root@Zeus:~# ls -la "/mnt/user/Download/Station 19/Season 1" total 14244788 drwxr-xr-x 1 nobody users 492 Mar 30 13:33 ./ drwxr-xr-x 1 nobody users 32 Mar 30 13:27 ../ -rwxr-xr-x 1 nobody users 1067075126 Mar 23 2018 01\ -\ Stuck.mkv* -rw-rw-r-- 1 nobody users 1173701285 Mar 22 2018 02\ -\ Invisible\ to\ Me.mkv -rwxrwxrwx 1 nobody users 1608867420 May 19 2018 03\ -\ Contain\ the\ Flame.mkv* -rw-r--r-- 1 nobody users 1505993923 Mar 30 12:46 04\ -\ Reignited.mkv -rw-r--r-- 1 nobody users 1281228287 Mar 30 12:52 05\ -\ Shock\ to\ the\ System.mkv -rw-r--r-- 1 nobody users 1273811097 Mar 30 12:58 06\ -\ Stronger\ Together.mkv -rwxr-xr-x 1 nobody users 1262525439 Apr 27 2018 07\ -\ Let\ It\ Burn.mkv* -rw-r--r-- 1 nobody users 1328311142 Mar 30 13:11 08\ -\ Every\ Second\ Counts.mkv -rw-r--r-- 1 nobody users 1146491895 Mar 30 13:16 09\ -\ Hot\ Box.mkv -rwxr-xr-x 1 nobody users 1111705584 May 19 2018 10\ -\ Not\ Your\ Hero.mkv* -rwxr-xr-x 1 nobody users 1826928842 Mar 29 10:12 s01e11\ dont\ know\ why.mkv* root@Zeus:~# ls -la "/mnt/user/Download/Station 19/Season 2" total 12453064 drwxr-xr-x 1 nobody users 788 Mar 30 13:59 ./ drwxr-xr-x 1 nobody users 32 Mar 30 13:27 ../ -rw-r--r-- 1 nobody users 1281436710 Mar 30 13:30 Station\ 19\ -\ 2x01\ -\ No\ Recovery.mkv -rwxrwxrwx 1 nobody users 1355284821 Oct 12 04:11 Station\ 19\ -\ 2x02\ -\ Under\ The\ Surface\ (2).mkv* -rwxr-xr-x 1 nobody users 1227354156 Oct 19 04:07 Station\ 19\ -\ 2x03\ -\ Home\ To\ Hold\ Onto.mkv* -rw-r--r-- 1 nobody users 1378694500 Mar 30 13:39 Station\ 19\ -\ 2x04\ -\ Lost\ and\ Found.mkv -rwxr-xr-x 1 nobody users 1138715708 Nov 2 03:11 Station\ 19\ -\ 2x05\ -\ Do\ a\ Little\ Harm.mkv* -rw-r--r-- 1 nobody users 1066970011 Mar 30 13:45 Station\ 19\ -\ 2x06\ -\ Last\ Day\ on\ Earth.mkv -rw-r--r-- 1 nobody users 1926910354 Mar 30 13:49 Station\ 19\ -\ 2x07\ -\ Weather\ the\ Storm.mkv -rwxr-xr-x 1 nobody users 1346573356 Mar 8 04:12 Station\ 19\ -\ 2x08\ -\ Crash\ and\ Burn.mkv* -rwxr-xr-x 1 nobody users 1005018106 Mar 15 03:11 Station\ 19\ -\ 2x09\ -\ I\ Fought\ The\ Law.mkv* -rwxr-xr-x 1 nobody users 1024955299 Mar 22 03:11 Station\ 19\ -\ 2x10\ -\ Crazy\ Train.mkv* As you can see the perms are all over the place. Is there a command that I can run to change it on a full share level so that everything can be modified/deleted/moved? Please help PS: As far as I'm aware, everything should be like this (-rw-rw-rw- 1 nobody users 366982490 Jul 18 2014 01\ -\ Acceptance.avi). How do I force every file to be like this while folder levels like this (drwxrwxr-x 1 nobody users 0 Dec 24 11:27 13\ Reasons\ Why/). There are also some random files in other folders that are like this (-rw-r--r-- 1 root root 586046642 Mar 30 12:20 09\ -\ Breast\ Cancer\ Show\ Ever.mkv)....I don't know why!
  22. So long story short, was trying to follow the tutorial on this post I made a mistake creating my first snapshot which has made a full read only directory in a backup folder I created. I forgot to add the variable to the folder to give it a date. I want to delete the entire folder but when I tried "rm -r /mnt/disk1/Backup/Snapshots/Data/Data/" it just gives me a cannot remove - read only file system. I want everything past "/mnt/disk1/Backup/Snapshots" deleted. Anyone able to help me get rid of that entire folder? I'm not fluent in linux command lines
  23. Yes, if you have existing data on the disk(s) it can take a while to move the data to the subvolume since it's like a disk to disk copy, it can't be moved directly, but there's a way around that, this is what I did to quickly convert a share to a subvolume: Rename current share to a temp name: mv /mnt/disk1/YourShare /mnt/disk1/temp Create a new subvolume with old share name: btrfs sub create /mnt/disk1/YourShare use btrfs COW to do an instant (or almost instant, it can take a few seconds) copy of the data to the new subvolume cp -aT --reflink=always /mnt/disk1/temp /mnt/disk1/YourShare Delete temp folder rm -r /mnt/disk1/temp Done, repeat this for all disks and shares I need clarification for the “repeat this for all disks and shares”. I have an array of 18 disks. Currently just using regular shares but want to start taking snapshots. what I did to test this was moved all “data share” onto disk 1 as it was spread over several disks as a regular share. Worked great! But now here is my question; If if I were to move all my data from the “data share” onto a single disk, and follow the commands for that single share, do I need to repeat the commands for each disk with the same name so it can propagate files onto those disks as the drive gets full as it does using basic shares? Or will it do that on its own? Then I would do the same thing for each disk for the “movie share”?