sonofdbn

During my scanning, there's a bunch of popup messages on the lower right listing things like "Processing media for album...." or the occasional "Scanner error" when there's a problem (for me, usually a weird video file).

In the last few days I've had a problem with my speeds coming down substantially. I usually get around 25 MiB/s in total, but now I usually get around 6-8 MiB/s. What is odd is that if I restart the container, I get back to full speed initially, but then it comes down again. I use PIA (and Wireguard) and have tried different endpoints, with the same result. What I have noticed in the log files is that I get this line repeated every 15 minutes. 2022-05-05 20:20:48,836 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port 'nnnnn' I don't recall seeing this happening before, and wonder if this has anything to do with the slowing down. Or is this a PIA issue or something else? Edit: So after analysing what I could, it seems that the speed differences are probably a result of the vagaries of torrents. When I look at longer periods of total traffic, it's hard to discern any real pattern. So looks like nothing to worry about, although I'm still not sure whether the repeated log entry is expected behaviour.

So I understand from this that it's not a good idea to buy a Sandisk USB flashdrive to use with unRAID. But if I already have a Sandisk flashdrive and try it with unRAID and am able to license and boot unRAID with it, am I OK? (I have an unused unRAID key and a few Sandisk flashdrives sitting around, so this is not purely hypothetical.) Or is there still a risk that there will be a licensing issue down the road? And if I try to license the flashdrive and it fails to register or boot, does this invalidate my key?

Upgraded to the latest FCP (2022.01.16), and got an error message "Docker application Docker application binhex-rtorrentvpn has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option". So I went to the settings for binhex-rtorrentvpn and fixed that, but after running Rescan under FCP I get the same message. Not sure what I should be doing. Also, haven't changed the docker app settings for a while, so not sure why this error is being picked up now - perhaps it's a new check? [Edit: My bad. Forgot that I had two volumes mounted, and had only fixed one of them. After fixing the other one it all looks good now.]

Thanks. I had already done some Googling and couldn't find anything that explains enough down at my level. Bottom line is: will there be any problems with 6.10 if I just leave things as they are?

