wickedathletes

Running it now. How do you know if the one run on 1/13 did not have write turned on? My scheduler is set to run on the first day of the month but write corrections is on. So this must have been a crash, do those not write corrections by default?

I did pull my disk 4 some time around the 13th. Maybe its seated bad? I plan to replace it because its causing a bug in unraid, so rather than wait for a fix I figured I would swap it with another 8TB, rebuild parity, then take that 8tb drive a clear it (hopefully fix the bug) and replace a 4TB drive with that. I didn't start this because I had some work done to my home that required power outages, now that thats over of course I have parity showing issues so now I don't want to do it yet haha.

nothing... that is what is confusing me. Nothing in my logs that I can see either... I am running out of space, could a space issue cause something like this? I had 2 drives down to KBs left while something was trying to move to them. I am trying to replace a drive to add some more TB's but didn't want to do anything with my parity with errors in it.

1/2 was my last 0 errors run. 1/21 was my manually run check.

one was scheduled, the second I manually ran with "Write corrections to parity" checked. Both came back with the same number. All monthly checks have been 0 prior.

Write corrections to parity is checked. Do I need to check something else?

My last 2 parity checks completed but I noticed it: Finding 24047 errors Duration: 1 day, 19 hours, 21 minutes, 52 seconds. Average speed: 89.7 MB/sec Same error count, both checks. Any thoughts on what could be going on? hades-diagnostics-20210121-1803.zip

@limetech, just wanted to confirm the issue still exists in RC2: Here are diags from beta 30: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta30-available-r1076/page/2/?tab=comments#comment-10968 And here are the results of `hexdump -C -n 512 /dev/sdh` https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta30-available-r1076/page/3/?tab=comments#comment-10972 limetech said: Thanks, yes that explains it. Probably, with -beta25 and even earlier releases, if you click on the device from Main and then look

any chance this was resolved in rc2 @limetech? Here are diags from beta 30: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta30-available-r1076/page/2/?tab=comments#comment-10968 And here are the results of `hexdump -C -n 512 /dev/sdh` https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta30-available-r1076/page/3/?tab=comments#comment-10972 limetech said: Thanks, yes that explains it. Probably, with -beta25 and even earlier releases, if you click on the device from Main and then look at 'Partition for

@ljm42, yes, thank you for that!

@limetech, looks like this is still an issue for me in RC1 (beta 25 and back works fine, bug first discovered in beta 30), any update on a potential fix timeline? One of my drives shows "Unmountable: Unsupported partition layout."

@limetech, any chance this is fixed in beta35? I can't chance it as I wont have a recourse back to nvidia drivers since the old plugins are dead in the water so I don't want to change bumping up to then have to go back without a way to go to the nvidia driver sets. "Thanks, yes that explains it. Probably, with -beta25 and even earlier releases, if you click on the device from Main and then look at 'Partition format' it will say 'GPT: 4KiB-aligned (factory erased)' - that (factory erased) shouldn't be there. Will fix for next release."

that is definitely possible, but asking my brain to think back 3 years is a big task hahaha. It would have been one of 2 things, a rebuild of a disabled disk or a replacement of a 4TB disk as 3 years ago my server only had room for 8 drives.

This drive is functioning 100% fine in beta25 and earlier. 29/30 it wont mount. I honestly don't recall. I would say I have pre-cleared 90% of my drives but their was a time when I didn't have the ability to pre-clear due to a drive failure and no extra bays to use (aka I was under the gun). Its possible this was the drive that was not, but I doubt it. The drive is roughly 3 years old. Is their a way out of this state, or with this drive am I stuck on beta25 for eternity haha?

thank you and as always, you guys are the best!