cybersteel8
-
Posts
30 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by cybersteel8
-
-
I am having this problem as well, after Steam successfully using the LANCache it eventually comes up with "Forgetting cache type LANCache on host due to chunk timeout" and refuses to use the cache for the rest of the download.
I hope we can get some help with this!
-
2 hours ago, itimpi said:
At one level that is correct, but if you have backups it would normally be MUCH quicker to simply restore the files identified by the scrub as being corrupt.
Ah, so a btrfs scrub actually documents the names of the files that are corrupt? That's incredibly useful to know, thanks!
-
On 5/30/2022 at 5:01 PM, JorgeB said:
If no checksum errors were found you can have confidence that the data is OK, so just correct parity.
Thanks. Due to the following test, I have now run a correcting parity check, and it corrected the 5 errors.
On 5/30/2022 at 9:39 PM, trurl said:Just to make sure there isn't something else causing sync errors, you should run a correcting check, followed by a non-correcting check, all without rebooting.
I have done this and the results seem successful. After the correcting check, I ran a non-correcting check immediately without rebooting at all. There were no errors detected in the non-correcting check.
Would the diagnostics still be useful, considering the second parity check resulted in no errors? I am unsure if it is safe to assume that my hardware is fault-free, but I suppose if I keep getting parity errors, diagnostics would become more useful. I think this is something I will keep an eye on, but not worry about. I'd like your opinion on this.
--
It seems the answer to my original question is that, when a non-correcting parity check results in errors, no action is taken by Unraid. A second parity check will show the same errors. The action that ought to be taken by the user is to run a btrfs scrub on all of the array drives to determine if there are any problems with the data on the drive. If the btrfs scrubs result in no errors, then the errors are on the parity drive, so a correcting parity check is appropriate. Another non-correcting parity check after correcting parity is appropriate, to ensure that parity is indeed in a valid state.
"If there are errors as a result of the scrub, then that drive should be rebuilt from parity, as the parity mismatch is from the data not the parity" - This is my assumption. I would appreciate a comment on this to know if my assumption is correct. -
3 minutes ago, trurl said:
Have you had unclean shutdown since last good parity check?
My last good parity check was a month ago, and unfortunately I have rebooted since then, as I upgraded from 6.9.2 to 6.10.1 and that requires a reboot.
It was not unclean. -
On 5/28/2022 at 3:29 PM, itimpi said:
You would have to force Unraid to rebuild a complete drive - you cannot do anything at a lower level of granularity with parity.
Much easier is restore any affected files from your backups.
I still don't know how to determine which files are affected. I don't even know which drive I would want to rebuild, if I took this approach. How do I know which files are affected?
On 5/28/2022 at 5:06 PM, JorgeB said:Run a scrub on all array drives, if no corruptions are found run a correcting check.
Thanks. I have done this on all my array drives, and no errors were found on any of them. Does this mean the error was on the parity drive and not on my data drives? Do I know this with confidence?
-
12 hours ago, JorgeB said:
using btrfs
I am using btrfs - how do I find out if the errors are in data or parity?
I understand that a correcting parity check will update parity, but what if the errors are in the data, not the parity? How would I fix the data using the parity information? -
My monthly parity check completed with 5 errors. This is in my syslog:
kernel: md: recovery thread: P incorrect, sector=1962934168 kernel: md: recovery thread: P incorrect, sector=1962934176 kernel: md: recovery thread: P incorrect, sector=1962934184 kernel: md: recovery thread: P incorrect, sector=1962934192 kernel: md: recovery thread: P incorrect, sector=1962934200 [...] kernel: md: sync done. time=82684sec kernel: md: recovery thread: exit status: 0
There is no other messages in my syslog related to the parity check.I don't actually know what happens now. Unraid says there were 5 errors, but all my disks are still active, nothing's simulated or whatever.
What action did Unraid take once these errors appeared? As it was non-correcting, did nothing happen? It just reports them and that's it? Which files are these in particular - is there a way to know? Do I need to know?
I don't know what action I take once errors appear in the non-correcting parity check.
-
I successfully updated from 6.9.2 to 6.10.1
I was initially concerned when looking at the Main tab, seeing all my drives mounting one by one with 0TB, but after the Array finished starting up, everything is fine. So don't be worried if you notice this!
I really like the new dashboard graphs, and the btrfs schedule-able features. Very exciting!-
1
-
-
Hi all, I am new to using the Dynamix Auto Fan Control plugin, and I would like to ask - can this plugin control multiple PWM controllers at once? I have my fans plugged into different pins on my motherboard, so they are independently controllable. Can the plugin modify the fan speed of all of these fans, or only one controller?
-
4 hours ago, trurl said:
Unclean shutdown parity check is non-correcting
Ah, so the answer to my first question is that it is running as if it was unticked, which is the behaviour I want. So there's is nothing I need to change! Thank you!
-
Hello all! This is quite a convenient thread, though I didn't find the answer to my question so I hope I'm not asking the same thing as somebody else.
I experienced an unclean shutdown due to a power outage, and when the power returned and the server came back online, it mounted the disks and began a parity check automatically (as expected).
I would like to ask - when starting a parity check manually, the "write corrections to parity" is ticked by default. When the parity check starts automatically, is it starting with this ticked or unticked? How do I found out and control this behaviour?
Furthermore, I am under the impression that unless I want to correct the parity data, I should untick this option when doing parity checks. This is so that any corrupt data on the data disks can be fixed using the parity data. As this is likely when there is an unexpected power outage, I believe that it would be proper practice to perform the automatic parity check without writing corrections to parity. Is my assessment correct?
Thank you all!
-
8 hours ago, arturovf said:
Well yes disabling HDR tone mapping is a workaround, but then you can't do several 4k to sdr transcodes because cpu can't cope it
Indeed. Though, I think I need to point out that this is a Plex issue, not an Unraid one. This thread was started and bumped because of Unraid's support for this CPU. It supports it and hardware acceleration is available for Plex. -
1 hour ago, arturovf said:
No, support it's not perfect yet, 4k HDR to SDR tone mapping is not working well (green artifacts).
I am indeed having trouble with HDR to SDR tone mapping (the transcoder is failing completely), but QuickSync is indeed working when doing SDR content, both 4K and 1080p. The gpu driver is being forwarded to Plex and Plex's transcoder is indeed hardware accelerated.
If you experience any problems with HDR transcoding, turn off HDR Tone Mapping in your Plex Settings > Transcoder section. -
On 7/31/2021 at 8:19 PM, eyeonly said:
Hi everyone,
I am planning to upgrade my current unraid server from i5 6500 to 11th or 10th generation.
May i have an update on this topic? Can 11th Intel cpu, i5 11400 iGPU work well on unraid?
QuiackSync is very imporant on my Plex
Hey mate, yeah, I got QuickSync to work perfectly fine with my i5-11500
I did need to install the intel_gpu_top app from the Community Applications plugin to get QuickSync to work.I also had to pass the /dev/dri directory to the Plex docker container as well. Check out the instructions regarding that docker path variable here:
-
I am curious about the benefit of setting the system share on Cache Prefer.
I use the tool that backs up my appdata onto the array (as it is also cache prefer) but I don't have such functionality for the system share, so it currently only exists on the single cache disk I have.
I would like to know if there is any benefit in keeping this share on the cache at all times - in other words, is the docker.img file that is inside it constantly in use while docker containers are running? I only restart my docker containers when there is an update to be applied, and I assume that is when the docker.img file is used. But otherwise, is the file in use at all?
If it isn't, then there's no point keeping it on the cache, right?
-
So it sounds like you've got your external drive plugged into your Windows PC and Windows is managing a share that you've mounted on your Unraid system to copy your data to? Have I understood this correctly?
This would involve troubleshooting Windows's share setup, which is a little fiddly. I'd first use the Unraid Terminal to check the directory's permissions on the external drive share to ensure that Unraid is able to read and write to it. You can test it by creating a dummy text file in that share from the Unraid Terminal just to be sure.You could do things such as:
ls -la /mnt/remotes/192.168.0.101_F/docs/scans/
That will show you the permissions of the directory indicated by the "." folder. Also any folders/files underneath that may have changed permissions and are not updatable by Unraid.
touch /mnt/remotes/192.168.0.101_F/docs/scans/testfile.txt
This will just create an empty text file in the share to ensure Unraid can write to it, at least, as the Unraid user you're logged into anyway.
That'd be my first sanity check to ensure the share is read/write -able. Reply with how those tests go, let's start at the simple steps. -
23 hours ago, wgstarks said:
The default would be to have appdata on cache. My appdata path is /mnt/cache/appdata/plexmediaserver/
I am in the process of getting a cache disk setup to move it off the array and onto cache, but currently it is on the array.
12 hours ago, Squid said:If the appdata share is stored on a different server than where the container is running from, then yes that is a weird setup (although nothing wrong with it per se)
Ah, no that's certainly not the case. On a fresh Unraid installation, there is a small selection of precreated shares - appdata, domains, isos, and system. The appdata share, when there is no cache disk in the system, seems to just save onto the array like any old share. That's what I have currently setup. This share, and all the shares I've created, have been created as SMB by default (which has been useful as I've exposed them to my network temporarily for some data loading via my Windows machine).
The way I'm describing it doesn't sound like there's anything weird with my setup, which is a relief.
The impression I am getting is that the Streams column is just the number of files currently active, and apparently certain docker containers keep dozens of files active at a time. Plex has about 69 (nice) streams active at a time. I consider that quite a lot, but I am assuming that is a normal number.Is it possible to view each individual file the Plex application is currently streaming from the appdata share?
-
Oh wow, right, so Plex has opened about 70 files in the appdata?
I don't believe I am using NFS - in the Settings > NFS is disabled. Is it weird that my containers are using so many streams each?
Is it also weird that I have my appdata share on SMB? I thought that was the correct way to point the container's config or data directory to it. -
Hello!
I have a question out of curiosity. On the Dashboard, I see my SMB shares, and there is a column called Streams. I'm wondering, what is this column exactly?
I have only 2 docker containers running at the moment, but I have 152 streams to the appdata directory. Plex is like 70 streams by itself.
What are streams and why are there so many? Are these all active I/0 to the share, implying constant disk access?
I'd love a technical explanation! Thank you for attempting to satiate my curiosity
-
I know your post is over 3 years old, but I think I know the answer
In htop I think this is the script that is executing, "webGui/scripts/share_size" - you could kill this process to stop it computing?
-
1
-
-
https://forums.zoneminder.com/viewtopic.php?f=41&t=30926
@dlandon It appears this is a reproducable issue in the zoneminder.unraid docker image - I came across that forum post when trying to find out why my container refused to start up. I think it might be necessary to restart the mysql service automatically during a fresh install? Not sure what's going on here, still quite new to all this. -
Thanks, that's very helpful.
I have a follow-up question:
I see that Unraid has a Parity Check Scheduler built-in but there isn't one for a Read Check.
Is it safe to assume that when a Parity Check runs, it is also implicitly doing a read check at the same time? -
11 hours ago, JorgeB said:
Read check like the name implies only reads the data disks, it will report any read errors.
Ah, so it functions kind of like a health check of the drive to see if all the sectors are still readable?
Thanks! -
I have migrated all my data to my new array, and I am yet to add parity. I am considering running a "Read check" on my array before adding the parity.
Is there any value in this? I understand that once I have my parity drives installed, a "Parity check" will be checking the data against the parity data, but without parity, does a "Read check" do anything? I am specifically referring to the button at the bottom of the Main page, where you can also see options like Reboot/Shutdown/Clear Stats and the Start/Stop array buttons etc.
So, is there a difference between a Parity Check and a Read Check? Without parity, does a Read Check do anything useful?
Thanks for your information. I couldn't find anything in the manual regarding this, unfortunately.
[Support] ich777 - Gameserver Dockers
in Docker Containers
Posted
Hey @ich777 There is some lowlevel updates to how docker containers for Counter Strike Global Offensive are built, and I have found some information from Valve about this. It may be relevant for your CSGO image, as well as maybe some other Valve game images.
https://www.reddit.com/r/GlobalOffensive/comments/10szs27/additional_details_for_linux_community_server/
https://gitlab.steamos.cloud/steamrt/sniper/platform/-/tree/steamrt/sniper
I am still able to run my dedicated server using your image (had to update sourcemod though) but I wonder if there's compatibility concerns for the future.