Letztes Thema vor 7 Std.

Unraid Forum

forums.unraid.net

Invision Community-Forum auf Englisch. 9 beobachtete Rubriken: File Sharing Protocol Support, Active Directory, Forum Feedback, Security, Pre-Sales Support, Unraid Blog and Uncast Show Discussion, Unraid Polls, General Support und Announcements.

Diskussionen pro Tag
30
Eingesammelte Diskussionen
623
Beiträge pro Tag
70
Rubriken
9
Beobachtete Quellen
10
Software
Invision Community

Neueste Diskussionen

Alle 4 Stunden aus dem öffentlichen Feed des Forums eingesammelt. Wiedergegeben werden nur Titel, Link und der Anfang der Nachricht; jeder Link führt zur Quelle zurück.

Migrate unraid to new harware

My current nas is becoming too small (HP microserver 10+) and I built a new one on SuperMicro X11SSH-LN4F platform with 10 HDD slots. I have ran memtest for multiple cycles and (fresh) unraid license for weeks now without issues for testing purposes. I have tested all the HDD slots and GPUs etc. All works as intented. I then took out all the drives, usb stick and cache drive from old machine(HP microserver) and installed them on the new supermicro platform and booted up. Everything works as intented as long as I do not put array online. As soon as I do it, the unraid locks up and does not recover without hard reset. I have disabled VMs and Dockers, but still locks up. Any ideas what is wrong with the system? Logs don't give any errors. And obviously, when the system locks up, also the logs stops responding. I have not tried yet the logs write on USB stick, since I started to have corrupted configurations with all those hard lockups and resets.

Habe jetzt einen neuen Server gebaut

Nachdem ich vor einiger Zeit mit diesem Projekt einstieg: https://forums.unraid.net/topic/149832-neuer-server/#comment-1342024 Es hat rund 2 Jahre gedauert, in denen alles funktioniert hat..Nur ab und zu zeigte er, dass eine der beiden hdds zu warm wurde. Die alte Hardware war auch nicht mehr erweiterbar, also musste was neues her. Als Gehäuse hatte ich noch einen alten Chieftec Midi-Tower stehen. Dieser wurde mit Staubschutzmatten gegen Staub gesichert. Folgende Komponenten verbaut: Netzteil:BeQuiet PurePower 11 400W I3 14100 B760m DS3H Speicher 16gb, 2x12TB HDDs und 512GB SSD wurden aus dem alten System übernommen. CPU-Kühler wurde einem anderen Terra-System entnommen. Dieses ist in ein anderes Gehäuse gezogen und hat eine WaKü spendiert bekommen. Zusätzlich wurde eine 240GB SSD BX200 von Crucial für Frigate verbaut. Durch die 3 seitliche Lüfter an den HDDs (arctic P9 Pro CO) steigt die Temperatur der beiden HDDs kaum über 40 Grad, ca 25 Grad im Ruhezustand

Nvidia Driver Plugin support

Hello, I'm am having issues with this after trying to upgrade unraid to 7.3.2. Here are the details: Nvidia Driver plugin selects wrong version on Unraid 7.3.2 upgrade System: Unraid 7.3.2, NVIDIA T400 4GB (TU117GL / Turing), driver plugin currently on 580.126.09 (not yet rebooted into 7.3.2). Steps: Started the 7.3.2 upgrade (not yet rebooted). Got the "unRAID version change detected" notification, followed by: Nvidia Driver v580.173.02 download failed Download from plugin package(s): Nvidia Driver for unRAID v7.3.2 failed! Checked the Nvidia Driver plugin page. Plugins page shows "up to date," but the driver info section lists: Supported candidates: 580.159.03, 590.48.01, 595.71.05 Recommended: 595.71.05 (open-source) Selected the 595.71.05 radio button and triggered a download. Log output shows it attempting to download v575.64.05 instead — a version that isn't even in the supported candidates list. Hard-refreshed (and tried different browser) and re-selected 595.71.05 — same result, still tries 575.64.05. Question: Is this a known issue with the version selector not saving/applying on this build? Is there a workaround (e.g. manually editing settings.cfg) to force the correct version, or should I wait for a plugin update before rebooting into the new kernel? Diagnostics attached if needed. Haven't rebooted yet — holding off until this is sorted since 575.64.05 isn't confirmed built for the new kernel. ds9-diagnostics-20260907-1054.zip