"Use SSL/TLS" was set to "Auto". "Local TLD" setting was indeed "local". I followed the instructions, but I end up with an unsecure connection to the server. In Chrome I get a warning "This server could not prove that it is tower.local; its security certificate is not trusted by your computer's operating system. This may be caused by a misconfiguration or an attacker intercepting your connection." If I look at the Certificate I see this: "This CA Root certificate is not trusted. To enable trust, install this certificate in the Trusted Root Certification Authorities store." I realise that actually in the past I always had an insecure connection (I don't access the Web GUI other than from the local network). If I set "Use SSL/TLS" back to "Auto" I don't get a warning in the browser - but it's still an insecure connection. Just didn't think about it at the time. Sorry if it's not quite on-topic, but how do I set up a secure connection? I can't provision the Certificate as I get a "DNS rebinding protection enabled" error. I'm running the Pi-hole container, so I wonder if there's something I need to do there.

I'm on FCP 2022.01.06 and I started getting this error message labelled "Invalid Certificate 1": "Your Tower_unraid_bundle.pem certificate is for 'Tower' but your system's hostname is 'Tower.local'. Either adjust the system name and local TLD to match the certificate, or get a certificate that matches your settings." I haven't received this error before and haven't done anything with certificates for years, so I suspect this is the result of a new check that FCP is doing. Should I be doing something to fix this, and if so what? I don't know much about certificates and don't want to bork the system.

@Trozmagon How long was this shorter cable? I assume you mean the SFF-8088 to SFF-8088 external cable?

I recently started using the plug-in again and had the warning re "Cannot start session..." I'm also on 6.9.2. Here's a screenshot: I thought that with these settings my parity check would start early this morning (17th) at 1 am and pause at 9 am, but although it did start, it's now around 12 noon here and it's still running. Not sure if this is a result of the warning or an incorrect setting.

Just saw this post. No problems with the RM650x. In fact, I got another one for my then new PC build and one for my daughter's PC a few years ago, and all three run fine. (Also meant that I got to use the unused cables for my unRAID server 😉.)

I'm getting lots of entries in the access.log file: nnn.nnn.n.nnn - admin [02/May/2021:23:24:56 +0800] "POST /plugins/httprpc/action.php HTTP/1.1" 200 892 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" nnn.nnn.n.nnn - admin [02/May/2021:23:24:56 +0800] "POST /plugins/httprpc/action.php HTTP/1.1" 200 55 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" nnn.nnn.n.nnn - admin [02/May/2021:23:24:56 +0800] "GET /plugins/cpuload/action.php?_=1619845697880 HTTP/1.1" 200 14 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" nnn.nnn.n.nnn - admin [02/May/2021:23:24:58 +0800] "GET /plugins/diskspace/action.php?_=1619845697881 HTTP/1.1" 200 41 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" nnn.nnn.n.nnn - admin [02/May/2021:23:25:00 +0800] "POST /plugins/httprpc/action.php HTTP/1.1" 200 815 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" nnn.nnn.n.nnn - admin [02/May/2021:23:25:00 +0800] "POST /plugins/httprpc/action.php HTTP/1.1" 200 55 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" nnn.nnn.n.nnn - admin [02/May/2021:23:25:00 +0800] "GET /plugins/cpuload/action.php?_=1619845697882 HTTP/1.1" 200 14 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" nnn.nnn.n.nnn - admin [02/May/2021:23:25:04 +0800] "POST /plugins/httprpc/action.php HTTP/1.1" 200 704 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" nnn.nnn.n.nnn - admin [02/May/2021:23:25:04 +0800] "POST /plugins/httprpc/action.php HTTP/1.1" 200 55 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" nnn.nnn.n.nnn - admin [02/May/2021:23:25:04 +0800] "GET /plugins/cpuload/action.php?_=1619845697883 HTTP/1.1" 200 14 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" nnn.nnn.n.nnn - admin [02/May/2021:23:25:08 +0800] "POST /plugins/httprpc/action.php HTTP/1.1" 200 838 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" nnn.nnn.n.nnn - admin [02/May/2021:23:25:08 +0800] "POST /plugins/httprpc/action.php HTTP/1.1" 200 55 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" nnn.nnn.n.nnn - admin [02/May/2021:23:25:08 +0800] "GET /plugins/cpuload/action.php?_=1619845697884 HTTP/1.1" 200 14 "http://nnn.nnn.n.nn:9080/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36" This gets repeated constantly and I fill up a 10MB log file roughly every day. Is there something wrong with my setup or can I do something to fix this?

Thanks for pointing out how port-forwarding will be done by PIA in future. I too will be in the same boat - and looking for suggestions for an alternative VPN.

Thanks for the quick replies. OK, I might just change the SSD - or is there a chance it's a SATA cable problem?

Darn. Does this mean I should run memtest? I have ECC RAM, and I've come across a post (by @johnnie.black!) that says memtest doesn't really help. I have a Supermicro X10SDV-TLN4F, which has IPMI.

So in the end I changed the BTRFS cache pool to a single SSD (also BTRFS), re-created everything and was fine for a few months. Unfortunately today I got error messages from the Fix Common Problems plug-in: A) unable to write to cache and B) unable to write to Docker Image. I'm assuming that B is a consequence of A, but anyway I've attached diagnostics. Looking at the GUI, Docker is 34% full and the 1 TB cache drive, a SanDisk SSD, has about 20% free space. But looking at the log for the cache drive, I get a large repeating list of entries like this: Jul 6 18:36:57 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 432263856128 wanted 2473752 found 2472968 Jul 6 18:36:57 Tower kernel: BTRFS info (device sdd1): no csum found for inode 39100 start 3954470912 Jul 6 18:36:57 Tower kernel: BTRFS warning (device sdd1): csum failed root 5 ino 39100 off 3954470912 csum 0x86885e78 expected csum 0x00000000 mirror 1 Jul 6 18:36:58 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 432263856128 wanted 2473752 found 2472968 Jul 6 18:36:58 Tower kernel: BTRFS info (device sdd1): no csum found for inode 39100 start 3954470912 Jul 6 18:36:58 Tower kernel: BTRFS warning (device sdd1): csum failed root 5 ino 39100 off 3954470912 csum 0x86885e78 expected csum 0x00000000 mirror 1 Jul 6 18:36:59 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 432263856128 wanted 2473752 found 2472968 Jul 6 18:36:59 Tower kernel: BTRFS info (device sdd1): no csum found for inode 39100 start 3954470912 Jul 6 18:36:59 Tower kernel: BTRFS warning (device sdd1): csum failed root 5 ino 39100 off 3954470912 csum 0x86885e78 expected csum 0x00000000 mirror 1 Jul 6 18:36:59 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 432263856128 wanted 2473752 found 2472968 Jul 6 18:36:59 Tower kernel: BTRFS info (device sdd1): no csum found for inode 39100 start 3954470912 Jul 6 18:36:59 Tower kernel: BTRFS warning (device sdd1): csum failed root 5 ino 39100 off 3954470912 csum 0x86885e78 expected csum 0x00000000 mirror 1 Jul 6 18:37:00 Tower kernel: BTRFS error (device sdd1): parent transid verify failed on 432263856128 wanted 2473752 found 2472968 Should I replace the SSD or is there something I can do with BTRFS to try to fix any errors? tower-diagnostics-20200706-1928.zip

