dbinott

it wouldn't let me type anything. I had to do a hard reboot.

I updgraded to 6.12.4 from 6.12.2 then when into maintenance mode to check a failed drive and now I can't get out of it. Stop does nothing. predator-diagnostics-20230918-1058.zip

I have GeForce GTX 1050 Ti with only 4GB. Should I bother trying to install?

Got this in my fix common problems. I think it might have to do with the macinabox not shutting down, but if someone could have a look. predator-diagnostics-20230812-0944.zip

First time ever in the years I have been using unraid. It booted back up ok and is running parity check. I know it may be too late for diagnostics after the fact, but I am attaching it anyway to see if anyone can help figure out what caused it. I just recently updated to the latest unraid. Like last week, maybe. predator-diagnostics-20230628-1726.zip

Ok, teach a man non-gender specific person to fish.... I ended up deleting /boot/config/network.cfg and it got recreated. Got set to Bonding I guess cause it saw I had 2 nics, but only want/using the one. So turned that off, put static addresses back, rebooted and bob's your uncle!

I changed my nic, added it as eth1, then swapped them around and gave same old static ip. eth1 is disabled. I can't update anything, can't get to the apps, can't use *arr's. I tried changing DNS servers a couple of times and when I do, it locks up and locks me out and I have to reboot from command line each time. I have tried the usual DNS 8.8.8.8 8.8.4.4 1.1.1.1 9.9.9.9 4.2.2.4 root@Predator:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. From 10.0.0.35 icmp_seq=1 Destination Host Unreachable From 10.0.0.35 icmp_seq=2 Destination Host Unreachable From 10.0.0.35 icmp_seq=3 Destination Host Unreachable From 10.0.0.35 icmp_seq=4 Destination Host Unreachable From 10.0.0.35 icmp_seq=5 Destination Host Unreachable From 10.0.0.35 icmp_seq=6 Destination Host Unreachable ^C --- 8.8.8.8 ping statistics --- 8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7159ms pipe 3 root@Predator:~# ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. From 10.0.0.35 icmp_seq=1 Destination Host Unreachable From 10.0.0.35 icmp_seq=2 Destination Host Unreachable From 10.0.0.35 icmp_seq=3 Destination Host Unreachable From 10.0.0.35 icmp_seq=4 Destination Host Unreachable ^C Help! predator-diagnostics-20230211-1738.zip

You are likely correct. I have pools for nzbget, Plex transcode others. So having said that, how should they be structured so this doesn't happen? if my nzbget is /mnt/nzbget/ should I add a folder to this and do the work there as opposed to doing it at the top level? Thanks!

Just happened upon this. I see share cfg's for shares I don't have and are named after some downloaded media. Any idea what's going on here? Obviously I must have something configured incorrectly? predator-diagnostics-20211129-2313.zip

So I had a fat finger typo in the plexpass docker console. Are these the correct files/folders that should appear? I have the config in a separate pool.

ok, I think I get it. Just not sure why my last pool was not created like the others, but I will figure that out. thanks.

ok, but doesn't explain why the files I put in /mnt/uhd are getting put in /mnt/user does it?

I added a couple pools after I get 6.9.0. They mapped to /mnt/user/Plex Media server and /mnt/user/nzbget and all is good. I added a new pool today, can't remember if it was before or after 6.9.1, called uhd, but it mapped to /mnt/uhd and everything I put on it is getting added to /mnt/user. Also shows up on /mnt/uhd, but if I delete from /mnt/usr, it's also gone from /mnt/uhd Not sure if a bug, or I screwed something up? diagnostics attached. /media here is mapped to /mnt predator-diagnostics-20210310-1927.zip