Networking degradation after Array update

I have a small NAS for media storage & backups: 128 Mb NVME /boot, 2Tb NVME /cache, and 2x 1TB SSDs /pool. Unraid was working great, but obviously storage was limited, so I swapped the SSDs for 2x 4Tb WDRed HDDs so that I could have a parity array. I changed no settings on Unraid or my router besides changing the pool to an array and clean-up of the shares, and now my network speeds are atrocious (see screencaps). Both NFS and SMB slow to a crawl (or halt) even on the fast /cache, and it makes no difference whether I "upload" from within Unraid or push a copy from my desktop. I've set Turbo Write on the arrays, backed NFS down to v3, and even tried pulling the hdd's, but nothing has worked. I'm at a loss, and google has thus far been unhelpful. Hoping some kind soul here might read my diagnostics and see if anything stands out. I appreciate any insights you can provide! unraid_upload-diagnostics-20260909-0920.zip

ZFS Pool unmountable after removing a drive (failed state)

Today, I decided to take one of the drives out of my cache pool (initial plan was to split the cache into two separate pools - 2x in one, 1x in the other). Managed to push the data out of one drive, and all was going well... (ish).... root@Tower:~# zpool status -P -v cache zpool events -v | tail -250 pool: cache state: SUSPENDED status: One or more devices are faulted in response to IO failures. action: Make sure the affected devices are connected, then run 'zpool clear'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-HC scan: scrub in progress since Wed Sep 9 16:25:52 2026 1.22G / 1.08T scanned at 2.31M/s, 0B / 1.08T issued 0B repaired, 0.00% done, no estimated completion time remove: Removal of vdev 0 copied 375G in 0h17m, completed on Wed Sep 9 13:33:48 2026 11.9M memory used for removed device mappings config: NAME STATE READ WRITE CKSUM cache FAULTED 0 0 0 corrupted data /dev/sdk1 ONLINE 0 0 0 /dev/sdi1 FAULTED 0 0 1.28K corrupted data /dev/sdi1 ONLINE 0 0 0 However, after a clean reboot, I get: root@Tower:~# /usr/sbin/zpool import -d /dev/sdi1 -d /dev/sdk1 pool: cache id: 9185321213315192028 state: FAULTED status: One or more devices contains corrupted data. action: The pool cannot be imported due to damaged devices or data. The pool may be active on another system, but can be imported using the '-f' flag. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-5E config: cache FAULTED corrupted data indirect-0 ONLINE sdk1 ONLINE sdi1 FAULTED corrupted data s

Docker Service Failed to Start

Need some help please. After updating Plex, I rebooted the server and after the reboot, I am getting "Docker Service Failed to Start" error on the docker tab. Don't know if the update is the culprit, but I have attached the system log.unraid-syslog-20260909-1515.zip

Unraid 8: Will the Unraid account remain truly optional?

I've been using Unraid for many years and I'm still running a legacy Pro license. I chose Unraid very deliberately because it was a self-hosted operating system: I buy the software, install it on my own hardware, and decide myself what I run on that hardware. I'm following the development of Unraid 8 with a lot of interest. There are several things I genuinely like about the direction, especially native Docker Compose and the move towards a more modern underlying platform. However, there is one aspect of the Unraid 8 direction that increasingly concerns me: the gradual integration of the Unraid account, Community Apps, backup functionality and other services into the core user experience. I understand why Unraid wants to make these things easier and more consistent. But I would really like some clarity about where the boundary is between Unraid OS itself and Unraid's online services/ecosystem. For me, an Unraid server should ideally be able to operate completely locally. I don't need Unraid Cloud. I don't need remote management through Unraid's infrastructure. I don't need my server to depend on an Unraid account for day-to-day operation. If I want remote access, backups, monitoring or other services, I already have the ability to build and host those myself. That's actually one of the reasons I run an Unraid server in the first place. What concerns me is the possibility of a gradual shift from: "Unraid is a self-hosted OS." towards: "Unraid is a self-hosted OS, but increasin

Disk Upgrade/Replacement.