My APC UPS died a while ago and I'm only now getting round to replacing it. Probably it's just the battery, but there's not much information available from APC. I used to have my unRAID box, a Synology 4-bay box and my Win 10 PC running off it. In truth, it might have been too much for the APC (650VA, 390W). But since I have to replace something anyway, I was wondering whether it's better to have one UPS per device or one big(ger) UPS. I only need the UPS to enable a clean shutdown; our power doesn't go out often, but a few times a year it goes out when there's lightning. I'm thinking that one UPS per device is probably the way to go because: - it's cheaper, or at least in the same ballpark as having one big device - not risking a single point of failure - that big device will probably weigh a ton - easier to control the shutdowns (no need for software to link to a master device) - takes up a bit more space, but power-cable wise less messy when devices are not close to each other, as in my case. Any thoughts about this?

Came across this issue in reddit, and after doing a bit of reading in this thread and elsewhere on the forum I'm quite concerned. BUT I don't know how to check how badly - if at all - I'm affected. So far what I've done is installed iotop and libffi from the Nerd Tools plug-in and I've run iotop -oa, but I don't know how to interpret the results. loop2 does seem to be writing more than anything else, but how do I know which disk it's writing to? Does it write only to the cache disk? Could someone help out by posting what commands a casual user could try to see what's happening, and how to interpret the results?

The UD is 500GB, and it's likely to be too small, especially taking into account other stuff I want to put on it.

Yes, it's a downloads share for torrents. I did try using cache-prefer, but then of course some files did, correctly, go to the array. But I didn't like keeping the array disk spinning for reads. What I'd like to do is download to my unassigned device (SSD) and then manually move things I want to seed longer back to the cache drive. But I can't find any way of doing this in the docker I use (rtorrentvpn).

I'm trying to look at what's going wrong on my server, and previously enabled the local syslog server, writing to my cache disk as outlined here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-781601. (It's in the FAQ for unRAID v6 topic.) The problem is that my cache drive might be part of the problem, so I'd like to avoid writing to it. Is there a way of writing the local syslog folder to an unassigned device? I have an unassigned SSD which I could use. When I try to select a local syslog folder through the GUI, I only get a choice of shared folders.

Now looking at Fix Problems, I see errors: Unable to write to cache (Drive mounted read-only or completely full.) and Unable to write to Docker Image (Docker Image either full or corrupted.). According to Dashboard, doesn't look like cache is full (90% utilisation - about 100 GB fee). This is what I get (now) when I click Container Size on the Docker page in the GUI. Name Container Writable Log --------------------------------------------------------------------- calibre 1.48 GB 366 MB 64.4 kB binhex-rtorrentvpn 1.09 GB -1 B 151 kB plex 723 MB 301 MB 6.26 kB CrashPlanPRO 454 MB -1 B 44.9 kB nextcloud 354 MB -1 B 4.89 kB mariadb 351 MB -1 B 9.62 kB pihole 289 MB -1 B 10.2 kB letsencrypt 281 MB -1 B 10.1 kB QDirStat 210 MB -1 B 19.4 kB duckdns 20.4 MB 9.09 kB 5.18 kB

Took a quick look at the logs in the above diagnostics and they seem to have omitted docker.log.1. So I've attached it here after editing out many similar lines. (Think file size was too big to upload.) Plex container ID is 8138acb243f3 Pihole container ID is 358107cb7f64 These two seem to come up in the logs. docker.log.1.txt

I've re-created the docker image and all seemed fine. But this morning the log usage on the Dashboard jumped from 1% to 30% when I refreshed the browser. I did reinstall Plex yesterday, and prior to that the log was at 1% of memory (I have 31.4 GiB of usable RAM). Unfortunately it seems that the Dashboard doesn't necessarily update the log until you refresh the browser, so it's possible that the log size was higher than 1% earlier. Is Log size on the Dashboard just the syslog or also docker log? Because docker log is at 36MB, syslog at only around 1MB. Diagnostics are attached. tower-diagnostics-20200427-0949.zip

Can't say I did check the settings. But I'm sure the docker image wasn't anywhere near full when I looked at the dashboard. I remember thinking that there was significantly more free space since I'd left out a number of dockers when I did the reinstall.

OK, I can do that, but I already re-created the docker image when I reinstalled the dockers on the re-formatted cache drive. Any way of reducing the chance of this corruption happening again? Or could it be that there's some problem with the appdata files that I backed up and used to reinstall the dockers that is causing this?