virtualbox.org

Hi,
I have been using virtual box for many years and had no issues cloning vms on the local raid 1 ssd c drive.
However I’ve just set up a second raid drive (ide) and wanted to clone vm’s to that.

The cloning process completes without error, and the vm startups up - however it’s MySQL instance is corrupted and reports a disk error?

I also notice that the text in the terminal is yellow for these failed clones.

I can’t understand why the clone is failing, or why the text is yellow?

Regards
B

So when you clone a VM to the same SSD drive the original is on, the cloned VM's database is good. But when you clone to the other drive, the cloned VM's database is bad?

If so, what happens if you clone to the SSD, confirm the clone's database is good, then use Virtualbox's Move command to move the clone to the other drive?

Also, Virtualbox does not have any control over the color of the terminal text. If this color-changing terminal is inside the VM's OS, then it is the VM's OS that is changing the color, not Virtualbox.

Thanks Scott,

"So when you clone a VM to the same SSD drive the original is on, the cloned VM's database is good. But when you clone to the other drive, the cloned VM's database is bad?"
Yes that's correct.

"If so, what happens if you clone to the SSD, confirm the clone's database is good, then use Virtualbox's Move command to move the clone to the other drive?"
I wasn't aware of the Move command, but i tried exporting and then importing from the new drive and that works!

So i now have the VM on the IDE drive, and the terminal text is yellow. I can clone the VM back onto the SSD without issue (and the terminal text is white again). For the life of me i cant see where the setting is for th terminal colour - though that's not an issue in itself.

I can only imagine there is a difference in how clone and export work which was corrupting the data as it was copied

Data should not be corrupted during cloning or exporting. Clone makes another guest, export packs the guest into a distributable OVF format. They both change the UUIDs, but the data should be preserved.

If SSD cloned to IDE is bad, but SSD cloned to SSD copied to IDE is good, and IDE cloned to SSD is good, then anecdotally the problem seems to center on writing to the IDE from a running program but not by straight folder-copy.

This one is a puzzle.

Yes, and what i find most confusing is that the VM OS loads up ok and everything else seems to work, except for the mysql data.

Luckily i have a work around, many thanks for your help and pointing out the Move command.

Glad you're able to keep working! If you ever figure out what was causing this, please post back.