jncunha

So I left the extended test running during the night and this is what I've got as a result: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 17359 - # 2 Short offline Completed without error 00% 17338 - # 3 Short offline Completed without error 00% 9732 - # 4 Short offline Completed without error 00% 9084 - # 5 Short offline Completed without error 00% 8634 - # 6 Short offline Completed without error 00% 8159 - # 7 Short offline Completed without error 00% 7416 - # 8 Short offline Completed without error 00% 6008 - # 9 Short offline Completed without error 00% 5376 - #10 Short offline Completed without error 00% 4656 - #11 Short offline Completed without error 00% 3912 - #12 Short offline Completed without error 00% 3046 - #13 Short offline Completed without error 00% 2318 - #14 Short offline Completed without error 00% 1922 - #15 Extended offline Completed without error 00% 1572 - #16 Short offline Completed without error 00% 676 - ATA Error Count: 6 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 6 occurred at disk power-on lifetime: 17332 hours (722 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 10 ff ff ff 4f 00 02:02:19.032 READ FPDMA QUEUED 60 00 38 ff ff ff 4f 00 02:02:19.031 READ FPDMA QUEUED 61 00 08 ff ff ff 4f 00 02:02:19.031 WRITE FPDMA QUEUED 61 00 e0 ff ff ff 4f 00 02:02:19.031 WRITE FPDMA QUEUED 61 00 08 ff ff ff 4f 00 02:02:19.030 WRITE FPDMA QUEUED Error 5 occurred at disk power-on lifetime: 17332 hours (722 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 40 ff ff ff 4f 00 02:02:13.319 WRITE FPDMA QUEUED 60 00 08 ff ff ff 4f 00 02:02:13.308 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 02:02:13.308 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 02:02:13.307 READ FPDMA QUEUED 60 00 e0 ff ff ff 4f 00 02:02:13.306 READ FPDMA QUEUED Error 4 occurred at disk power-on lifetime: 17332 hours (722 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 e8 ff ff ff 4f 00 02:02:07.911 WRITE FPDMA QUEUED 60 00 30 ff ff ff 4f 00 02:02:07.911 READ FPDMA QUEUED 60 00 98 ff ff ff 4f 00 02:02:07.910 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 02:02:07.910 READ FPDMA QUEUED 60 00 08 ff ff ff 4f 00 02:02:07.910 READ FPDMA QUEUED Error 3 occurred at disk power-on lifetime: 17332 hours (722 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 40 ff ff ff 4f 00 02:02:03.511 READ FPDMA QUEUED 61 00 20 ff ff ff 4f 00 02:02:03.511 WRITE FPDMA QUEUED 60 00 98 ff ff ff 4f 00 02:02:03.510 READ FPDMA QUEUED 60 00 30 ff ff ff 4f 00 02:02:03.510 READ FPDMA QUEUED 60 00 f0 ff ff ff 4f 00 02:02:03.509 READ FPDMA QUEUED Error 2 occurred at disk power-on lifetime: 17332 hours (722 days + 4 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 20 ff ff ff 4f 00 02:01:58.635 WRITE FPDMA QUEUED 60 00 40 ff ff ff 4f 00 02:01:58.618 READ FPDMA QUEUED 60 00 f0 ff ff ff 4f 00 02:01:58.616 READ FPDMA QUEUED 60 00 30 ff ff ff 4f 00 02:01:58.615 READ FPDMA QUEUED 60 00 98 ff ff ff 4f 00 02:01:58.615 READ FPDMA QUEUED Also the SMART report file in attachment. Thanks! ST4000DM004-2CV104_ZFN0WN16-20220422-0758.txt

Well it probably means that if I want to keep the Xeon and the ECC RAM I just have to get more money together. My system is working more or less for my needs but as soon as I do something that is more CPU intensive the whole thing just panics. Your CPU from the generation around 2019 right? I'm checking something between 2015-2019 and definitely the prices are just crazy. Is there any kind of UNRAID database with builds I could take a look to see what kind of components would fit my price?

I was taking a look at your system and I do like the idea of sticking with a Xeon CPU and ECC RAM. I was also checking your motherboard but in my country is super expensive ☹️. I need to find a cheaper solution where I can keep the CPU, RAM and motherboard combo around 500$ total. Maybe going a generation older?

My UNRAID server is running on an old system and I'm thinking about upgrading it. Currently these are the specs: Super Micro X8SIL-F Intel® Xeon® X3470 @ 2.93GHz 8 GB DDR3 Single-bit ECC For disks I have 16TB combined between WD Red and Seagate IronWolf and I have an SSD as a cache drive (possibly adding one more soon). I've been checking some videos and found out I could run Tdarr to convert my library and save disk space (my case is a Fractal Node 804 so I can fit a maximum of 10 3.5" disks). For this it would also be ideal to add a GPU (I have an MSI GTX 970 laying around that I could use but I can't fit it in my motherboard and I'm really not comfortable in using the Dremel to hack the x8 PCIe slot). Ideally the board would sit in a x16 slot for space reasons so I could still use the bottom of the case (on the motherboard side) for additional 3.5" disks. Also, my CPU seems to struggle with Sabnzbd when I'm downloading or unpacking. Most of the threads reach the maximum load and I'm not able to keep a constant download speed (I think it's not ISP traffic shaping) and if I'm downloading something it struggles to play a movie from my Android TV (without transcoding) at the same time. I like the Super Micro motherboards so far. Really can't complain. If I'm only direct playing a 4K movie on the Android TV it works very well and the CPU doesn't throttle. But I guess I can't stretch this system much more if I want to start converting my library and get more performance for Sabnzbd. I wonder if this upgrade would make sense or if I should look into optimizing what I download and maybe looking for alternatives for Sabnzbd. And if none of the later make sense, which motherboard (micro ATX), CPU and RAM combo should I go for. Any ideas?

Ok sounds good. Thanks for the help. I will do the extended test and post the result here. If I acknowledge the error in the dashboard and the number keeps climbing will I get the warning again?

Hi! One of my array drives is giving me the "Reported uncorrect" error. This is a normal Seagate Barracuda 4TB disk. I'm wondering if it's time to replace the disk or if there is something that can be done to fix the error (I know this might be a dumb question but I know zero of SMART errors and what they mean). I've attached the diagnostics .zip if anyone is able to help and point me in the right direction. Also I would like to start understanding what drives the decision of replacing the drive or to keep running according to the specificity to the SMART error. I think I started having this error after a power outage. I ran the SMART self-test (the short one) and it passes. I can try the extended one if that helps for the diagnostic. Thanks for the help! jonas-nas-diagnostics-20220421-1237.zip