subagon

ljm42, Sorry if I wasn't clear. I'd already provisioned all my servers with myunraid.net certificates. My suggestion is a change to the GUI interface. From the first screen/page of the Connect plugin I see this (thereare two other servers but no need to show them); In order to access the Main management screen I must click on "Manage" above. Next I see this; Clicking on any of the above 3 link takes me to the Main management screen. My suggeestion was to add a likk somewhere on the first screen of the Connect plugin tat would take me directly to the Main management screen of the server. Just a quicker way to get to where I want to go. Maybe make the name of the server (in my screenshot "ted") a link that directly opens a new tab of the Main management screen. Thanks for all the hard work and looking forward to updates to Connect and 6.12! Mike

I've build a new Unraid server to backup the data from my current Unraid server. I'm copying the data via a 10G network connection and I'm tranfering a bit less than 5TB/day. At this rate it will take somewhere around 30 days to conplete the backup. I was wondering if I could; put a new drive in the old server format it to XFS copy files locallly put a new drive in the NEW server add it to the array and not lose the data Rinse and repeat Once all data has been moved, rebuild the parity Is something like this possible? Edit: I know I could use unassigned devices, but I'm not sure copying the data twice would be any faster than the network copy.

itimpi, Sorry, my screenshots didn't show the array after I started it. However, after starting the array, the format button wasn't there. I was able the format the driver using unassignerd devices after I enabled Destructive Mode.

SOLVED. I installed Unassigned Devices but forgot to set Destructive Mode to "Enabled" =============== I feel like a noob... This is my second unraid server, all new. First server has been in use 7+ years. I don't remember having any issues when I built it. New install of unraid. 12 x 20TB drivers (1 for parity). I ran one cycle of preclear, no problems. I added all the drives to the array and started the array. Got the "unmountable unsupported partition layout" message next to each drive. Remembered I need to format the drives. No option anywhere I can find to format the drives. Unraid 6.11.5 Supermicro X9DRD-7LN4F 24 bay 4U This server was running unraid up until a year ago when I transfered the drives and USB flash to new hardware. Reusing it as a backup server.

Really simple request... I have 3 Unraid servers and really like the Connect Plugin dashboard. One place to get a quick look at everything and a jumping off point to each server. I'm sure we'll see move information added to this dashboard over time. For now I would like to suggest adding a link on the dashboard for each server to go directly to the management screen of each server. Currently this requires a click on "Manage" and then a click on one of the 3 links to mange the server. I use the plugin to jump to each server and a link on the dashboard would save me many clicks a day.

Thanks guys for the replies. For now I'm going to wait on any 40G NICs. Two weeks ago I bought 2 Intel X520-DA2 NICs (10G) and then I saw the 40G NICs at about the same price. I just assumed anything faster that 10G would be more than I wanted to spend (wrong). Anyway, yeaterday I received a second cable for the X520's and bonded the two interface to get a 20G point-to-point connection. I think that's good enough for what I have planned. Mike

Tom3, Thanks for taking time to reply. My use case is point-to-point (no switch). I wonder if you could explain your statement about "compatibility of the two ends". I plan to buy two identical NICs and configure them the same. I assume two identical cards would be compatible with each other. Maybe you mean there could be issues in the configuration beyond what can be configured in the unRAID GUI. Also, thanks for explaining that these cards are not a single 40G link, but rather 4x10G links aggregated. I did find this and ran it thru Google Translate. The OP lists Mellanox 40G cards in the setup and I have to assume they work. Mike

I'm building my second unRAID server as a backup to my primary unRAID server. I want to have a point to point netword connect between the two servers just for backups. The initial backup is going to talk a long time, ~100TB, and the faster connection the better. I've seen many 40G Mellanox NICs on eBay under $40 and looking for people with first hand experience with 40G. Would like a card that's reliable and doen't require additional configuration. Model number would be appreciated. TIA, Mike

