Omid

Thanks for confirming and for the link! Now to try find the cable in the UK... 😅 And I totally agree with you regarding the motherboard. The build quality and finish isn't too far off ASUS's ROG series of motherboards, so I feel like it's using the same premium components. Its features, ports and PCIe configurations seem very appropriate for an Unraid build (e.g. no bifurcation when maxing out M.2 slots or the SlimSAS connector). My only qualm is that the big cooler I got for the 13700k, the Noctua NH-D15, will be almost touching the IPMI card if I put it in the top PCIe x1 slot (1mm gap; maybe less!). I'm pretty sure they will eventually touch after some time, because...gravity. I'll confirm that I received 2x 32GB Kingston (KSM48E40BD8KM-32HM) and am currently putting them through memtest where they were detected as supporting ECC.

@NAS-newbie Would you happen to know if your RAM is single-bit or multi-bit ECC? The Unraid Dashboard should show it on the Memory panel -- at least it does on my current Unraid server with DDR3: I'm re-platforming/upgrading the server and have the same motherboard with a 13700k. Trying to pick the best RAM from what I believe are the only options in the world right now for ECC DDR5. I'm not sure which is single/multi-bit. Micron/Supermicro? This part number seems a little different to the one you shared Kingston (SK Hynix) SK Hynix It'll also be awesome if you could fix the link to your SlimSAS cable in the OP 😉 Thanks in advance!

Bump 🙂

Unraid 6.11.5 Docker ✅ VMs ❌ I'm still using the /mnt/cache/.appdata approach for my appdata (rather than using a Share) and am happy to continue with this, but I'd like to move my appdata to a new NVMe-backed pool that I'll be creating. My appdata includes my Docker image. If I recall correctly, some folks had experienced permissions related issues when doing something similar. I'd like to avoid such a situation and am evaluating my options. My structure is: ---- /mnt/cache/ ---- ---- .appdata/ ---- ---- ---- apps/ ---- ---- ---- docker.img ---- ---- Share1/ ---- ---- Share2/ Am I okay to just stop Docker, rync the entire appdata directory, update configs and start the array? I could actually start the copy with rsync (excluding image) whilst everything is still running, just to get the bulk of it copied, and then switch off Docker and repeat the command (including image) to get the delta copied over [Option 1]. My appdata is only ~90GB but there are lots of small files which makes these operations slow. I am aware of the Share and Mover approach to do this, but wanted to avoid any risks (to system/share config) that might come if I convert this dot-folder to a Share folder on the cache drive. This incurs more downtime of Docker, as you'd have to wait for Mover to fully complete the move in one shot before starting everything up again. It's also a move and not a copy [Option 2]. EDIT: Use CA backup and restore and manually move my Docker image [Option 3]. EDIT: Could I convert my single 500GB SATA SSD Cache pool into a new AppData pool of two drives, with one 1TB NVMe? Let Unraid do its thing to mirror the data, then replace the 500GB SATA SSD with the second 1TB NVMe. [Option 4] Doh! My current Cache drive is xfs. Thanks in advance for any thoughts and inputs!

Same issue here. Plex randomly became unreachable and I now see the following in logs: [services.d] starting services [services.d] done. Starting Plex Media Server. Critical: libusb_init failed Created 1 week ago, but I know Plex has been working up until an hour ago. I tried a restart and also manually updated Plex (I auto update every 7d anyways). I see the same in logs. At this point, I'm hoping @Antivanity is correct here; it could be due to issues at Plex: https://status.plex.tv/incidents/jhn0629l9pzb Although I can't understand how such a DNS outage would affect the bootstrapping of the local server app...

It may be useful to share diagnostics to allow for better support (unRAID > Tools > Diagnostics) You have to be very unlucky to have had 2 bad drives like that. It's worth checking other things at this point. How are you running preclear and which version it is? Is this new drive connected to the same storage controller as existing drives? Tried a different cable/port? Side note: what's the specific model number of the drive? Unlikely to be cause of issue, but if this is a newly purchased drive, I think most recommend the CMR drives (WD Red Plus/Pro) and not the SMR drives. The lower capacity Red drives (e.g. 4TB) come in both flavours; e.g. WD40EFZX (CMR) and WD40EFAX (SMR) Aside from this issue you're experiencing, I recently went through a similar juggle of drives on an old unRAID server where I replaced my 2TB parity with a larger one and repurposed the old parity as a new data drive. Feel free to message me if you have questions at that stage.