Opened 9 years ago
Last modified 8 years ago
#15213 new defect
Unable to remove device with attached diff images
Reported by: | ArtZ | Owned by: | |
---|---|---|---|
Component: | virtual disk | Version: | VirtualBox 5.0.16 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Windows |
Description
Receive message box - one or more disk image files are not currently accessible......
Select "check"
VDI device is not attached to any machine. Also, rechecked all machines and non are using this vdi in this location. Attempt to remove it but it says it has 1 child media and object in use.
a) cryptic message as it should really say in plain english what object name its associated with.
b) there are no machines that I currently have using this particular vdi.
c) have similar named vdi located in another directory but not attached to this one here. Nothing is attached to it.
Attachments (6)
Change History (9)
by , 9 years ago
Attachment: | vmerror.JPG added |
---|
by , 9 years ago
Attachment: | vmerror2.JPG added |
---|
by , 9 years ago
by , 9 years ago
by , 9 years ago
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Summary: | Unable to remove device → Unable to remove device with attached diff images |
---|
The behavior is not that obvious and could be improved. On the other hand the error message clearly states that the hard disk cannot be removed because there is 1 child medium. So if you want to remove this medium, you have to remove this child medium first. You have to remove all child media before you can remove the actual medium. Of course VirtualBox should be able to remove the complete chain (perhaps asking the user if he is really sure about that). At the moment you have to do this manually.
On the other hand your scenario is not that common, because it's not possible to remove a medium from a VM if the VM has snapshots -- manipulating the VM settings will only change the current state, not the initial state. And it's also not possible to remove such a VM -- something which needs to be improved as well.
comment:3 by , 8 years ago
Error still occurring with version 5.1.8 - Its been 8 months now, how long does it take to respond to this bug?
still happening with v5.018. Again cryptic message should tell user what it really thinks machine name its attached to. But then again in this case its not attached, believe its a case of mistaken identity of vd of same name in another directory.