I just purchased 2 Intel X520-DA2 (dual port) NICs and connected two unRAID servers directly (no switch). I'm using this connection as a secondary connection to backup my primary server. After installing the X520, it shows up in Network settings, no problems. Since you'd be using SFP+ transceivers your choice of cable is up to you. I went with a 3 meter Wiiteck SFP+ DAC copper cable for $20 on amazon (tinyurl.com/bkcercf5).

Follow up... Ordered and received a new NVMe drive today. Installed and recognized by Unraid. I guess Unraid doesn't support eMMC? Again it's not an issue for me since I was replacing it anyway.

Thanks itimpi for pointing that out. This gives me hope that a NVMe drive will work in this device with Unraid. So I guess Unraid doesn't support eMMC? Not an issue in my case since I want to replace it. I'll wait and see if someone will post with experience with this hardware. EDIT: I found this... Maybe this hardware has the same issue? Tech specs... https://support.hp.com/us-en/document/c06437903#AbT5

This is a fresh install and all I have done is set a static IP address and nothing else. Configuration: - Unraid 6.11.5 - HP t740 thin client - 16GB RAM - 2 M.2 slots - Slot #1: 32GB NVMe SSD in slot labeled "NVME" - Slot #2: empty, labeled "SATA" The 32GB drive is visible in BIOS. However, the drive is not visible on the Main page. I've read a few similar posts here and nothing matched. This thin client PC doesn't have any RAID controller I can see. It doesn't have any SATA ports, just the two M.2 slots, one NVMe and the other SATA. I only have the single 32GB NVme SSD installed. The 32GB SSD came with the PC and I would like to replace it with a larger NVMe drive, but don't want to spend $ if it won't work in this thin client. I did try installing a SATA SSD in the SATA slot and Unraid did see it, formated, etc. With both the SATA and NVMe drivces installed only the SATA drive is visible. The diagnostics file below is with only the 32GB NVMe installed. This isn't a "production" server. It's just a test box I use to test out various OS's, dockers, etc. Right now I'm using it to test a backup server for my primary Unraid server (no, this thin client will not be the backup server). Thanks, Mike tower-diagnostics-20230413-0146.zip

Same issue here and downgrading to 4.4.5-1-01 got me working again.

Thanks kuuki, this got me going again. 👍 I hope this gets fixed so I can go back to "latest" instead of a fixed version.

I updated TubeArchivist-RedisJSON yesterday and now the docker refuses to start. Here's the log output. 1:C 29 Oct 2022 00:52:35.031 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1:C 29 Oct 2022 00:52:35.031 # Redis version=6.2.7, bits=64, commit=00000000, modified=0, pid=1, just started 1:C 29 Oct 2022 00:52:35.031 # Configuration loaded 1:M 29 Oct 2022 00:52:35.031 * monotonic clock: POSIX clock_gettime 1:M 29 Oct 2022 00:52:35.032 # A key '__redis__compare_helper' was added to Lua globals which is not on the globals allow list nor listed on the deny list. 1:M 29 Oct 2022 00:52:35.032 * Running mode=standalone, port=6379. 1:M 29 Oct 2022 00:52:35.032 # Server initialized 1:M 29 Oct 2022 00:52:35.032 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. 1:M 29 Oct 2022 00:52:35.041 * <ReJSON> version: 20400 git sha: e383c08 branch: HEAD 1:M 29 Oct 2022 00:52:35.041 * <ReJSON> Exported RedisJSON_V1 API 1:M 29 Oct 2022 00:52:35.041 * <ReJSON> Exported RedisJSON_V2 API 1:M 29 Oct 2022 00:52:35.041 * <ReJSON> Enabled diskless replication 1:M 29 Oct 2022 00:52:35.041 * <ReJSON> Created new data type 'ReJSON-RL' 1:M 29 Oct 2022 00:52:35.041 * Module 'ReJSON' loaded from /usr/lib/redis/modules/rejson.so 1:M 29 Oct 2022 00:52:35.043 * Loading RDB produced by version 6.2.7 1:M 29 Oct 2022 00:52:35.043 * RDB age 101371 seconds 1:M 29 Oct 2022 00:52:35.043 * RDB memory usage when created 0.98 Mb 1:M 29 Oct 2022 00:52:35.043 # The RDB file contains AUX module data I can't load: no matching module 'scdtype00' Any suggestions? Thanks, Mike

