Page 1 of 2
[SOLVED] Fail to start VM
Posted: 21. Nov 2020, 12:35
by satimis
Hi all,
Host Ubuntu 20.04 desktop
VM Ubuntu 20.04 desktop
This VM has not be running for sometimes. Just started it with following warning popup;
Code: Select all
Failed to open a session for the virtual machine multisite00.
Could not open the medium '/home/satimis/VirtualBox VM/multisite00/multisite00/multisite00/multisite00-disk1.vdi'.
VD: error VERR_FILE_NOT_FOUND opening image file '/home/satimis/VirtualBox VM/multisite00/multisite00/multisite00/multisite00-disk1.vdi' (VERR_FILE_NOT_FOUND).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
File manager shows multisite00-disk1.vdi is there. Right-click VM shows "Discard Saved State ..." already greyout.
Please help. Thanks
Regards
Re: Fail to start VM
Posted: 21. Nov 2020, 14:53
by mpack
What's with the multiple nested "multisite00" folders?
Also, instead of an unsupported assertion, it would be nice to see a screenshot of the folder (with a visible path), showing that the file is there.
Re: Fail to start VM
Posted: 21. Nov 2020, 16:18
by satimis
Hi,
$ ls /home/satimis/VirtualBox\ VM/multisite00
$ ls /home/satimis/VirtualBox\ VM/multisite00/multisite00/
Code: Select all
Logs multisite00-disk1.vdi multisite00.vbox multisite00.vbox-prev
I wonder why there are 2 multisite00 folders. I suppose it is the cause of the problem ?
Can I move the files running drag-n-drop moving them to the 1st folder and then delete the double folder?
Thanks
Regards
Re: Fail to start VM
Posted: 21. Nov 2020, 16:28
by mpack
satimis wrote:
I wonder why there are 2 multisite00 folders.
I count three in the error message. I would be looking for some kind of infinite loop scenario, e.g. a link that links to itself. I don't know Linux well enough to know if that's possible.
Re: Fail to start VM
Posted: 21. Nov 2020, 17:20
by satimis
Performed following test;
On terminal ran
$ sudo mv /home/satimis/VirtualBox\ VM/multisite00/multisite00/* /home/satimis/VirtualBox\ VM/multisite00/
$ ls /home/satimis/VirtualBox\ VM/multisite00/
Code: Select all
Logs multisite00-disk1.vdi multisite00.vbox-prev
multisite00 multisite00.vbox
Unable to work. Please see attached screenshot
Re: Fail to start VM
Posted: 21. Nov 2020, 18:14
by fth0
mpack wrote: count three in the error message. I would be looking for some kind of infinite loop scenario, e.g. a link that links to itself. I don't know Linux well enough to know if that's possible.
Of course it's possible, and it's easy, too:
Code: Select all
mkdir test1
cd test1
ln -s . test2
cd test2/test2/test2
cd ../../..
rm test2
cd ..
rmdir test1
creates a folder named
test1, and inside that folder a symbolic link to itself named
test2. Afterwards, you can descend into it indefinitely.
satimis wrote:I wonder why there are 2 multisite00 folders. I suppose it is the cause of the problem ?
Please provide the output of
ls -lR /home/satimis/VirtualBox\ VM/multisite00.
Re: Fail to start VM
Posted: 21. Nov 2020, 18:38
by satimis
fth0 wrote:
satimis wrote:I wonder why there are 2 multisite00 folders. I suppose it is the cause of the problem ?
Please provide the output of
ls -lR /home/satimis/VirtualBox\ VM/multisite00.
$ ls -lR /home/satimis/VirtualBox\ VM/multisite00/
Code: Select all
'/home/satimis/VirtualBox VM/multisite00/':
total 14034152
drwx------ 2 satimis satimis 4096 Nov 21 19:29 Logs
drwx------ 2 satimis satimis 4096 Nov 21 23:03 multisite00
-rw------- 1 satimis satimis 14372831232 Sep 27 06:21 multisite00-disk1.vdi
-rw------- 1 satimis satimis 4286 Nov 21 19:29 multisite00.vbox
-rw------- 1 satimis satimis 4286 Nov 21 18:13 multisite00.vbox-prev
'/home/satimis/VirtualBox VM/multisite00/Logs':
total 16
-rw------- 1 satimis satimis 1979 Nov 21 19:29 VBox.log
-rw------- 1 satimis satimis 1980 Nov 21 18:13 VBox.log.1
-rw------- 1 satimis satimis 1980 Nov 21 18:06 VBox.log.2
-rw------- 1 satimis satimis 1979 Nov 21 14:49 VBox.log.3
'/home/satimis/VirtualBox VM/multisite00/multisite00':
total 0
Regards
Re: Fail to start VM
Posted: 22. Nov 2020, 00:41
by fth0
Ok, then you have no symbolic links, and you can simply remove the superfluous folder with rmdir /home/satimis/VirtualBox\ VM/multisite00/multisite00.
Re: Fail to start VM
Posted: 22. Nov 2020, 01:06
by satimis
fth0 wrote:Ok, then you have no symbolic links, and you can simply remove the superfluous folder with rmdir /home/satimis/VirtualBox\ VM/multisite00/multisite00.
$ sudo rmdir /home/satimis/VirtualBox\ VM/multisite00/multisite00
$ ls -al /home/satimis/VirtualBox\ VM/multisite00/
Code: Select all
total 14034156
drwx------ 3 satimis satimis 4096 Nov 22 06:52 .
drwxrwxr-x 19 satimis satimis 4096 Sep 28 05:53 ..
drwx------ 2 satimis satimis 4096 Nov 21 19:29 Logs
-rw------- 1 satimis satimis 14372831232 Sep 27 06:21 multisite00-disk1.vdi
-rw------- 1 satimis satimis 4286 Nov 21 19:29 multisite00.vbox
-rw------- 1 satimis satimis 4286 Nov 21 18:13 multisite00.vbox-prev
But on File Manager the inaccessible warning still popup as shown on the photo attached to my previous posting.
Regards
Re: Fail to start VM
Posted: 22. Nov 2020, 04:49
by scottgus1
The error means that the file being errored on is not where Virtualbox is programmed to look for it.
This is where Virtualbox is looking:
'/home/satimis/VirtualBox VM/multisite00/multisite00/multisite00/multisite00-disk1.vdi'
This is where the file is:
/home/satimis/VirtualBox\ VM/multisite00/multisite00-disk1.vdi
Note the two extra multisite00's in the Virtualbox path.
You have to release and remove this disk file from your guest in the main Virtualbox window's Virtual Media Manager (but Keep it not Delete it), then add a disk, and browse to the guest folder where the disk file is now. Then your guest should work.
Re: Fail to start VM
Posted: 22. Nov 2020, 05:54
by satimis
If I understand your advice correctly, take following steps on the main window of Oracle VM VirtualBox Manager;
1) Right-click "multisite00 VM" -> Remove
(this will remove "multisite00 VM" but not delete all files in its folder)
2) Then click -> "New" to add this VM "multisite00-disk1.vdi" from /home/satimis/VirtualBox\ VM/multisite00/ folder.
Please advise. Thanks
Regards
Re: Fail to start VM
Posted: 22. Nov 2020, 06:00
by scottgus1
satimis wrote:1) Right-click "multisite00 VM" -> Remove
No, I don't think you can remove whole VMs from the Virtual Media Manager, just disk files. See the main Virtualbox window's File menu, Virtual Media Manager. You want to remove the disk file, not the whole VM.
satimis wrote:Then click -> "New"
This will probably start a new guest.
Rather, right-click the drive controller the disk was attached to before you released/removed it, click Hard Disk, in the popup click Add, then br9wse to the disk file.
Re: Fail to start VM
Posted: 22. Nov 2020, 06:52
by satimis
scottgus1 wrote:satimis wrote:1) Right-click "multisite00 VM" -> Remove
No, I don't think you can remove whole VMs from the Virtual Media Manager, just disk files. See the main Virtualbox window's File menu, Virtual Media Manager. You want to remove the disk file, not the whole VM.
satimis wrote:Then click -> "New"
This will probably start a new guest.
Rather, right-click the drive controller the disk was attached to before you released/removed it, click Hard Disk, in the popup click Add, then br9wse to the disk file.
Before I ran following commands on Terminal to move the files and to delete the double folder multisite00
Code: Select all
$ sudo mv /home/satimis/VirtualBox\ VM/multisite00/multisite00/* /home/satimis/VirtualBox\ VM/multisite00/
$ sudo rmdir /home/satimis/VirtualBox\ VM/multisite00/multisite00
Where can I find "Hard Disk"
On Oracle VM VirtualBox Manager
High-lighting multisite00 VM only showing the warning. Please see attached photo
Regards
Re: Fail to start VM
Posted: 22. Nov 2020, 14:18
by fth0
Perhaps we should look at the contents of two important files first:
Please reboot the host and post the global settings file (/home/satimis/.config/VirtualBox/VirtualBox.xml) and the VM configuration file (/home/satimis/VirtualBox\ VM/multisite00/multisite00.vbox).
Re: Fail to start VM
Posted: 22. Nov 2020, 19:04
by satimis
fth0 wrote:Perhaps we should look at the contents of two important files first:
Please reboot the host and post the global settings file (/home/satimis/.config/VirtualBox/VirtualBox.xml) and the VM configuration file (/home/satimis/VirtualBox\ VM/multisite00/multisite00.vbox).
Rebooted PC
On Terminal Ran;
1)
$ ls -al /home/satimis/.config/VirtualBox/VirtualBox.xml
Code: Select all
-rw------- 1 satimis satimis 15379 Nov 22 13:01 /home/satimis/.config/VirtualBox/VirtualBox.xml
2)
ls -al /home/satimis/VirtualBox\ VM/multisite00/multisite00.vbox
Code: Select all
-rw------- 1 satimis satimis 4286 Nov 21 19:29 '/home/satimis/VirtualBox VM/multisite00/multisite00.vbox'