JorgeB

Please post the diagnostics: Tools -> Diagnostics

To get better visibility you should post on the appropriate support thread:

Those diags are just after rebooting, if Unraid isn't shutting down cleanly it should be saving diags to the logs folder on your flash drive, post those if they are there.

If the error continues to increase in another server it's likely the disk, but it's extremely rare, in fact I don't remember ever seeing it ever before, but of course it's not impossible.

Please post the diagnostics: Tools -> Diagnostics

Blue is normal for a new device, it's gonna be cleared and when done it will change to green, then you'll need to format it.

This looks more like a hardware problem, but did it start after upgrading Unraid? If you downgrade to v6.7.2 does it go away?

Post xfs_repair output for both disks.

Parity disk dropped offline so there's no SMART, check connections and post new diags, migh as well replace/swap cables with another disk to rule them out.

Yes, parity check should always be non correct unless sync errors are expected, like after an unclean shutdown, though not common parity can get wrongly updated (and corrupted) if a disk fails during a correcting check.

That's expected, once a disk gets disabled it need to be rebuilt, to the same or to a new one. No highlighted issues but it was a disk problem, you can see the UNC @ LBA error (read error) that happened: Error 2 [1] occurred at disk power-on lifetime: 37789 hours (1574 days + 13 hours) A little over a day ago, you should run an extended SMART test, these type of error can be intermittent, or even happen once or twice and then disk be fine for a long time, though they are never a good sign. You also want to keep an eye on this SMART attribute: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 197 051 - 54 If it keeps increasing there will likely be more errors soon.

Changed Status to Closed Changed Priority to Other

This looks more like a general support issue, please continue discussion here: https://forums.unraid.net/topic/86177-680-array-devices-blank-after-update/ I'll close this for now and will re-open if it really is a bug.

This looks more like a general support issue, but in any case we need the diagnostics (tools -> diagnostics), if you can't get the when the server becomes unresponsive see here to enable syslog mirroring to flash.

This looks more like a general support issue, but in any case we need the diagnostics (tools -> diagnostics), if you can't get the when the server becomes unresponsive see here to enable syslog mirroring to flash.

It is long, but it's normal for a large btrfs filesystem, since I use btrfs on the data disks some of my servers take more than 2 minutes to mount all the disks, and even more to unmount, kind of a pain, there's a patch/mount option to improve that, but it's not yet merged.

That's likely related to the timeout, since UD is aborting and not completing the mount.

And if that one works OK this one will also work: https://www.amazon.com/CREST-Internal-Non-Raid-Controller-Bracket/dp/B07ST9CPND/ref=sr_1_2?keywords=JMB585&qid=1576324877&s=electronics&sr=1-2 That would be great since there aren't really any good 4 port controller options, I might get one myself to test soon, though they are kind of expensive for 5 ports.

Split level overrides allocation method, set split level to "split any directory".

That looks more like a boot order issue, sometimes boot order can change with added devices, but note that trim won't work with the 9201 and mx500, so might as well leave it onboard.

In that case it should be fine, anyone who gets one please report back.

BTW, parity checks should be non correct unless sync errors are expect, or there's a risk of corrupting parity if a disk fails, though that didn't happen in this case.

Disk dropped offline, that's why there's no SMART, possibly because of the SASLP controller which is a known problem, but could also be a failing disk, power cycle the server, disk should come online then post new diags

Yep.

Changed Status to Closed Changed Priority to Other