As you most likely have noticed I have marked this as Pseudo-Solved. The reason for this is simple, I have not solved the core issue but I have solved my issue and can move on and this is how:
I added a completely new Linux Machine Instance in Virtual-Box. I then added 3 new vdi drives and used fsarchiver from there to rebuild the base (sda1) instance I test with. Booted perfectly. I then created two new vdi drives and one at a time tested each VSIDO fsarchive install and all booted perfectly without issues.
My assessment is that the old original files had some 'attachment' to the original V-Box Machine they were established on and was looking for something that just wasn't there anymore.
All it cost me was minute frustrations but in the end all is good again in the Dev world of VSIDO.
I added a completely new Linux Machine Instance in Virtual-Box. I then added 3 new vdi drives and used fsarchiver from there to rebuild the base (sda1) instance I test with. Booted perfectly. I then created two new vdi drives and one at a time tested each VSIDO fsarchive install and all booted perfectly without issues.
My assessment is that the old original files had some 'attachment' to the original V-Box Machine they were established on and was looking for something that just wasn't there anymore.
All it cost me was minute frustrations but in the end all is good again in the Dev world of VSIDO.