at0m

This plugin looks like it's only updating Dockers I pulled from the community 'store' and not ones I have running from Compose files using Compose Manager, even though I get update notifications saying an update is available for those Dockers. Is there a particular reason why this is the case? I have update Dockers set to yes in the plugin.

So I've had my server running for quite a while, and ended up replacing my router last week. Not sure if that's relevant, because DHCP is turned off. Anyways, today I had a short power outage. I've got a Synology DS1019+ connected via usb to a UPS and acting as a network host to shut down the Unraid server. I've tested this and know that it works right. Today, it didn't all come back when power came on; only the DS1019+ did. When I got home and tried to power up the server, it seemed like it booted, then beeped twice and shut off, which is what it typically does if the power goes out. I've tried restarting it several times, and it does the same thing every time. This shouldn't be an issue, because there's a USB ethernet adapter and a direct line between the two, which isn't even on my network. It's a different subnet, static IPs, and those IPs haven't changed. I pulled the boot drive to look at logfiles and I can't seem to find the syslog server log file. Looking at the rsyslog.cfg, it looks like below. I thought i had the mirror to flash option turned on, but I don't see anything in the logs directory other than some config dumps from months ago. local_server="1" server_protocol="udp" server_port="514" log_rotation="1" log_size="100M" log_files="4" remote_server="192.168.1.210" remote_protocol="udp" remote_port="514" syslog_flash="" server_folder="/mnt/user/appdata" Is there a change I can make to this config file to make sure the copy to flash is on so I can try to start it up again and see what it tells me about why it's shutting down?

I've found several plugins for various systems using the same C code and even later versions of the driver from Realtek. Many have many more devices supported under the same drivers because they have the same chipsets, they just need their IDs added to the array for whichever chipset driver is used for them. It would be nice if unraid's plugin was upgraded to support those newer devices.

I know the GPU Stats plugin is configured right. As I said, since the data matches, I came here. Nothing was using my iGPU though, so maybe that was causing it. I'll pursue that later. If you look at the links I posted, it shows the chipset by where the ID was added to the file. Mine reports the same model number, v2.0R, which is what that patch was meant to add support for. You should literally be able to add that line to the driver the plugin uses. It's added to this table: /* table of devices that work with this driver */ static const struct usb_device_id rtl8152_table[] = { on the unraid box, lsusb reports the below, which matches the commit, as previously stated Bus 002 Device 005: ID 20f4:e02c TRENDnet TUC-ET2G(v2.0R) Was purchased from here: https://www.amazon.com/TRENDnet-Gigabit-Ethernet-TUC-ET2G-Chromebook/dp/B07RBMTVYF Mfg website here, although the datasheet doesn't call out the chipset: https://www.trendnet.com/support/TUC-ET2G-v2

So I've got two issues: When using Intel-GPU-Top and the GPU statistics plugins, I'm running an i5-6500T, but it doesn't show in the dropdown in the statistics plugin (it only shows one option named '99: HD - 0000-00-000-000000' and the only statistic that appears to be updating on the dashboard are the IMC Bus Utilization (changes quite a bit), and the Interrupts/sec (which is usually 2 or 4). Everything else is zeroes. When I run the CLI command, I get the same thing (which is why I'm posting in this support thread instead of the GPU Statistics one - the numbers match, they're just mostly all zeroes). Second, when using the RTL8152/3/4/6 USB Drivers plugin, my adapter isn't showing up in the list. I've got a different USB3 Gigabit one that worked OOB on another port, but the 2.5GBit one I just installed doesn't show up. I'm not sure, but when trying to research why the ones I just bought weren't working on either my unRAID or Synology, I did find a comment in release notes about needing to update the package so the Synology version of the driver could support a new hardware revision of the adapter I'm using (TUC-ET2G). Is there a possibility this plugin needs a similar update? The relevant release is here: https://github.com/bb-qq/r8152/releases/tag/2.15.0-9 and the relevant commit for that release is here: https://github.com/bb-qq/r8152/commit/9015a72f773d8af17261a150ca38627bc9ab1350 I have not yet applied the change to my go file to enable 2.5GBit, because I wanted to see if I could get the adapter working at all first before trying to get it to run full speed. Diagnostics attached. tower-diagnostics-20230308-2251.zip

And should have a working search function, which is something I feel you're completely missing. It needs to either find effective information, or be removed.

Did this PR get implemented? Update log on the plugin shows last updated on 2021.12.09

The warning is appreciated but they were brand new drives. Nothing on them I wanted to keep. Yeah, I think I've got it going now.

I logged out and logged back in after starting the array and found the format option at the bottom of the list near the start array button. It's a little confusing that it's not anywhere on any of the drive or array information pages.

brand new machine, brand new hardware, got it booted up and connected to the internet, configured one drive with no parity, tried to start the array, and it says its unmountable. I don't see a format option anywhere and can't find any info searching the forums with google other than a previous bug screwing up formatting drives larger than 2TB. Patch notes say that bug should be fixed, and both drives are 2TB anyways so I don't see how that might factor in. Diagnostics attached. tower-diagnostics-20230215-2242.zip

My point being the SEO on the documentation search function is garbage if the top hit is useless info. I understand this is essentially a volunteer effort (which is a little odd for paid software, but that's a different story), but my first instinct when looking at documentation is not to read the whole first page which is generally useless, I _search_. And search in this case is pointing to the wrong thing, as both OP and I found.

The top hit when you search in Documentation for 'cache' is that outdated document. It does have that disclaimer at the top, and says it links a current FAQ document, but that link 404s. So where should we find current info, again?