All Activity

Folgende Shares solltest Du immer auf dem Cache lassen (Primary storage > Cache; Secondary stoarge > none): appdata domains system (isos) < nicht zwingend aber besser Das sind Verzeichnisse, auf die Docker/VM's zugreifen. Wenn diese auch im Array sind, können die HDD's nicht schlafen. Und die Geschwindigkeit der Docker/VM's lässt sehr zu Wünschen übrig.

Mehr als das: https://www.ionos.de/digitalguide/server/sicherheit/3-2-1-backup-regel/ würde die

4 hours of fidgeting around just because of an extra space 😞 Thank you very much! It worked!

Here is the diagnostics. My timezone is America/Chicago and I also noticed that the date when I login is 5 hours behind. So, if I login at 11 pm, typing date command brings back 6 pm. I went through the posts regarding "Device eth0 does not exist". I deleted my network.cfg, ensured that Bridging is enabled. I also bought a separate NIC and tried to use it, but no luck. I still get the same message and I cannot connect to the server over my network. tower-diagnostics-20240426-1833.zip

大家好，我最近使用unraid建立了两个服务器，一个使用3个314A网卡，另一个使用2个flr544+网卡。我将它们全部连接到Mellanox sx6036。由于每个网卡都有两个40G接口，我希望通过LACP实现高速。当我完成配置后，我使用内置的iperf3来测量速度，发现除了eth0之外的所有接口都没有负载，所以它只能在25G左右运行。我希望得到帮助。这是我的配置图（配备314A的机器目前只插入了两个端口） 兄弟们救一救！

Gonna need to know a bit more information: Are you running your own nginx to handle the letsencrypt part, or saying that you are using the discourse letsencrypt/nginx? If running your own - Do other https apps work correctly? Your nginx/SWAG config file is the most likely culprit. If you're getting far enough that the browser is saying it's not secure, it tells me nginx isn't configured correctly yet. Discourse does run its own internal nginx/letsencrypt which is configured through the built in config yml files.

Was sollte ich denn noch berücksichtigen? Meinst du damit das noch andere Hardware kaputt gehen kann wie der Cache oder das MB oder eher Fehler die mit den Daten passieren können? Ja genau das ist der Punkt wo fängt man an und wo hört man auf weil es die kosten sprengt. Unraid hängt bei mir an einer USV und eine Überspannungsschutz des weiteren backuppe ich alles wichtige auf einen externen Server. Was könnte ich den noch sinnvolles machen?

My inquiry revolves around NFS/Unassigned Devices/IP. Here's the scenario and my initial train of thought, although I later realized there might be flaws in my approach. I have two Unraid servers: one with 38 TB dedicated to storing all my media (Server 1), and the other with 24 TB for files, apps, etc. (Server 2). Server 1 is equipped with a Ryzen 9 - 7900X processor, 64GB of memory, 2X10GB interfaces, and 4x1GB interfaces. Server 2 features a Ryzen 7 - 2700X processor, 32GB of memory, 1x10GB interface, 2x1GB interfaces, and an RTX 1650. Initially, my plan was as follows: Connect Server 1 and 2 via the 10GB interface. Have Server 2 host my Plex server and access an NFS share on Server 1 to read the media. Manage both Server 1 and 2 (Unraid IP) on a different network. Provide Server 2 with a network for accessing the Plex App. My aim was to separate Unraid management and media sharing via NFS onto different networks. However, I'm uncertain whether I can confine NFS/Unassigned Devices to a specific interface/IP/Network. Is this feasible, or am I restricted to having NFS on the Unraid management interface?

it seems that for right now this is not possible as starting with version 1.20.5 of minecraft it now requires java 21 and at this time it is not available on linux except for unstable testing. i will be keeping an eye on this and try to work on a fix

Hi @JorgeB and @bonienl, could you please share us the progress or plan about the issue? Though we can manually flush the IPv6 address, I still want the Unraid to flush it automatically.

Thanks for your command! at least I don't need to restart.

Ok, that actually answered a lot of my questions. Thank you again for the link.

