channyceps

One of my disks show a SMART Error (UDMA CRC Error Count of 9) and this is what the error log shows: Is this a bad drive that needs to be replaced or is it just a cable problem? ATA Error Count: 9 (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 9 occurred at disk power-on lifetime: 6148 hours (256 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 -- -- -- -- -- -- -- 84 41 00 00 00 00 40 Error: ICRC, ABRT at LBA = 0x00000000 = 0 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 01 00 00 00 00 40 00 00:00:36.113 READ FPDMA QUEUED ec 00 00 00 00 00 00 00 00:00:36.112 IDENTIFY DEVICE e5 00 00 00 00 00 00 00 00:00:36.110 CHECK POWER MODE ec 00 00 00 00 00 00 00 00:00:36.105 IDENTIFY DEVICE ec 00 00 00 00 00 00 00 00:00:36.104 IDENTIFY DEVICE Error 8 occurred at disk power-on lifetime: 5692 hours (237 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 -- -- -- -- -- -- -- 84 41 00 07 8e e3 40 Error: ICRC, ABRT at LBA = 0x00e38e07 = 14913031 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 00 08 8a e3 40 00 6d+09:08:40.632 READ FPDMA QUEUED 60 a8 00 60 86 e3 40 00 6d+09:08:40.627 READ FPDMA QUEUED 60 58 00 08 86 e3 40 00 6d+09:08:40.626 READ FPDMA QUEUED 60 00 00 08 82 e3 40 00 6d+09:08:40.623 READ FPDMA QUEUED 60 00 00 08 7e e3 40 00 6d+09:08:40.618 READ FPDMA QUEUED Error 7 occurred at disk power-on lifetime: 5691 hours (237 days + 3 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 -- -- -- -- -- -- -- 84 41 00 bf 95 f3 40 Error: ICRC, ABRT at LBA = 0x00f395bf = 15963583 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 00 c0 91 f3 40 00 6d+08:38:54.559 READ FPDMA QUEUED 60 00 00 c0 8d f3 40 00 6d+08:38:54.555 READ FPDMA QUEUED 60 00 00 c0 89 f3 40 00 6d+08:38:54.550 READ FPDMA QUEUED 60 00 00 c0 85 f3 40 00 6d+08:38:54.545 READ FPDMA QUEUED 60 00 00 c0 81 f3 40 00 6d+08:38:54.540 READ FPDMA QUEUED Error 6 occurred at disk power-on lifetime: 5445 hours (226 days + 21 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 -- -- -- -- -- -- -- 84 41 00 fe ff 3f 40 Error: ICRC, ABRT at LBA = 0x003ffffe = 4194302 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 20 00 df ff 3f 40 00 00:00:45.369 READ FPDMA QUEUED 2f 00 01 10 00 00 00 00 00:00:45.369 READ LOG EXT 60 20 00 df ff 3f 40 00 00:00:45.044 READ FPDMA QUEUED 2f 00 01 10 00 00 00 00 00:00:45.043 READ LOG EXT 60 20 00 df ff 3f 40 00 00:00:44.739 READ FPDMA QUEUED Error 5 occurred at disk power-on lifetime: 5445 hours (226 days + 21 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 -- -- -- -- -- -- -- 84 41 00 fe ff 3f 40 Error: ICRC, ABRT at LBA = 0x003ffffe = 4194302 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 20 00 df ff 3f 40 00 00:00:45.044 READ FPDMA QUEUED 2f 00 01 10 00 00 00 00 00:00:45.043 READ LOG EXT 60 20 00 df ff 3f 40 00 00:00:44.739 READ FPDMA QUEUED 2f 00 01 10 00 00 00 00 00:00:44.739 READ LOG EXT 60 20 00 02 00 00 40 00 00:00:44.447 READ FPDMA QUEUED tower-diagnostics-20230914-2228.zip

So I'm looking to upgrade from my current set up (i5-3570k) as it's not able to handle a single 4k jellyfin transcode (I could be setting jellyfin up wrong but I'm pretty sure a 3570k is not adequate to transcode 4k to 1080p) and I want basically the cheapest CPU I could get away with for my use case. My use cases are mainly to host about 15-20 docker containers, do a single 4k to 1080p transcode (my movies are all mp4 in h264) and potentially 1 or 2 VMs althought unlikely in the near future. I'm currently leaning towards Intel over AMD (although I'm not fully against AMD I've just read intel QSV is good), and specifically looking at the 12100, 12500 and 13100. My questions are basically is there a significant benefit going for the 13100 or 12500 for the UHD 770? For one 4k transcode, is the UHD 730 in the 12100/13100 compared to the upgrade UHD 770 in the 12500? In where I'm located, the 13100 and 12500 have a 15% and a 45% over the 12100 respectively and I'm not sure if the price premium is justified.