splendidthunder

Yes. Why does unraid not just "pause" the disk sort of. where it will keep the drive in the array and use it still , skipping the failed write and retry in 10 seconds. If that fails 5 times (50 seconds of retry) than show a warning that the write failed. Let the user decide if they want to continue with the potential of data loss, show them hey you may have a hardware problem and pause the array state. My main job is perfromance engineering for a fortune 500. I use disks daily and interact with large disk arrays. This issue genuinely boggles my mind. As does not saving syslogs on system failure. I had to setup a syslog server for this specifically. limetech knows this software is not going on enterprise hardware in most cases , bad sata cables , crap power and faulty hotswap disk cages are common, they should have accounted for this possibility and have some sort of mechanism to deal with it instead of relying on customers to trouble shoot for days trying to correct it. Even though in every case my hardware was ok , i still ran into the issue which is another story. I feel like the current implementation was just , kick the disk and let the customer figure it out. This issue is not just us 2 users complaining , i see it on reddit alot. Users complain of CRC errors , Fix it and low and behold that same user months later with the same issue. They are replacing and rebuilding on a potential problem that may not even exist.

I have already done this with support , 3 different systems. Everytime support said it was hardware , i replaced everything including power , cables , controllers. This is not my normal account , i cannot remember which email i used on here before. Support wants to blame hardware for everything. They had no interest in what i had shown them. on 6 of the customer systems , we swapped to truenas with the hardware in place. All backups have been working without any errors (including CRC) for a year and a few months now. So to blame hardware (yes im very aware UDMA CRC errors are hardware related) is just the easy way out. The problem could be how unraid reads smart data , how it registers there is infact a CRC error or how it handles what happens when a crc error happens. Either way im not going to be a QA for unraid , Thats just unacceptable. I guess customer support is right though , i had 12 total servers in the feild doing backups of data and they all had hardware problems causing CRC errors ( 3 different batches of different hardware too , different disks in all of them (customer supplies the disks new). Does not make sense , the hardware is fine , truenas has proven that.

thank god someone said this. IT NEEDS to be said. Since 6.** this issue has existed. its almost out of control now. i have done around 15 builds in the last 2 years. All exhibit crc errors and kicked disks every few months. Hardware is all fine , has been swapped , disk controllers swapped, cables ,power everything. Issue still exists. I did an experiment with 2 builds 1 intel 10400 cpu Adaptec 71605 , 1 with ryzen 5600g and LSI 9201. 4 8 TB disks in each. Ran them until the inevitble CRC errors happened(60-70 days). 1 had a kicked disk. Wiped both machines and put Truenas core on them. They ran for 6 months without any errors , no CRC errors nothing. (touching nothing in the systems , they were still in the rack) Sure there will be people saying its cables , power ect. i never have issues or the like. I have been using unraid for 14 years now. I have never had so many problems as i have had in the last few years. I have never bought so many HBA's and packages of SAS cables in my life to try to fix a problem.