I have an UGreen DXP2800 NAS drive running Unraid. I have the OS and cache set up on an 2xNVME drives. All my media is on 2xHDD. One is an 8GB WD Red HDD and the second drive is a 10TB Seagate Ironwolf. The WD drive is getting on and I have bought another Irongate to replace it. The majority of my data is held on the WD. My question is how can replace the drive and move the data. Do I simply move it all across to the current 10TB drive, or do I remove the current 10TB and then replace it with the new 10TB drive before moving data across and replacing the 8TB WD with my original 10TB drive? I don't want to have a RAID Array....I like to live dangerously 🤣 I have attached a screenshot of how I have things currently set up. I hope this makes sense? I'm fairly new to Unraid and never had to do this before, so please try to be sympathetic to this 61yr old PC tinkerer.

Moving single parity drive from Parity 2 slot to Parity 1 slot

Last year or so I went through the process of changing my Parity drive to a larger one to allow me to upgrade array disks to larger sizes. This process resulted in having an empty Parity 1 slot and instead using only the Parity 2 slot. I'm now wishing to move this parity drive from Parity 2 slot to Parity 1 slot. What is the cleanest process? To clarify I only have one parity disk. Alternatively, is that required? I read about Parity Q computation on P2 slot being more computationally expensive than Parity P on P1 slot, and disk order mattering when using P2. This whole potential issue was only brought to my attention when I started monitoring Unraid with Pulse.

Cache drive getting disabled, no detail in logs?

A few weeks ago, my Samsung SSD cache disabled. I moved an already-mounted SSD to act as cache, and pulled this one. Testing found no issues, so I planned to reformat/restore it, thinking it was a transient issue. I did that yesterday, and overnight it was disabled again. Specifically, per syslog: As of 4AM ET, mover ran and no errors reported As of 4:40AM ET, Fix Common Problems ran and reported "Error: cache (Samsung_SSD_990_PRO_2TB_S7KHNJ0X312749R) is disabled" I've run the full SMART test and attached it here, along with the diags from before that full test. That came up clean, as well. The only other thing I could find is below, in my dmesg: [66672.535303] XFS (nvme0n1p1): Mounting V5 Filesystem 00ecfc48-3876-4328-95b5-1615bfbef65e [66672.541689] XFS (nvme0n1p1): Ending clean mount [152151.312270] block nvme0n1: the capability attribute has been deprecated.Ideas on what I'm missing here, welcome. Thank you. morningstar-smart-20260909-0626(1).zip morningstar-diagnostics-20260909-0630.zip

"Device" is missing in docker configuration

Hi, I try to add an device to a docker container but I can't find it under the options: What is the right one to choose? In german it should be "Gerät" but none of these does fit?

[7.3.2] Unstable system for the about the entire year of 2026

Hello all, I'm looking for some ideas or 2nd pair of eyes to see if I can figure out an issue on my system in 2026. See below for all the details and attachments, I've tried to already figure out a lot but a bit at a loss for the moment. System is a Supermicro X10DRi Intel Dual CPU Xeon E5-2620 some details: Dual Power 1200W supply 80 Plus Titanium Dual SFP ETH card[Mellanox Technologies MT27710 Family [ConnectX-4 Lx]]: 1 in use as main to the switch Dual onboard ETH: 1 in use as bonded backup. 128 GiB DDR4 Multi-bit ECC (Depending on the run its idle: ~ 20GB, on more activity ~60GB.) 1 Zigbee USB device plugged in and available in a docker. Updated edit: SAS9300-4i controller (Temp while parity checking 65 degrees) Unraid Bootflash is on USB inside on the motherboard plugged in. (only 10% in use) IPMI/BMC available. No video card in the system, other than the mother board, so no virtualization of this component. VM's but these are pinned to CPU's IPMI is controlled by IMPI plugin from Unraid. I have a system running Unraid that is unstable mostly since start of 2026, system ran fine for pretty much entire 2025 and before. The flash written system logging doesn't show anything specifc. Sep 8 12:46:58 Mountain kernel: md: recovery thread: exit status: 0 Sep 8 12:59:12 Mountain flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Sep 8 16:30:48 Mountain webgui: Successful login user root from 10.0.0.42 Sep 8 16:59:13 Mountain

623 Diskussionen eingesammelt seit 1 September 2026. Dieses Forum nach Stichwort beobachten →