[HDD to SSD "the disc must be as big or bigger than the original" Error]

Thank you everyone for your help; I will start a new thread with I think a much simpler question!

[HDD to SSD "the disc must be as big or bigger than the original" Error]

At the absolute most raw level, couldn't I add the SSD to the array, rebuild parity, then remove the HDD and rebuild parity again, with no data loss?  I know that is a super ham-handed way to approach the problem, but wouldn't it work, given none of the drives are greater than half the size of my parity drive?

 

I'm asking about alternatives because I do not see any "Copy" function in any of the menus that would enable me to copy the HDD to the SSD, so I'm guessing it's something above my very low level of expertise.

[HDD to SSD "the disc must be as big or bigger than the original" Error]

46 minutes ago, trurl said:

No, just means copy. The Unassigned Device isn't part of the array. At this point the SSD in the array is empty. You just need to copy the data back to it from the Unassigned Device.

 

So I remove the HDD from the array, add the SSD to the array, mount the HDD as a UD, then copy to the SSD?

[HDD to SSD "the disc must be as big or bigger than the original" Error]

2 minutes ago, trurl said:

SSDs in the parity array cannot be trimmed.

Apologies, I do not know what that means.  Did I refer to that in one of my steps?

[HDD to SSD "the disc must be as big or bigger than the original" Error]

Yikes, that sounds scary...so I'm not missing anything, is it:

1. Shut down array.
2. Remove HDD, add SSD, reboot array.
3. Add SSD to array via New Config tool.
4. Rebuild Parity - I'm not technical so forgive me, but why wouldn't parity write to the new SSD at this time?  I think this is the part of how parity works that confuses me the most; can't the array see the SSD as a new drive replacing a dead drive and use parity plus the other drives to rebuild?  Or is this where the start sector issue becomes the issue?
5. Format the SSD - I assume in the dashboard?
6.  Mount HDD to the array via Unassigned Devices - though if I'm already at my max SATAs I'm blocked here...
7. Copy data back, meaning, rebuild the array again?
8.  Shut down, remove HDD, reboot?

 

[HDD to SSD "the disc must be as big or bigger than the original" Error]

I've been using unRaid since 2012 and have swapped out countless drives over that time.  My 4TB WD HDD hard drive is on the way out, so I decided to replace it with a new Crucial MX500 SSD, others of which I've had in my array for years.  For some reason I'm getting an error that "the disc must be as big or bigger than the original" even though both are 4TB.

Is there any way to have my unRaid OS work through this?  In all these years and swaps I've never encountered this before.

[Windows 10 Mapped Drive Missing After Plex Update]

I did see this in the log, with .34 being my local machine:

 

Mar 1 10:39:11 Tower rpcbind[20815]: connect from 192.168.4.34 to getport/addr(mountd)
Mar 1 10:39:11 Tower rpcbind[20816]: connect from 192.168.4.34 to getport/addr(nfs)
Mar 1 10:39:11 Tower rpcbind[20817]: connect from 192.168.4.34 to getport/addr(nlockmgr)
Mar 1 10:39:11 Tower rpc.mountd[1786]: refused mount request from 192.168.4.34 for /unVideo (/unVideo): unmatched host
Mar 1 10:39:11 Tower rpc.mountd[1786]: refused mount request from 192.168.4.34 for /unVideo (/unVideo): unmatched host

[Windows 10 Mapped Drive Missing After Plex Update]

I had to move to a different PLEX docker last night due to the depreciation of the one I was using.  I moved to the official Plex docker. All seems fine with Plex this morning, but out of nowhere I can no longer access my server -- I had it mapped as a network drive in Windows 10, but today, poof, gone, and doesn't even show up as available to re-map. I can't find anything online that explains if this is due to Windows, Plex, unRaid, or all of the above just being inscrutable at my expense. Any thoughts?