Marius1085

Members
  • Posts

    8
  • Joined

  • Last visited

Marius1085's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Thank you very very much johnnie. The errors didnt show up and everything works fine. Seems to be the update to a newer kernel is all it takes.
  2. Can I see which files were corrupted? Those were all media files, so nothing too bad but if I could see which are corrupt that would be cool. As of now everything is fine and parity didnt show a single error. Ill tell you again in a few days to see if my parity is working fine.
  3. Another question. As the parity had some failures I also saw some errors on the main page for some of the other array disks. For example parity had 1300 errors and 3 other disks shared these 1300 errors. This only happened when cache wrote to array while parity was active. What do these errors say? Could it be that some files are corrupted? If so can I see which files are corrupted?
  4. Ok, Ill try upgrading and see how that works out. Ill let you know if that solved my problem.
  5. Hey, I searched the forum for fitting answers but cant seem to find any for my problem. I already changed the SATA cables, and precleared 2 times and ran an extended smart but UNRAID is still throwing errors at my face. So I dont know whats happening. I rebuild my parity drive for the third time now but still get parrity errors. First and second time I got parity errors when I wrote from my cache drive. On the third time the first write from cache worked fine but before my second scheduled cache write (I set mine to 0:00 everyday) I got parity errors again. I want to have a parity drive for extra security but Im at the point where I just want to change that to a data drive. I dont know where but I saw someone using turbo write? so in disk setting he changed turnable from auto to reconstruct write. Would this help? Please tell me what Ive done wrong and how I can fix it. I added the diagnostics logs. Thanks for your help quantumbreak-diagnostics-20200625-0017.zip
  6. Thank you very much. Makes total sense that LBA means the logical sector size but I wasnt quite sure. The usage now seems realistic.
  7. Yeah sure. Here is the S.M.A.R.T. report from the GUI. Let me know if you need anything else. hdd.txt
  8. Hey, I just stumbled upon the S.M.A.R.T. data of one of my HDDs and I am starting to worry if it could fail soon. It's a 8TB Seagate IronWolf NAS drive and the data that's worrying is the LBAs written and LBAs read aswell as Hardware ECC recovered. The drive is only 25 days old but way over what Seagate recommends. Seagate says on their site that this drive has a workload of 180TB/year. My questions are: Are the LBA datas wrong or should I worry? If so, how can I reduce the write and read? Can hardware ECC recovered be corrected by using ECC ram? Am I voiding my warranty by reading and writing more than Seagate recommends? I'm attaching my S.M.A.R.T. report data from DiskSpeed docker. Thank you for your help