Working here

Just update qbittorrentvpn (June 11) and it's not working. Most of the UI is missing and what is there doesn't respond. All my torrents that were listed are no longer displayed, but they exist on the filesystem. Can I fall back to the prior version? I don't see a version variable on the edit screen. I checked at docker.com and the container was updated 3 hours ago. The log file looked ok, no obvious errors.

Two weeks and the system hasn't crashed. So I'm going to assume that removing all IPs from br0 and moving them to "bridge" has stabilized the server. Next I'll re-IP all my dockers back to br0 but adding a VLAN as described above. I hope Lime Tech addresses this issue in a future release so that this workaround isn't necessary.

Update: For troubleshooting I have either shutdown or migrated all dockers from the "br0" to "bridge". I also upgrade back to 6.9.2 (from 6.9.1) since this issue seems to effect both 6.9.1 & 6.9.2. if this works, I'll likely use a VLAN as described in the links above. I'll see how long the system stays up. If I don't make any further updates to this thread after 2 weeks, assume that the problem is solved.

JorgeB, Thanks for the info. I'll give it try and move my br0 connections over to a VLAN. I looked at my syslog and found this from this morning, but the server has not crashed since yesterday. May 17 07:59:41 asok kernel: ------------[ cut here ]------------ May 17 07:59:41 asok kernel: WARNING: CPU: 15 PID: 0 at net/netfilter/nf_conntrack_core.c:1120 __nf_conntrack_confirm+0x9b/0x1e6 May 17 07:59:41 asok kernel: Modules linked in: vhost_net tun vhost vhost_iotlb tap kvm_intel kvm iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha veth xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat iptable_mangle macvlan xt_nat xt_MASQUERADE iptable_nat nf_nat xfs md_mod nct7904 watchdog ip6table_filter ip6_tables iptable_filter ip_tables igb i2c_algo_bit ipmi_ssif sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd mpt3sas i2c_i801 i2c_smbus input_leds glue_helper rapl intel_cstate i2c_core ahci led_class raid_class intel_uncore acpi_ipmi libahci scsi_transport_sas wmi ipmi_si acpi_pad button [last unloaded: kvm] May 17 07:59:41 asok kernel: CPU: 15 PID: 0 Comm: swapper/15 Not tainted 5.10.21-Unraid #1 May 17 07:59:41 asok kernel: Hardware name: Supermicro X9DRD-7LN4F(-JBOD)/X9DRD-EF/X9DRD-7LN4F, BIOS 3.3 08/23/2018 May 17 07:59:41 asok kernel: RIP: 0010:__nf_conntrack_confirm+0x9b/0x1e6 May 17 07:59:41 asok kernel: Code: e8 64 f9 ff ff 44 89 fa 89 c6 41 89 c4 48 c1 eb 20 89 df 41 89 de e8 d5 f6 ff ff 84 c0 75 bb 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 89 df 44 89 e6 31 db e8 5d f3 ff ff e8 30 f6 ff ff e9 22 01 May 17 07:59:41 asok kernel: RSP: 0018:ffffc900066e08a8 EFLAGS: 00010202 May 17 07:59:41 asok kernel: RAX: 0000000000000188 RBX: 0000000000003c05 RCX: 00000000b0e84f5c May 17 07:59:41 asok kernel: RDX: 0000000000000000 RSI: 0000000000000061 RDI: ffffffff820099c4 May 17 07:59:41 asok kernel: RBP: ffff888179d86f00 R08: 00000000fac24da6 R09: ffff8888a1211ae0 May 17 07:59:41 asok kernel: R10: 0000000000000158 R11: ffff8884a537f200 R12: 0000000000008461 May 17 07:59:41 asok kernel: R13: ffffffff8210db40 R14: 0000000000003c05 R15: 0000000000000000 May 17 07:59:41 asok kernel: FS: 0000000000000000(0000) GS:ffff88885fc40000(0000) knlGS:0000000000000000 May 17 07:59:41 asok kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 17 07:59:41 asok kernel: CR2: 000014faebee29f8 CR3: 000000000200c006 CR4: 00000000001706e0 May 17 07:59:41 asok kernel: Call Trace: May 17 07:59:41 asok kernel: <IRQ> May 17 07:59:41 asok kernel: nf_conntrack_confirm+0x2f/0x36 May 17 07:59:41 asok kernel: nf_hook_slow+0x39/0x8e May 17 07:59:41 asok kernel: nf_hook.constprop.0+0xb1/0xd8 May 17 07:59:41 asok kernel: ? ip_protocol_deliver_rcu+0xfe/0xfe May 17 07:59:41 asok kernel: ip_local_deliver+0x49/0x75 May 17 07:59:41 asok kernel: ip_sabotage_in+0x43/0x4d May 17 07:59:41 asok kernel: nf_hook_slow+0x39/0x8e May 17 07:59:41 asok kernel: nf_hook.constprop.0+0xb1/0xd8 May 17 07:59:41 asok kernel: ? l3mdev_l3_rcv.constprop.0+0x50/0x50 May 17 07:59:41 asok kernel: ip_rcv+0x41/0x61 May 17 07:59:41 asok kernel: __netif_receive_skb_one_core+0x74/0x95 May 17 07:59:41 asok kernel: netif_receive_skb+0x79/0xa1 May 17 07:59:41 asok kernel: br_handle_frame_finish+0x30d/0x351 May 17 07:59:41 asok kernel: ? ipt_do_table+0x570/0x5c0 [ip_tables] May 17 07:59:41 asok kernel: ? br_pass_frame_up+0xda/0xda May 17 07:59:41 asok kernel: br_nf_hook_thresh+0xa3/0xc3 May 17 07:59:41 asok kernel: ? br_pass_frame_up+0xda/0xda May 17 07:59:41 asok kernel: br_nf_pre_routing_finish+0x23d/0x264 May 17 07:59:41 asok kernel: ? br_pass_frame_up+0xda/0xda May 17 07:59:41 asok kernel: ? br_handle_frame_finish+0x351/0x351 May 17 07:59:41 asok kernel: ? nf_nat_ipv4_in+0x1e/0x4a [nf_nat] May 17 07:59:41 asok kernel: ? br_nf_forward_finish+0xd0/0xd0 May 17 07:59:41 asok kernel: ? br_handle_frame_finish+0x351/0x351 May 17 07:59:41 asok kernel: NF_HOOK+0xd7/0xf7 May 17 07:59:41 asok kernel: ? br_nf_forward_finish+0xd0/0xd0 May 17 07:59:41 asok kernel: br_nf_pre_routing+0x229/0x239 May 17 07:59:41 asok kernel: ? br_nf_forward_finish+0xd0/0xd0 May 17 07:59:41 asok kernel: br_handle_frame+0x25e/0x2a6 May 17 07:59:41 asok kernel: ? br_pass_frame_up+0xda/0xda May 17 07:59:41 asok kernel: __netif_receive_skb_core+0x335/0x4e7 May 17 07:59:41 asok kernel: ? __update_load_avg_cfs_rq+0xd6/0x18f May 17 07:59:41 asok kernel: __netif_receive_skb_list_core+0x78/0x104 May 17 07:59:41 asok kernel: netif_receive_skb_list_internal+0x1bf/0x1f2 May 17 07:59:41 asok kernel: ? dev_gro_receive+0x55d/0x578 May 17 07:59:41 asok kernel: gro_normal_list+0x1d/0x39 May 17 07:59:41 asok kernel: napi_complete_done+0x79/0x104 May 17 07:59:41 asok kernel: igb_poll+0xc9a/0xec8 [igb] May 17 07:59:41 asok kernel: ? do_send_sig_info+0x63/0x86 May 17 07:59:41 asok kernel: net_rx_action+0xf4/0x29d May 17 07:59:41 asok kernel: __do_softirq+0xc4/0x1c2 May 17 07:59:41 asok kernel: asm_call_irq_on_stack+0x12/0x20 May 17 07:59:41 asok kernel: </IRQ> May 17 07:59:41 asok kernel: do_softirq_own_stack+0x2c/0x39 May 17 07:59:41 asok kernel: __irq_exit_rcu+0x45/0x80 May 17 07:59:41 asok kernel: common_interrupt+0x119/0x12e May 17 07:59:41 asok kernel: asm_common_interrupt+0x1e/0x40 May 17 07:59:41 asok kernel: RIP: 0010:arch_local_irq_enable+0x7/0x8 May 17 07:59:41 asok kernel: Code: 00 48 83 c4 28 4c 89 e0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 9c 58 0f 1f 44 00 00 c3 fa 66 0f 1f 44 00 00 c3 fb 66 0f 1f 44 00 00 <c3> 55 8b af 28 04 00 00 b8 01 00 00 00 45 31 c9 53 45 31 d2 39 c5 May 17 07:59:41 asok kernel: RSP: 0018:ffffc900063fbea0 EFLAGS: 00000246 May 17 07:59:41 asok kernel: RAX: ffff88885fc62380 RBX: 0000000000000004 RCX: 000000000000001f May 17 07:59:41 asok kernel: RDX: 0000000000000000 RSI: 00000000313b14ef RDI: 0000000000000000 May 17 07:59:41 asok kernel: RBP: ffffe8f7ff47f700 R08: 00002a9d58969783 R09: 0000000000000000 May 17 07:59:41 asok kernel: R10: 000000000000f71a R11: 071c71c71c71c71c R12: 00002a9d58969783 May 17 07:59:41 asok kernel: R13: ffffffff820c7ec0 R14: 0000000000000004 R15: 0000000000000000 May 17 07:59:41 asok kernel: cpuidle_enter_state+0x101/0x1c4 May 17 07:59:41 asok kernel: cpuidle_enter+0x25/0x31 May 17 07:59:41 asok kernel: do_idle+0x1a6/0x214 May 17 07:59:41 asok kernel: cpu_startup_entry+0x18/0x1a May 17 07:59:41 asok kernel: secondary_startup_64_no_verify+0xb0/0xbb May 17 07:59:41 asok kernel: ---[ end trace eaf4c384b8419f52 ]--- I report back after I get the VLAN setup and dockers moved over to it. Mike

