trurl

Put your flash drive in your PC. Delete the file config/network.cfg so it will go back to using defaults, which includes DHCP. Why do you want to change the IP of anything on your LAN?

That is not a local IP. Don't put your server on the internet!!!

SMART for parity disk looks OK but that doesn't always tell the whole story. You might run extended SMART test on the disk.

No. In this situation, you would use the invalidslot command to tell Unraid to rebuild disk7 instead of rebuilding disk1. But unfortunately disk1 doesn't look very healthy. I am going to try to get another opinion from @johnnie.black and see if he has a better idea. Maybe trying to clone disk1 and using the clone for the rebuild? He is probably asleep now so wait a few hours.

SMART for all attached disks should be in diagnostics. So it isn't responding. The connectors should sit square on the connection with no tension in the cable that might disturb that square connection. And don't bundle SATA cables. Post new diagnostics.

Part of your system share is on the array. Shouldn't cause the problem though. Do you have any VMs? What other dockers do you have?

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

No SMART for parity, apparently not connected. Check all disk connections, power and SATA, both ends, including power splitters. Then post new diagnostics.

Post diagnostics instead of syslog. Diagnostics contains syslog and a lot more about your configuration. And please don't convert simple text files into pdf. Simple text files are so much easier to work with. Tools - Diagnostics, attach complete Diagnostics ZIP file to your NEXT post.

First time you've mentioned removing drives. You should explain what you have in mind so we can advise further.

Shouldn't have slowed that much. Post new diagnostics.

If the disk is disabled then it is being emulated, but the emulated disk is unmountable. If it is not disabled then it is not being emulated. Disabled/emulated are different than unmountable and you can have either or both conditions independently. If you had posted your Diagnostics we wouldn't have to guess whether the disk is disabled/emulated and whether your Unraid version has the XFS repair bug. Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

If your last parity check had zero errors then it should be fine. If it didn't why didn't you do something about it then? Exactly zero parity errors is the only acceptable result.

If you do what you are suggesting, you will have to rebuild parity after you remove the 2TB, so might as well just do the "easiest way" and rebuild the data disk.

I have split your post and its replies into its own topic. Please don't hijack.

You are having flash drive problems. Put it in your PC and let it checkdisk. Do you have a current backup of flash? If not, be sure to make one when you have it in your PC. And be sure to boot from a USB2 port.

Maybe that's why I never noticed anyone rebuilding that way, because they never had a question about how to start the rebuild.

Connection problem with parity. Check all disk connections, SATA and power, both ends, including any power splitters.

Not a question of whether they changed. Just trying to get a more complete picture. You didn't tell us anything really about your hardware, and rather than pulling teeth to get that information, diagnostics makes it easier for everyone. And other things a user can do to their configuration can lead to problems. Many things can get diagnosed by looking at things other than syslog, If you had been running Ryzen, for example, I would have had other suggestions for that since there are some tweaks that can help with those CPUs and crashes. yes

Let the rebuild finish then post new diagnostics

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

You may have to temporarily configure Krusader docker as the root user by changing PUID and PGID to 0

Your syslog is being spammed with these once per minute: May 15 07:49:55 UNRAID s3_sleep: Disk activity on going: sdc May 15 07:49:55 UNRAID s3_sleep: Disk activity detected. Reset timers. I'm sure I have looked at other syslogs where a user was using s3_sleep plugin, but I never saw that behavior. What happens if you uninstall that plugin?

Why? While the disk is disabled, it is not used at all. It is emulated by the parity calculation by reading all other disks. So, moving files from the disk is actually working all of the disk harder than usual, and your array is currently unprotected since you only have single parity and a disabled disk. Also, the whole point of rebuilding is to get the disk back with all of its data intact. So, you are only making your system work harder, and you are unprotected until the rebuild is complete, and you are delaying that rebuild. Your data is actually safer if you go ahead with the rebuild instead of moving data from the emulated disk to other disks in the array.