trurl

On mobile now so can't look at Diagnostics. There isn't anything called "repair array ". Can you can explain that part better?

169 IP just means you aren't getting DHCP. /dev/sda isn't necessarily /boot. Try another USB port preferably USB2.

Maybe you have a more general docker setup issue. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread. If it appears you have an issue not specifically related to this container I may split these posts into their own thread.

Latest beta has a different alignment for SSDs which may improve performance with some devices.

Many are already using latest beta. In addition to new kernel there are some very interesting new features. I seldom hesitate to run betas because I have a good (enough) backup plan.

You should follow the correcting check with a noncorrecting check to make sure there are no errors. If there are still errors then you may have some hardware problem. Also, those lines you posted from the log were about your cache and have nothing to do with the array or the parity check. Possibly you will still have something to deal with there as well.

The disk is disabled so it needs to be rebuilt. Unraid disables a disk when a write to it fails. But that write still updates parity, so that write can be recovered from a rebuild. After a disk is disabled, Unraid doesn't use the disk anymore. Instead it emulates the disk using all other disks from the parity calculation. The emulated disk can be read, and it can also be written by updating parity. So any subsequent writes are also in the array and can be recovered. The actual disk itself is out-of-sync with parity. The only other possible course of action would be to New Config and rebuild the parity disk instead. But since the data disk is out-of-sync and missing those writes, it really makes more sense to rebuild it.

From diagnostics it looks like that drive is still on 4K alignment though so should be OK with 6.8.3. Doesn't look like anything wrong with drive, and cache is mounted. Let's see if @johnnie.black has anything to say.

yes. Assuming the controller presents the disks as before the drives should be recognized so nothing to reconfigure there. If you have any VMs using passthru might need to tweak those. Many of us have done this. Here is my recent rebuild thread:

Not sure what you mean by "re-import". If the original is the same size as the replacement then you should be able to rebuild to the original instead.

Latest beta is kernel 5.7

Have you ever used one of the Unraid 6.9 betas?

Nothing apparent in those. 2 FAQs that might be relevant:

The main thing I was hoping for more clarity on was your question. Did you replace disk8 with a different disk to begin rebuild? Or were you rebuilding to the same disk? What exactly do you mean by "just put it back in the system"?

Maybe diagnostics would help clarify and possibly show other considerations. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

Syslog snippets are seldom sufficient. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

Do you have the Unassigned mapped with slave access?

Prefer is the correct setting and Yes is most definitely the wrong setting. Probably After you get Cache fixed post new diagnostics and we can work on that.

Maybe diagnostics would answer some questions and let us see if anything else needs to be considered.

If the disk is actually disabled then Unraid isn't using it until rebuilt anyway. And I don't think I would bother trying to rebuild it to itself. Of course, while disabled, any access to that disk will be emulated by reading all other disks. And unless you have dual parity you don't have redundancy either. Do any of your other disks have SMART warnings on the Dashboard?

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

Have you done memtest?

/boot

Rebuild will start over from beginning.