JohnBee

Yes, same file, in same location (verified)
That said, I restarted Unraid, and the problem went away
 
 

Thanks for the info, will look at faster solutions

I would like update this thread and post that I have identified the cause of this behaviour as well as found a suitable solution.

The first thing to note, is that this particular behaviour seems specific to assigning relevant paths and directories to alternative devices - such as nvme's or SSD drives
The second to note is that the Docker and VM services, will continue to point to their original paths until these are either stopped or cycled.

That said, and should this not be done, the respective Docker and VM services can potentially report false information, and as a result of polling the now original paths and folders.
And so, the solution to this, and at this time, appears to that of cycling both the Docker and VM services after the changes to their respective devices are made.

- hope this helps and thanks to JorgeB, for following-up on this

PS. it would seem that the ideal scenario on this, is that of cycling said services following devices changes