John_M
-
Posts
4727 -
Joined
-
Last visited
-
Days Won
12
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by John_M
-
Check the value of Settings -> Notification Settings -> Plugins update notification. I have it set to Check once a day. You probably have it set to Never check.
-
Thanks for that. The document suggests, as an alternative to disabling IOMMU, and gives instructions on how to do it. Maybe someone with affected hardware and who is prepared to take a risk could give that a try?
-
Watching from the sideline because my Gen8 still has its original non VTd-capable Celeron processor, but wouldn't a better solution be to disable VT-d automatically via syslinux.cfg when the problematic configuration is detected instead of disabling the NIC? It would still take some users by surprise, of course, but at least they'd still be able to connect to their servers.
-
Unraid 6.10 has built-in support for splitting the scheduled parity check into multiple shorter periods. See Settings -> Scheduler
-
The first step to diagnosing is to try a different browser. In fact, try as many browsers as you can. Are there any nginx error messages in the server's syslog? Post your diagnostics whenever you make a bug report. -
6.10 update, Firefox browser is not displaying dynamix non tabbed view correctly
John_M commented on 2Rock's report in Stable Releases
Those plugins shouldn't be a problem if they are all up to date but you can test by booting into safe mode, which ensures that no plugins are loaded. -
It's Disk Utility, in the /Applications/Utilities folder.
-
I looked for documentation about the about the scrub and balance schedulers that were recently introduced for btrfs volumes. What kind of scrub is done on a schedule? Is it a correcting one or a read-only one, given that there's a choice when a scrub is run manually? What kind of balance is done on a schedule? Is it a full one or one based on partially filled extents? Does the presence of the Block group usage parameter imply that it's the latter?
-
It looks like you have a problem with your "dockers" pool (corrupt 515432): Apr 25 11:52:19 Unraid1 kernel: BTRFS info (device sdm1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 515432, gen 4
-
Maybe something in this thread might help: https://askubuntu.com/questions/863150/pcie-bus-error-severity-corrected-type-physical-layer-id-00e5receiver-id
-
That looks like a hardware problem to me.
-
Can you enter the username (it can only be 'root') and password manually? Browsers store username/password combinations against the URL of the page. If you're using https the URL has changed from https://<hash>.unraid.net to https://<local ip address with dashes>.<hash>.myunraid.net with this update.
-
A Samba bug? See here (from page 7 of this thread): https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6100-rc2-available-r1565/page/7/?tab=comments#comment-16681
-
Nov 14 16:23:38 NIKOS-TOWER kernel: amdgpu 0000:0a:00.0: amdgpu: amdgpu: finishing device. According to the syslog snippet you posted you are loading the amdgpu driver which will prevent the card being passed through to a VM. Either stop loading the amdgpu driver or, if you need it for another AMD GPU, bind your 5700XT card to the VirtIO driver on the Tools -> System Devices page. As mentioned in the release notes, at the top of this page, which would explain the different behaviour.
-
Is this what you're looking for?
-
My upgrade from 6.9.2 to 6.10.0-rc2 was uneventful, thank you. Shouldn't that say 'Network traffic' instead of 'General Info'?
-
It looks like you have the Turbo-write plugin installed. I believe it's responding to the spin-ups and spin-downs, rather than causing them, but it might be worth disabling it temporarily just in case.
-
I'm not sure how I was meant to know that.
-
Some HBAs don't support trimming SSDs. Your diagnostics would show how yours is connected.
-
Corrupt file systems aren't restricted to old devices. Run it again, without the -n option.
-
You're trying to rebuild Disk 2 but your Parity disk is disabled (see the red cross next to it in your screenshot) so the array can't start because there are too many missing disks. Do you still have your old Disk 2? Is it completely dead? Unfortunately, your new Disk 2 isn't particularly healthy, either. Do you have backups of your important data?
-
Have you run a file system check on the cache, in case there is corruption?
-
It seems to be re-starting every minute or so. You said that if you stop that particular container the error messages continue? Try setting it not to auto-start, then reboot, start the array, wait for a while with it not running and if the error messages do indeed continue then post new diagnostics. You might have another problem that's hidden in all the noise. I have no experience of Transmission_VPN so you should check its support thread to see if there are any known issues and then check its configuration and/or re-install it.
-
Alternatively, you could set up a Linux VM, running your favourite distribution and install whatever packages you want.
-
The problem container has ID 8a49c72ca63f2abb0a1377cb1d795dac4f10e3167cd3582351deaa48aa277d99. If you go to the Docker page of the GUI and turn on Advanced mode the first 12 hexadecimal digits of the ID of each container are displayed. Does that help you to locate it?
