Timonator

Hi all, I had issues with NextCloud AIO, which was down and did not start anymore. So I updated the containers in the hopes it would work, but it didn't. The error messages also suggesting stopping the array and restarting, but ever since my entire docker does not run anymore. I also tried then updating Unraid, but not success. The log shows constant crashes of the API log Apr 18 11:45:18 UnRaidRack unraid-api[3276242]: ⚠️ UNRAID API crashed with exit code 1 Apr 18 11:45:20 UnRaidRack unraid-api[3276746]: ✔️ UNRAID API started successfully! Apr 18 11:45:21 UnRaidRack unraid-api[3276746]: ⚠️ Caught exception: connect ECONNREFUSED /var/run/docker.sock Apr 18 11:45:21 UnRaidRack unraid-api[3276746]: ⚠️ UNRAID API crashed with exit code 1 Apr 18 11:45:23 UnRaidRack unraid-api[3277198]: ✔️ UNRAID API started successfully! Apr 18 11:45:24 UnRaidRack unraid-api[3277198]: ⚠️ Caught exception: connect ECONNREFUSED /var/run/docker.sock Apr 18 11:45:24 UnRaidRack unraid-api[3277198]: ⚠️ UNRAID API crashed with exit code 1 Does anyone, have an idea what is going on with my Docker service? Kind regards unraidrack-diagnostics-20250418-1147.zip

Thank you for confirming, then it will go back to Seagate.

I recently added 2 IronWolfPro drives to my array. They are both 16TB. Some days ago 1 of the drives was disabled, I am guessing during the parity check and has a bunch of errors displayed on it. When searching a bit online I found that there is an issue with LSI cards and Ironwolf on unraid. So I Performed the steps to disable low current spin-up and EPC. Now I added the drive back to my array and it is accessible again. But the drive is already showing some S.M.A.R.T. errors. I hopefully added the correct diagnostics to the topic. I ran a short SMART self test which is also attached. Is my drive already toast? There was no data written to it yet. Or is there some other issue with IronWolfs that I am not aware of. Also is this reaon enough for a RMA? BeforeHDDFirmwareChange.zip AfterHDDFirmwareChange.zip unraidrack-smart-20250207-1949.zip

Currently I don't have a SAS HBA, I am looking into getting one. Does it matter if the HBA is flashed to IT-mode or not? Do you think there will be performance impact using the parity drives on the expander and how big of an impact vs wiring them directly to the motherboard/HBA?

Hi all, I am currently using a SM X12STH-SYS with a Xeon E-2378. Currently I only have 5 16TB exos drives with 1 being used for parity. To future proof, I got a SM chassis 846, which houses 24 hot swap drive bays in the front. Sadly though, I found out it had a SAS-846-EL1 backplane, which does not support drives over 2TB. So I have ordered a SAS3-846-EL1 and am still looking for a SAS3 HBA to connect it to. My motherboard has a miniSAS connection, but I don't think it supports the expander configuration. Speed will be divided between the 24 drives, as far as I can find online. Which would mean 4x12Gbps, which is about 6GB/s, about 250MB/s/drive. The drive read/write are around 250-260MB/s anyway, so I guess I am not loosing any performance. Do any of you know of negative performance impacts of putting the parity drive(s) on an expander backplane? Or is it much better to connect the partity drives seperately to a SATA connection?