Hope you can help with mine as well? I thought this would be working in 6.9.0? M/B: ASRock B450 Pro4 Version - BIOS: American Megatrends Inc. Version P4.10. Dated: 03/05/2020 CPU: AMD Ryzen 5 3600 6-Core @ 3600 MHz sensors nct6779-isa-0290 Adapter: ISA adapter Vcore: 0.00 V (min = +0.00 V, max = +1.74 V) in1: 0.00 V (min = +0.00 V, max = +0.00 V) AVCC: 0.00 V (min = +0.00 V, max = +0.00 V) +3.3V: 0.00 V (min = +0.00 V, max = +0.00 V) in4: 0.00 V (min = +0.00 V, max = +0.00 V) in5: 0.00 V (min = +0.00 V, max = +0.00 V) in6: 0.00 V (min = +0.00 V, max = +0.00 V) 3VSB: 0.00 V (min = +0.00 V, max = +0.00 V) Vbat: 0.00 V (min = +0.00 V, max = +0.00 V) in9: 0.00 V (min = +0.00 V, max = +0.00 V) in10: 0.00 V (min = +0.00 V, max = +0.00 V) in11: 0.00 V (min = +0.00 V, max = +0.00 V) in12: 0.00 V (min = +0.00 V, max = +0.00 V) in13: 0.00 V (min = +0.00 V, max = +0.00 V) in14: 0.00 V (min = +0.00 V, max = +0.00 V) Array Fan: 2872 RPM (min = 0 RPM) Array Fan: 2445 RPM (min = 0 RPM) Array Fan: 2106 RPM (min = 0 RPM) Array Fan: 3020 RPM (min = 0 RPM) CPU Temp: +52.5°C intrusion0: ALARM intrusion1: ALARM beep_enable: disabled sensors-detect # sensors-detect version 3.6.0 # Board: ASRock B450 Pro4 # Kernel: 5.10.19-Unraid x86_64 # Processor: AMD Ryzen 5 3600 6-Core Processor (23/113/0) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... Success! (driver `k10temp') AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found `Nuvoton NCT5532D/NCT6779D Super IO Sensors' Success! (address 0x290, driver `nct6775') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): YES Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus Module i2c-dev loaded successfully. Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0) Do you want to scan it? (yes/NO/selectively): yes Client found at address 0x4f Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP421'... No Probing for `Texas Instruments TMP422'... No Probing for `Texas Instruments TMP435'... No Probing for `Texas Instruments TMP441'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1) Do you want to scan it? (yes/NO/selectively): yes Next adapter: SMBus PIIX4 adapter port 1 at 0b20 (i2c-2) Do you want to scan it? (yes/NO/selectively): yes Next adapter: NVIDIA i2c adapter 4 at a:00.0 (i2c-3) Do you want to scan it? (yes/NO/selectively): yes Adapter cannot be probed, skipping. Next adapter: NVIDIA i2c adapter 6 at a:00.0 (i2c-4) Do you want to scan it? (yes/NO/selectively): yes Adapter cannot be probed, skipping. Next adapter: NVIDIA i2c adapter 7 at a:00.0 (i2c-5) Do you want to scan it? (yes/NO/selectively): yes Adapter cannot be probed, skipping. Next adapter: NVIDIA i2c adapter 8 at a:00.0 (i2c-6) Do you want to scan it? (yes/NO/selectively): yes Adapter cannot be probed, skipping. Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `k10temp': * Chip `AMD Family 17h thermal sensors' (confidence: 9) Driver `nct6775': * ISA bus, address 0x290 Chip `Nuvoton NCT5532D/NCT6779D Super IO Sensors' (confidence: 9)

Wondering if anyone can help me figure out I am not getting data for some metrics? At one point I had the library data and stream data. I recently moved the server to a different location with different network, but I believe I changed IP addresses where applicable. Not sure why negative numbers in growth? Why some data about library but not others? I have disk data, but can't get overview?

Just updated to 6.9.0 and thought this was going to be resolved? Still unable view all my sensors. 😞

If radarr itself is not reporting anything in the queue, then it is most likely an issue with the other app showing incorrect data. Did you ask them? Go to their github page.

Heimdall issue, not radarr. Did you try reloading the page or restarting heimdall?

Make a backup first. Type "delete * from blacklist_table_name"

Imo, this version was not ready for primetime. But too late. @tgggd86 I bet if you delete all your blacklist it will work. The migration is failing on it. But you would have to start v2 to do that, or edit the sqlite db directly if you know how.

Are you using SWAG for your webserver/reverse proxy? You will find all that info in the appdata folder for swag.

This worked for me for not being able to add movies remotely, whether it works for you, I don't know. But if it does, great. Link to discord post https://discord.com/channels/354974912613449730/506925392603512839/785253299129286666 In the text below where it says "got the new files", that was in reference to this https://discord.com/channels/354974912613449730/506925392603512839/785242013289283624 Text from post map $http_upgrade $connection_upgrade { default upgrade; '' close; }

Guys, this happened to me and I figured it out. There are some config issues with nginx. I posted in the discord channel. I will post here when I get back to my computer. Sent from my HD1910 using Tapatalk

Yes, I can do that.

ok, so when the cache drive was disconnected, I started to reinstall, that stuff got put on the array. I reconnected the cache drive that has all the good configs on it. I just didn't want the array stuff overwriting the cache drive stuff in case it was not correct. Not a big deal tho.