All Activity

I'm getting an issue that user scripts aren't running. Simple script #!/bin/bash echo "hello" getting a blank screen or a 504 Bad Gateway error. Nothing logged (that I know of). I've tried it on mutiple browswers, only started happening since the last User Scripts update.

But the interesting thing is, I switched to a new PSU and I had the same issue in unraid normal mode. And I tested a CPU Benchmark in Unraid safe mode without plugins and everything. (I tested also with only plugins on). And everything works without Issues for a long time. But I also found a setting in BIOS its called Power Loading. -> Enables or disables dummy load. When the power supply is at low load, a self-protection will activate causing it to shutdown or fail. If this occurs, please set to Enabled. Auto lets the BIOS automatically configure this setting. Maybe I should try that ?

Yeah that doesn't work sadly, I tried that already It throws a 404 Yeah that's what I thought I should do but was scared of. If it doesn't end up working in another port, but I assign all drives to the same spots, will all the data, dockers etc be fine? (also sorry for the delayed reply, it appears my notification settings weren't what I thought they were)

It all started with a drive failure. I had a drive fail, so I replaced it and rebuilt onto a new, bigger, drive. Once the rebuild was finished, somehow all of my docker containers were gone. Now, when I reinstall the container, and try to restore from app data backups, sometimes my GUI will go completely white, not even the menu bar is left. tower-diagnostics-20240420-1025.zip

I have read some discussions about using this switch. Just realize what it will do if you decide to use it. If you 'accidentally' (or anything else happens--Hacker, careless user, malware. etc.) delete a file from the source, this switch will delete it from the destination file system. This will make it difficult (or, possibly, impossible) to recover those files. IF you just leave them there on the destination file system, they will be there if you ever need to find them again. The only reason for using the -delete switch is to make sure that both the source and destinations file system are mirrors of each other. If your objective to be able to recover 'missing' files, it may turn out to be counterproductive in some respects! If you are backing up temporary file systems and there is a need to delete them periodically, I would only use that switch on that segment of the file system that those files are in. (I store the complete command line for each of the rsync commands that I use a plain text file and copy-and paste the appropriate command line into GUI terminal window.)

Hallo, ich denke der Titel ist schwer verständlich. Folgendes Problem: Ich habe meinen Unraid PC von einem I9 10900 auf einen auf eine I9 12900 umgebaut. Also kompletes System ink. Mainbaord. Mainboard ist ein Z690 mit DDR5 Ich habe drei NVMe SSDs und leider zeigen alle Fehler (siehe Screenshot) wenn man sie in den einen der Chipsatz SSD PCI Slots betreibt. Im CPU SSD PCI Slot funktionieren alle ohne Probleme. Die Fehler treten auch erst auf wenn ich das Board mit einer eingesteckten Grafikkarte betreibe - ohne, mit IGPU funktionieren alle SSds in allen Slots. Also irgendwas mit dem PCI Bus Traffic? Aber momentan tap ich da im Dunkeln, woran das wirklich liegt - Evtl. hat hier jemand eine Idee um der Ursache auf die Spur zu kommen.

A couple years ago I set up a NAS with an UNRAID Trial key and moved a bunch of backup data on to it. The OS version is 6.9.2. Today I had need of that data again, so I plugged in and spun up this device. The trial by now had of course expired, so I purchased an Unraid OS Unleashed License as I have 8 drives in this NAS. When I attempt to apply the activation code I just purchased I get the error "Could not find associated product Unleashed Redemption" (shown below). I see that it says "To redeem or purchase Starter, Unleashed or Lifetime licenses, please upgrade to at least Unraid 6.12.8 or later via Tools > Update OS in the Unraid webgui." however without being able to apply my code, I am not able to upgrade from the GUI. What am I supposed to do? https://drive.google.com/file/d/1PRY-VkWrEdi7mJGZ3FivpYYcny61hyDT/view

I am running a few web applications via docker on my unraid. Every day, appdata backup plugin will backup appdata, during this time, the containers will have short downtime. My concern is that downtime affects my Google page indexing Many of the pages has the status: Crawled - currently not indexed Anyone else encounter the same issue? Or did some experiment?

all my issue was a USB flash drive malfuction. I switched to another flash drive and used the Unraid USB cretor tool and now my server is up and running with all the OS update and plugins. Somehow the boot flash got into "read-only" mode and thats why Unraid couldnt make any writes on the boot device.

So, after several weeks of trying to find the problem, all it was a USB flash drive malfunction, somehow it got to the point where the flash drive only stayed in "read-only" and thats why unraid could not write any of the updates to the boot device. I changed to another flash drive (it took me a hell of work because I did it the hard way) and now my unraid is working find and updates are back for the OS and plugins. Thanks for the replies!

Thank you, Kilrah. I clearly misunderstood.

That is for appointing someone to configure your server for you. Licensing issues have nothing to do with this and will be solved when you fill up the form with your problem without any payment obviously.

Kilrah, Support want $150 just to chat. Pro license - and I should be able to do this without paying someone more money. I can show the whole screen but it gives out my license number

