Can't unmount vdi file

[oxoocoffee]

I just tried to gparted one of the vdi files and I am getting error unmount it. I have two VM setup both are Ubuntu 18.04 with latest updates

VM1 - is what I am booing into (fresh install) VM2 - is what is attached as additional IDE or SATA to VM1

VM2 was cloned from VM1

Here is what I did try to do

1. in VM1 attach VM2 vdi file. I did try as IDE and SATA each time
2. Boot to VM1
3. Start gparted
4. Select /dev/sda (VM2)
5. Try to resize ext4 partition (Did checked it is not mounted)
6. Apply changes

It seams that /dev/sdb is VM1 what I booted into.

Resize fails

[Socratis]

Maybe because it's a clone and they have the same UUID?

The way you're doing things is rather peculiar. Why don't you boot VM2 (with VDI2) from a GParted live DVD? That's how everyone and their cousin is doing it...

[oxoocoffee]

Ok So I just downloaded latest GParted Live iso. I created separate VM with out creating vdi disk as Linux x64 Debian. Before starting I entered Settings and added GParted Live iso to Storage/Controller IDE and checked LiveCD option for it. Next I added Controller SATA and Added Existing VM I am trying to resize. After Booting lsblk does not show /dev/sdb. I just see /dev/sda which is Gparted Live mount.

Am I missing something?

[Socratis]

1. It's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

2. You were supposed to follow these steps when you filed the bug, and provide a VBox.log:

   Attach a (full) log file ("Machine" menu/"Show Log" in the main VirtualBox Manager window) straight away to save time for you and for us. The log file contains a lot of useful information about both the host andthe guest systems as well as information about what happened during a particular machine run. Please do not cut and paste it.

So, if you can, please open a new thread in the ​VirtualBox on Linux Guests section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.