trurl

May not be as bad as you think. Best case, you disturbed the connection to disk5 when replacing disk3, and fixing that before restarting the rebuild will result in complete success. Might even be possible that the disk you replaced wasn't bad either but something else caused it to be disabled. Or it could indeed be bad due to all the neglect, though it would be unlikely to lose more than just that 1 or 2 disks. We won't know without more information than just those screenshots. Absolutely no point in continuing with that rebuild with all of the disk5 errors. Stop it and see if you can get diagnostics.

By "key", do you mean a USB flash drive? Or do you mean you purchased a license key for Unraid?

What do you get from the command line with this? ls -lah "/mnt/user/Movies/English Movies/50 First Dates (2004)" and this? ls -lah "/mnt/user/Movies/English Movies/50 First Dates (2004)/50 First Dates (2004)"

Sounds like you must have created a recursive link somehow. Post a screenshot of the folder contents from MC.

Diagnostics already includes the syslog since the last reboot, so unless you are posting an additional syslog captured by Syslog Server there is no need to attach syslog with diagnostics. Looks like something is still expecting to access something related to that ipmi plugin. Close all browsers on all computers that may be accessing your server, including any mobile apps. Try again after clearing browser cache. It is really best if you work with your server from a single tab on a single browser on a single computer, otherwise the webUI can get out of sync between the different tabs/browsers/computers.

Are you still having problems? If so post new diagnostics

👍

If they were non-correcting checks then parity would not be changed.

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post

Have you seen this? https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

Looks like you are running Nvidia Unraid build. Does it happen with the standard Unraid build?

I don't know how to interpret the SMART report that controller is passing. Maybe someone else will reply.

Looks like 2 of these: https://www.harddrivebenchmark.net/hdd.php?hdd=KINGSTON SA400S3&id=13973

Your Media share is cache-yes. However, there are currently no files for that share on cache. Did you change it to cache-yes after that transfer speed test? Or did mover run since that transfer speed test?

Unrelated, but your system share has files on the array.

From your screenshot, I assumed you were transferring data from the Downloads share to the TV Shows share. But your diagnostics says you don't have any shares by either name. What are the paths of your source and destination?

Until we see diagnostics no reason to assume the destination share is even cached. And the screenshot looks like a round trip over the network thru his PC.

Also Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post. Then Setup Syslog Server to get your logs saved somewhere you can retrieve them after crash: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post

system share is all on cache now. You had your docker image set to 30G. That is somewhat larger than I usually recommend (20G), but not something I would normally comment on. Did you ever have problems filling it? After enabling docker, you can get your dockers back just as they were using the Previous Apps feature on the Apps page.

According to ethtool you have no ethernet connected

Setup Syslog Server so syslog will be saved somewhere you can get it after rebooting: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post. If you make a mistake with your Network Settings then of course you can make your server unreachable. There are often 2 settings in the BIOS that are needed to get full virtualization support.

Unraid only requires a clear disk when adding a disk to a new slot in an array that already has valid parity. This is so parity will remain valid. Some people use preclear for testing disks, but Unraid does not require clear disks in your situation.

Maybe a browser refresh would have gotten it sooner.