1) Your screenshot doesn't show the reason it isn't 2) Contact support, forum can't help with licensing

I have a Pro license and a flash usb boot drive that says it no longer can write. I'm pretty sure I have *not* transferred this license before but I'm trying to transfer the license to a new flash drive and it's telling me it's Ineligible. I'm holding my temper really hard right now. I don't feel I should be seeing this at all with my Pro license with my data effectively being held hostage. As far as I'm concerned I feel we should be able to have a full working backup usb boot drive, and I apologize if that offends anyone, but here we are and without a working boot backup, I'm stuck with a failing USB drive in order to access my data. How do we fix this?

First off, thanks for those that took some time to reply. I appreciate the help! So instead of "nestat -i" I used "ip -d link" which showed all the links and the promiscuity value. I can't say I would know what is right or wrong here. But, trying to wrap my head around this, to me, I think eth0 should NOT have promiscuous mode turned on and the VLAN eth0.2@eth0 SHOULD have it turned on. It's only eth0.2 that has multiple MAC addresses on it. ETH0 does not. Just to clarify so we are all on the same page, it is 02:65:43:f8:ad:c4 (vhost0@eth0 & [email protected]) that is being reported on Unifi as having the same IP as 3c:8c:f8:ee:59:84 (eth0) A couple of other questions if anyone knows: Why does eth0 have "promiscuity 2" whereas all the others are "promiscuity 1" or "promiscuity 0". Why are maxmtu different across intefaces? It's "65535" on eth0.2, virbr0 and vhost0.2 and "16334" on eth0, vhost0 and macvtap0. root@KNOXX:~# ip -d link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 promiscuity 0 allmulti 0 minmtu 0 maxmtu 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 524280 tso_max_segs 65535 gro_max_size 65536 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 promiscuity 0 allmulti 0 minmtu 0 maxmtu 0 ipip any remote any local any ttl inherit nopmtudisc addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 65536 tso_max_segs 65535 gro_max_size 65536 3: eth0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 3c:8c:f8:ee:59:84 brd ff:ff:ff:ff:ff:ff promiscuity 2 allmulti 0 minmtu 68 maxmtu 16334 addrgenmode eui64 numtxqueues 32 numrxqueues 32 gso_max_size 65536 gso_max_segs 65535 tso_max_size 65536 tso_max_segs 65535 gro_max_size 65536 parentbus pci parentdev 0000:03:00.0 4: eth0.2@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 3c:8c:f8:ee:59:84 brd ff:ff:ff:ff:ff:ff promiscuity 1 allmulti 0 minmtu 0 maxmtu 65535 vlan protocol 802.1Q id 2 <REORDER_HDR> addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 65536 tso_max_segs 65535 gro_max_size 65536 5: vhost0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq state UP mode DEFAULT group default qlen 500 link/ether 02:65:43:f8:ad:c4 brd ff:ff:ff:ff:ff:ff promiscuity 0 allmulti 0 minmtu 68 maxmtu 16334 macvtap mode bridge bcqueuelen 1000 usedbcqueuelen 1000 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 65536 tso_max_segs 65535 gro_max_size 65536 6: [email protected]: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq state UP mode DEFAULT group default qlen 500 link/ether 02:65:43:f8:ad:c4 brd ff:ff:ff:ff:ff:ff promiscuity 1 allmulti 0 minmtu 68 maxmtu 65535 macvtap mode bridge bcqueuelen 1000 usedbcqueuelen 1000 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 65536 tso_max_segs 65535 gro_max_size 65536 7: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default link/ether 02:42:d6:d7:15:3b brd ff:ff:ff:ff:ff:ff promiscuity 0 allmulti 0 minmtu 68 maxmtu 65535 bridge forward_delay 1500 hello_time 200 max_age 2000 ageing_time 30000 stp_state 0 priority 32768 vlan_filtering 0 vlan_protocol 802.1Q bridge_id 8000.2:42:d6:d7:15:3b designated_root 8000.2:42:d6:d7:15:3b root_port 0 root_path_cost 0 topology_change 0 topology_change_detected 0 hello_timer 0.00 tcn_timer 0.00 topology_change_timer 0.00 gc_timer 47.60 vlan_default_pvid 1 vlan_stats_enabled 0 vlan_stats_per_port 0 group_fwd_mask 0 group_address 01:80:c2:00:00:00 mcast_snooping 1 no_linklocal_learn 0 mcast_vlan_snooping 0 mcast_router 1 mcast_query_use_ifaddr 0 mcast_querier 0 mcast_hash_elasticity 16 mcast_hash_max 4096 mcast_last_member_count 2 mcast_startup_query_count 2 mcast_last_member_interval 100 mcast_membership_interval 26000 mcast_querier_interval 25500 mcast_query_interval 12500 mcast_query_response_interval 1000 mcast_startup_query_interval 3125 mcast_stats_enabled 0 mcast_igmp_version 2 mcast_mld_version 1 nf_call_iptables 0 nf_call_ip6tables 0 nf_call_arptables 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 65536 tso_max_segs 65535 gro_max_size 65536 10: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:ca:33:2d brd ff:ff:ff:ff:ff:ff promiscuity 0 allmulti 0 minmtu 68 maxmtu 65535 bridge forward_delay 200 hello_time 200 max_age 2000 ageing_time 30000 stp_state 1 priority 32768 vlan_filtering 0 vlan_protocol 802.1Q bridge_id 8000.52:54:0:ca:33:2d designated_root 8000.52:54:0:ca:33:2d root_port 0 root_path_cost 0 topology_change 0 topology_change_detected 0 hello_timer 1.28 tcn_timer 0.00 topology_change_timer 0.00 gc_timer 80.37 vlan_default_pvid 1 vlan_stats_enabled 0 vlan_stats_per_port 0 group_fwd_mask 0 group_address 01:80:c2:00:00:00 mcast_snooping 1 no_linklocal_learn 0 mcast_vlan_snooping 0 mcast_router 1 mcast_query_use_ifaddr 0 mcast_querier 0 mcast_hash_elasticity 16 mcast_hash_max 4096 mcast_last_member_count 2 mcast_startup_query_count 2 mcast_last_member_interval 100 mcast_membership_interval 26000 mcast_querier_interval 25500 mcast_query_interval 12500 mcast_query_response_interval 1000 mcast_startup_query_interval 3125 mcast_stats_enabled 0 mcast_igmp_version 2 mcast_mld_version 1 nf_call_iptables 0 nf_call_ip6tables 0 nf_call_arptables 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 65536 tso_max_segs 65535 gro_max_size 65536 30: macvtap0@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 500 link/ether 52:54:00:94:77:76 brd ff:ff:ff:ff:ff:ff promiscuity 0 allmulti 0 minmtu 68 maxmtu 16334 macvtap mode bridge bcqueuelen 1000 usedbcqueuelen 1000 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 65536 tso_max_segs 65535 gro_max_size 65536

