n1c076

ps I recommend everyone with an asm1166 controller to update the firmware as explained here: https://docs.phil-barker.com/posts/upgrading-ASM1166-firmware-for-unraid/ the performance of the controller improves significantly

the new controllers solved the problem, no more errors of any kind, another confirmation that multipliers are evil thank you for all! 👍

just ordered two asm1166 6 ports to replace the 10 ports one with multiplier 🤞

interesting, we have in common an hw migration while keeping the array.. Inviato dal mio iPhone utilizzando Tapatalk

ps thank you very much Jorge and Decto! 👍

ok apparently I found how to spend my free time in the next few days.. I have to understand if I can keep this controller in my build and for my use case or if it's better to change it.. for sure it didn't was a good beginning.. 😅

In any case, this new build is giving me some thoughts.. some random ata error o sata link reset, frequently when spinning up, I fear this cheap data controller and its sata cables was not a good idea https://amzn.eu/d/dIIvyws

Ok, I will add some data to the array and start a new parity check without correction, I'll let you know 👍

same 5 sector: Feb 18 05:57:18 micronas kernel: md: recovery thread: P corrected, sector=3519069768 Feb 18 05:57:18 micronas kernel: md: recovery thread: P corrected, sector=3519069776 Feb 18 05:57:18 micronas kernel: md: recovery thread: P corrected, sector=3519069784 Feb 18 05:57:18 micronas kernel: md: recovery thread: P corrected, sector=3519069792 Feb 18 05:57:18 micronas kernel: md: recovery thread: P corrected, sector=3519069800 what do you think Jorge? It's the parity hdd or another one?

It's a new server and I've done many burn in and memtest cycles without any problem, but ok I'll try another parity check with correction and I'll let you know. Thank you Nicola

Hi All, I have a parity correct check with 5 errors and the second check with no correct lists the same errors: First correct check Feb 16 04:21:08 micronas kernel: md: recovery thread: P corrected, sector=3519069768 Feb 16 04:21:08 micronas kernel: md: recovery thread: P corrected, sector=3519069776 Feb 16 04:21:08 micronas kernel: md: recovery thread: P corrected, sector=3519069784 Feb 16 04:21:08 micronas kernel: md: recovery thread: P corrected, sector=3519069792 Feb 16 04:21:08 micronas kernel: md: recovery thread: P corrected, sector=3519069800 second no correct: Feb 17 04:00:59 micronas kernel: md: recovery thread: P incorrect, sector=3519069768 Feb 17 04:00:59 micronas kernel: md: recovery thread: P incorrect, sector=3519069776 Feb 17 04:00:59 micronas kernel: md: recovery thread: P incorrect, sector=3519069784 Feb 17 04:00:59 micronas kernel: md: recovery thread: P incorrect, sector=3519069792 Feb 17 04:00:59 micronas kernel: md: recovery thread: P incorrect, sector=3519069800 I have a disk with smart error, current pending sector: SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 0 3 Spin_Up_Time POS--K 165 164 021 - 6750 4 Start_Stop_Count -O--CK 098 098 000 - 2902 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 200 200 000 - 0 9 Power_On_Hours -O--CK 001 001 000 - 83169 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 290 192 Power-Off_Retract_Count -O--CK 200 200 000 - 188 193 Load_Cycle_Count -O--CK 001 001 000 - 1858898 194 Temperature_Celsius -O---K 130 102 000 - 20 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 1 198 Offline_Uncorrectable ----CK 200 200 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 83 No other smart error, any advice? Nicola micronas-diagnostics-20230217-1114.zip micronas-diagnostics-20230216-2031.zip