trurl

No, I don't use AMD and didn't research this. The mentioned plugin can be installed from the Apps page.

I have flash drives from the "good" era and they have served me well for many years and counting. It is very easy to find threads on this forum from people who have had problems with their flash drive and difficulty finding a good replacement. And another thing that makes finding a replacement difficult is the fact that many flash drives these days don't even have a valid GUID for the license to be associated with. So some new, never used, flash drives are automatically blacklisted.

Other than that nothing seems to be wrong, rebuild hasn't completed yet. So what exactly do you mean by "disconnects"? Do you mean your disks are disconnecting. Or do you mean you can't access the webUI? I think you are making your hardware unnecessarily complicated, difficult to maintain and troubleshoot.

Automatic license transfer is only allowed once per year. After that, you have to get customer support involved for each license transfer in that same year. So even if you have flash backup, if you buy flash drives that fail more often than once per year then you won't be able to get your server going again without additional help.

Your syslog is being spammed with these Mar 29 04:56:10 Tower kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400900000). Mar 29 04:56:10 Tower kernel: [drm] UVD and UVD ENC initialized successfully. Mar 29 04:56:10 Tower kernel: [drm] VCE initialized successfully. Mar 29 04:56:10 Tower kernel: amdgpu 0000:1c:00.0: [drm] Cannot find any crtc or sizes Mar 29 04:56:16 Tower kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400900000). Mar 29 04:56:16 Tower kernel: [drm] UVD and UVD ENC initialized successfully. Mar 29 04:56:16 Tower kernel: [drm] VCE initialized successfully. Mar 29 04:56:16 Tower kernel: amdgpu 0000:1c:00.0: [drm] Cannot find any crtc or sizesand it repeats like that about every 3 seconds. Any idea what that is about?

Parity has no format so that isn't a consideration in this case. This is the only time I have ever seen a drive with more than the typical size, and less than typical isn't seen much anymore since everyone decided HPA was an unwelcome surprise.

Parity rebuild starts here: Mar 29 04:52:07 Tower kernel: md: recovery thread: recon P ...End of syslog is here: Mar 29 05:02:06 Tower root: Fix Common Problems: Warning: Syslog mirrored to flashWith no indication that rebuild completed, and obviously not enough time for that anyway. Did you take these diagnostics just after starting the rebuild? Post new diagnostics

I see, you were on the Settings page. Sorry

Otherwise, how could it prevent you from using that one license to boot multiple systems

The instructions are referring to the Settings page, not the Docker page. One of the items on the Settings page is Docker, which is where you make the settings for the Docker service, and will allow you to delete and recreate the docker.img

I went looking for other diagnostics with a 12TB drive. Those smaller drives seem to be typical, really odd the new one reports as being larger. I wonder if it really is? And why?

I wonder if this is the reason for the different sizes. And I wonder if we won't begin to see more of this with the higher drive prices these days.

Attach Diagnostics ZIP to your NEXT post in this thread.

If you can't get diagnostics for some reason, the result of this command line might tell us something: df -h /

I didn't have a SMART report for a typical 12TB handy for comparison. Are those other disks the typical size? Or is the new disk the typical size and the others are small for some reason? Is HPA still a thing?

Strange. Usually when this happens, it is because you are trying to replace parity with a disk that is smaller in some way. But in this case, it is the replacement data disk that is larger in some way and all the other data disks are the same size as parity. All disks seem to be the same model, only a single partition on each. And they are all on the same controller. Probably parity swap is going to be the way out of this as you suggest, but it might be educational if @JorgeB could take a look. Shouldn't be too many more hours before daylight in his timezone.

If you have to reboot, rebuild will have to start over. What data? All your data disks seem to have their data. Do you know of anything you are missing? Not enough information to know. That's why we need diagnostics taken when the problem occurs.

All New Config does is reset your drive assignments. No reason to think it would have any effect on your other problems. Attach Diagnostics ZIP to your NEXT post in this thread.

Attach Diagnostics ZIP to your NEXT post in this thread. Also, what do you get from command line with this? lsblk

You can rebuild disk8 and disk9 at the same time. Since emulated disk8 is already an empty XFS disk that is what rebuild will give you. Then you can copy the recovered data back to it.

Type @ followed immediately by the first few letters of the username then when the popup appears, you must select the username Like this @NewDay Also, when you "react" to a post (Like, Thanks, etc.) it also notifies the user.

Do you have an attached keyboard and monitor? You can also get diagnostics from the command line if the webUI isn't working. You should definitely take care of those Ryzen things in that FAQ.

All your data drives are mounting and show plenty of data. Parity has none of your data. SMART for parity looks fine. You can rebuild parity to that same disk. Stop the array, unassign parity, start the array with parity unassigned, stop the array, reassign parity, start the array to begin parity rebuild. While parity is rebuilding, you should see lots of writes to parity, lots of reads from all other disks, zero errors in the ERRORS column for all disks. If there are any problems, get diagnostics while it is still happening and post them.