目前未开的情况，会一会休眠一会转动，反而是打开虚拟机，一会儿没用就休眠了

双盘校验和单盘校验写入速度有差是吗？

It's dynamic, and there's actually a "CA Auto Turbo Write Mode" plugin to change it based on some conditions. Probably why Auto isn't implemented, the plugin's more flexible.

That would start the sync. Unless you happened to wrongly tick the "parity is valid" checkbox.

Hello! I use my Mac primarily, but have a windows computer backup. I have been trying to configure a YAML file for a dashboard (startpage) and I am running into an issue when my windows machine can edit it, but my Mac can't. My Mac can only duplicate it, edit the duplicate file, and then I have to put the new file back and delete the old one to make changes. This makes it annoyingly difficult to edit, check changes, edit, check changes. I tried the same thing on my windows computer, and it works pretty flawlessly. I can edit the changes directly in the file without duplicating file and so on. I checked the user permission of the file, and they were root root. I ran chmod -R 99:100 which changes them to nobody and user. I disconnected my Mac from the server and then reconnected it. I even restarted my Mac. The issue still exists.

Der Befehl ist auch Nonsens seh ich gerade. Hab den auch nur aus dem oben verlinkten Thread.

I tried that and was able to narrow the problem to two of the drives. WD100EMAZ-OOWJTAO WD120EDAZ-11F3RAO When I put them back in the drive toaster, they're still detected on my laptop, but not in BIOS when I put them in the board, even after swapping the sata data cables around.

Do you have any idea how to undo this? RAID is completely disabled btw. I bought these two OS HDDs from a used NAS. Already formatted them dozens of times. Nothing helps

@ElVit Das Du nach der Installation der RTL8168 Treiber aus dem Appstore in C8 kommen willst wundert mich etwas. ASPM wird dann zwar als aktiv angezeigt aber C3 wurde bei mir und anderen damit nie unterschritten. Das steht auch im GITHUB bei den Treibern das ASPM damit nicht funktioniert. Dafür haben wir ja den SETPCI workaround der hier im Thread beschrieben ist und der OHNE die Installation der RTL8168 Treiber aus dem Appstore funktioniert. Du hast C8 wirklich mit Powertop überprüft? Dein Verbrauch scheint mir auch etwas hoch zu sein. 25W bei 3 HDDs im Spindown ist zuviel. Das Board sollte ca. 6-8W brauchen, dazu der ASM1166 Controller mit ca. 2W und die 3 Platten nochmal ca. 3-4W. Ich hätte also im idle (ohne Docker oder VMs laufen) ca. 11-14W erwartet. Du solltest das nochmal checken mit Powertop ob Du wirklich in den C8 kommst. Zur PicoPSU. Nimm gleich eine 160W. Man weiss nie ob nicht noch 1-3 Platten dazu kommen. Dazu ein Leicke 156W (oder 154W, habs gerade nicht detailliert im Kopf) Netzteil und 2-3 Platten zusätzlich sind auch später noch möglich. Gruss, Joerg