My server has been kernel panicing every 2-3 days since mid-April. It panicked 3 times today alone. I'm looking for any help I can get. History and steps so far... Problems started about 10 days after I upgraded to 6.9.2. I searched the forum and redit and found other "not syncing" type problems. One some were at boot and the solution seems to be replacing the USB flash drive. My server has never failed to boot, so I have discounted the USB flash drive as the problem. The second type I found was bad RAM. My server has 64G of RAM on 4 DIMMs. I removed 32G and ran the server until it panicked within 2 days. I then swapped the RAM and again within 2 days the server panicked. So I think I can assume the RAM is okay. I've also downgraded to 6.9.1 thinking maybe 6.9,2 was the problem. Again, the server panicked within a few days. BTW, I'm still on 6.9.1. Since the server panics, I don't have much in the way of logs, etc. I do have screenshots of the IPMI console and they all look very similar. I've not made any major, or minor really, changes to the server prior to the panics. The system has been running well for years. I'm starting to think the problem is hardware based since switching unRAID versions and few changes prior to the panics would rule out software. After the second (of three) crashes today I change the Tunable (md_sync_limit) from the default setting of "5" to "10". This was a wild guess at trying to solve this problem. It's the only parameter I could find that has "sync" in it. I couldn't find any documentation on this parameter either. Changing the value to "10" doesn't seem to have helped since the server has since crashed. Since the panics have started the server has been in almost constant parity check status. So much so I've had 2 drive die. I can't be sure the constant parity checks killed them, but I'm sure it didn't help either. It took more than a week, but I was able to replace the 2 dead drives between panics. I also upgraded my parity drives from 10G to 18G and used the old 10G parity drives to replace the dead drives. For now I'm canceling parity checks since the server has crashed 3 times in just one day. I also stopped all but a few dockers and no VM's. Attached are my diagnostic files and a screenshot of the console after a panic. Any help will be welcome, Mike asok-diagnostics-20210516-1950.zip

