darkside40

So its not the Ram and it is not the Parity Disk. I replaced it beacause i thought: The failures always appear around 95% (would be great if they would begin at 1% than i could save much time) maybe the failure is somewhere at the end of that disk if its checked sequentially. Next will be the controller.

Okay. I think the first and easiest thing now it to replaye the memory, althought Memtest found no error. If that does not solve the problem i will replace the AAR1430 with an ECS06 Controller, hopefully that does not makes such problems like the last ASM1166 i tried couple of months ago. If that does not help, yeah than i have to check every single disk.

Just to be sure: all the time i change something i have to do a correcting and after that a non correcting run? Only that way i can verify i found a solution.

I can imagine. Did a XFS Check on all disks, no issues. Had a look at all Disk's smart Values only one disk had 17 UDMA CRC Errors, maybe thats the cause.

Okay took me a time had some really busy days. So i exchanged all the Sata Cables at first. Run a first correcting Parity check that 1839 errors, did a second check (non correcting) some hours later that found 978 Errors: So i dont think it was the cabling. Next would be the controller i thing with the same procedure. I also attached the diagnostics, so maybe someone with more experience than me could have a look at them and maybe find something obvious. htms-diagnostics-20231026-0714.zip

So i assume the first run must be a correcting Parity check, so that the second run should not find any errors more.

Okay i did 2 Memtest runs now. No Errors? What would be the next step? I have an alternative controller Card (Silverstone ECS06) lying around.

Yes i am sure. Okay than i will try that tomorrow, because i have to hook up a monitor or that.

Hi there, i am doing a parity check which shows my 213 errors till now. The last one also had errors but i thought that was because of an unclean shutdown before. Is there any way to see if there is any disk faulty etc? They are mounted without problems, so i dont think there is a smart problem etc. htms-diagnostics-20231011-1808.zip

Fix Common Problems will not solve it because of what i have read it will only trigger if the FS is unmountable. This will only occur if you start/stop the array, which isnt the case so often. And in my case even with the metadata corruption the FS was mountable. Also a Smart Check would have not captured the error, the disks are fine, and no they are not 10 years old. Would a regular parity check capture the problem? Dont know but in worst case you carry around the metadata corruption for four weeks before you know, if you do them monthly. On the other hand the solution would be simple, include something like the syslog notification script directly into unRaid. I mean the solution is there.

4 weeks no reaction by @limetech etc.

Yeah but you could avoid carrying the corruption around for an undefined amount of time if you know about it by simply monitoring the syslog. Like i said the hdd mounted fine in my case so thats not an indicator, and i think most people do a parity check approx. once a month because thats an operations which stresses all the disks in the array.

Three weeks, a major problem and no official reaction. Limetech really cares about the data of its users 👍

@limetech does any of the official Unraid developers ever take a look in the feature request section?

Thanks for the hint with the Syslog Notify Script, didnt know that this exists till now. On the other hand i ask myself why such a useful function is not included in unRaid. At least in my case it didnt work that way. Stopped the array with the metadata corrupted FS, rstarted the array without repairing it and unRaid did not complain. Wonder why there is no word of any official unraid developer till now. Thats a real problem.

Yeah that would be a good idea!

And thats a serious problem. I am still reconstruction which files got lost etc. I know a Raid is no backup, that correct, but if a filesystem error accours a want to be informed of that.

Thats the way i do it with Borg Backup. The only bad thing is if files vanish because of such a corruption an you are not notified of it.

Great seems that i lost some files. Just a quick questions, i think unraid is working on block level. So the parati also reflects the FS curruption, right? So a rebuild of the Drive would be useless.

Yesterday i had a problem where the XFS Filessystem of one of my disks went bad. There was some metadata corrupted which i have only recognized because there were files missing and directory listings didnt work correctly. When i have looked in the syslog there were some red lines telling me i have to use xfs_repair to solve that problem. That worked besides of the extra work i had fishing out my files out of the lost+found folder. What i thought is strange is that i didnt get a notification of the bad state of the fs. So i could have maybe worked on for days without taking the neccessary measures. Is there any way to implement a notification when something like this occours?

Okay than i get you wrong. Maybe something that should be considered because it is something that is present in the syslog.

Didnt get any althought Notifications are working correctly. But the drive also was not labeled faulty by unraid.

Hi there, is it normal you dont get a notification if there is a files system corruption in unRaid? Had some Problems yesterday. Wanted to move some Files on the CLI and the listing of a folder didnt appear. Lookes at the Syslog and there were some red lines telling me about a metadata corruption on a drive and that i had to run xfs_repair. Okay did that, had a lot of files and folders in lost+found and quite a bit of "fun" partially restoring the from backup or move them back to their originally space. What wonders is that i didnt get a notification about that quite big issue. Normally i get notifications for everything.

Could you please add the function of the S3 Sleep Script into the Core of unRaid. Althought it might not work for everybody, it would be a great addition for all users which live in Countrys other than the US where energy prices are much higher and users which care for the environment who think it is simply dumb letting a server run 24/7 when not needed. See also here:

So constant gambling upgrading your server.