I've been having a reoccurring issue with my system for about 2 weeks now, and I had originally diagnosed it to be faulty memory but I have a new unbuffered ECC set that's passed 10 runs of memtest86+ and I'm at my wits end. Aside from the memory, the rest of the hardware is less than 2 years old. I have tried rolling the OS version back to an older one and it does not resolve the issue, but I can't find anything in the syslog that could point me in the right direction and have no idea where to start digging past that. There's nothing I can find that indicates a pattern, either. I've attached the diagnostic report made after the last crash. tower-diagnostics-20240426-2050.zip

That's all very odd...i am aware of the Disk 9 Write caching and I am adding and replacing drives very frequently lately the go file has been like that for years without issues. almost all of it is commented out the docker-shell is just a small script that lets me via via CLI press a number to access any running docker containers cli it was introduced by spaceInvader1 some years ago. the log file was set set larger to accommodate some issues i had a long time ago. I do not have IPv6 enabled on my network or unRAID so that's very odd. I am using IPvlan as MacVLAN had issues a version or two back. eth0 is my 10gbps NIC and eth1 is the on board 1gbps NIC i would think nothing is wrong there since its been working for just over a year in this configuration. either way its something that recently happening and hasn't since the last recovery....very odd

Wireguard is built into unraid and is my go to for accessing my server from a phone or another computer. It also allows you access other machines on the same network.

My experience is exactly the opposite, I have Deluge running for many weeks before restarting, and have no issues when restarting the container from the dashboard in unraid. I used to do what I had mentioned and use quit and shutdown, and it did not restart itself...I'm not sure what init changes were made that may have changed this behavior, but consider I believe it ran with -d it shouldn't restart the daemon, I had a crash a few days ago during some testing of some stuff, and the daemon didn't relaunch. deluge-web kept running but was not connected to any daemon, the two are not mutually exclusive. Edit: If you want to stop the daemon from the webui, go to connection manager, and select the daemon and hit stop daemon.

Apologies for dragging this up again, cleanly shutting down deluge seems to have been a problem since it's inception lol. I have managed to 'Quit & Shutdown Daemon' from the windows client as mentioned above (does option not exist in the web client?), which seems to have resolved most of the issues I had previously with stopping the docker container from unraid. The issue I'm having now is that the daemon restarts itself. So if I need to shutdown the container for whatever reason I have to 'Quit & Shutdown Daemon', wait long enough that it shuts down cleanly, but not too long or it will have started again. I assume there's something in the Binhex container that's recognizing that the process is no longer running and starting it up again? Can I stop this somehow?

这可能得等12小时左右，我在重建校验盘，有结果了我在回复

那你之前的问题没有描述完整，现在尝试重置一下硬盘插槽：工具-新配置-勾选阵列插件重置 然后去共享重新添加设置，拆分级别：自动拆分，包含和排除的硬盘都要指定

UPDATE: I fixed the playback error part, even though i did this a couple times, i once again deleted the Codecs folder and started the server again and it started working. I would still like to know if the whole old version of server is normal, or if i need to do somethign else to get it updated. Thanks. Hi, question, Plex has been running great but all of a sudden i seem to be having issue playing back some media, even stuff i was able to play like 30 mins ago. I added a new movie to my collection and went to play, and after a few seconds of trying to load, it came back Playback Error. I then tried to play a movie i just watched, and same issue. Its a mixture of things that will play and things that wont. I did a restart and update to the latest version of unraid. I am using linuxserver resp and noticed that while it says updated on April 18th, and no update availble in docker, on the plex server, it shows im running version 1.31.3.6868 and latest is like 1.40. Is this common, i dont really recall as since installing, i never had to worry about it.

并不是，以前的版本文件夹Disk_Media包含了磁盘2 3 4 5 6 7 8 这个文件夹内的文件夹只要建立在哪个磁盘就会往哪个磁盘写入文件，现在的情况变成了在2磁盘建立文件夹 却写到了3我是从6.12.4升级到6.12.10的 6.12.4是可以这样的

I noticed this: Apr 26 14:54:22 streamengine kernel: PANIC at space_map.c:405:space_map_load_callback()

你的设置明显错误，根据你的描述，应该是要把文件夹Disk_Media指定存储在disk2。那么正确的操作应该是： 从一级导航 共享 下新建目录Disk_Media 拆分级别默认自动拆分即可 包含磁盘勾选disk2，排除磁盘disk1和disk3 补充一下，从文件管理器里disk2下新建的文件夹不会自动聚合在/mnt/user/