SOLVED: See below When thru all the install steps and have UUD kind of working. Biggest problem is getting Varken to connect to Tautulli and Sonarr. Here's the errors I get in the Varken log. 2021-04-03 01:10:30 : INFO : __init__ : Running job Every 30 seconds do thread(<bound method TautulliAPI.get_activity of <tautulli-1>>) (last run: 2021-04-03 01:10:00, next run: 2021-04-03 01:10:30) 2021-04-03 01:10:30 : DEBUG : connectionpool : Starting new HTTP connection (8): ********.1.37:8181 2021-04-03 01:10:33 : ERROR : helpers : Cannot resolve the url/ip/port. Check connectivity. Error: HTTPConnectionPool(host='192.168.1.37', port=8181): Max retries exceeded with url: /api/v2?apikey=xxxxxxxxxxxxxxxxxxxxxxx&cmd=get_activity (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x14a1e06afa90>: Failed to establish a new connection: [Errno 113] Host is unreachable')) 2021-04-03 01:13:03 : ERROR : helpers : Cannot resolve the url/ip/port. Check connectivity. Error: HTTPConnectionPool(host='192.168.1.37', port=8181): Max retries exceeded with url: /api/v2?apikey=xxxxxxxxxxxxxxxxxxx&cmd=get_activity (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x14a1e06943a0>: Failed to establish a new connection: [Errno 113] Host is unreachable')) Note: I've x'ed out the API key. Here's the varken.ini file. [global] sonarr_server_ids = 1 tautulli_server_ids = 1 maxmind_license_key = xxxxxxxxxxxxxxxxxxx [influxdb] url = 192.168.1.2 port = 8086 ssl = false verify_ssl = false username = telegraf password = metricsmetricsmetricsmetrics [tautulli-1] url = 192.168.1.37:8181 fallback_ip = 1.1.1.1 apikey = xxxxxxxxxxxxxxxxxxx ssl = false verify_ssl = false get_activity = true get_activity_run_seconds = 30 get_stats = true get_stats_run_seconds = 3600 [sonarr-1] url = 192.168.1.131:8989 apikey = xxxxxxxxxxxxxxxxxxx ssl = false verify_ssl = false missing_days = 7 missing_days_run_seconds = 300 future_days = 1 future_days_run_seconds = 300 queue = true queue_run_seconds = 300 Checked all setting many times. Either I'm missing something or overlooked a setting. Both Tautulli and Sonarr have been running for years and I verified both were running. Even restarted them several times. SOLVED: I followed the install instructions in the "Technically Speaking" YouTube videos. He setup his Varken docker with a "Bridge" network type. Not sure why, but this did not work for my setup. I tried "Host" and that failed too. So I used a custom interface, "br0" and gave the docker it's own IP address and now it's conneted to both Tautulli and Sonarr. If I had to guess why this happened is because most of my dockers are setup to use a different IP address from my UnRAID server.

I'm having the same issue. I downgraded to 4.2.1-1-05 but I'm still getting the errors messages you listed above.

Djoss, Thanks for setting me on the correct path. I swear I had turned on advanced setting, but obviously didn't.

Is there any way to increase the size of the QDirStat window? I use another docker, MKVToolNix, which has two docker variables to adjust the screen size. They are, DISPLAY_WIDTH & DISPLAY_HEIGHT. I tried adding these to the QDirStat docker but it didn't cause any change.