Page 1 of 1

Now do need help... Ubuntu 8.04, and an error message

Posted: 1. May 2008, 07:49
by drhiii3rd
Now I do need help.

Followed the recommendations in Ubuntu Forums to recover from an upgrade of 7.10 to 8.04. Ended up installing from a recommended .DEB file, everything appeared to go well. Then when I Started the Virtual machine, which was working flawlessly in 7.10, I received the following error.

I've posted help mesage in Ubuntu, but felt this would be a place to seek help too. First, I noted that in Settings/ CDROM there is a call to Guest Additions. It was formerly in /opt/virtualbox-1.4.0/additions, but I removed the prior install before upgrading. Don't know if I should have done that. But after installing the virtualbox_1.5.6-28266_Ubuntu_hardy_i386.deb file, it appears to have instaleld things into a different location. I searched but could not find a reference to 'additions'.

I am also not sure if this what is causing the error. Will keep looking around for how to reinstall VB, and enable Guest Additions, but any help or pointers would be appreciated. I am not sure what "Secondary Master" is referring to in the error below because there is only one hard drive on this system, and the VDI file is under /home/me/.VirtualBox/VDI which exists.

Help anyone? I totally do not like Microsoft, but I kinda miss some things and grew wonderfully accustomed to VirtualBox. So much so, I showed it to a gentleman who is working on some large projects where Virtualization is becoming important to his projects and he instantly saw the application and its utility, loved it, and pressing for it to be brought into their environment (meaning licensing).

VB is quite fantastic...

Error message below....

tx, drh



PIIX3 cannot attach drive to the Secondary Master.
VBox status code: -102 (VERR_FILE_NOT_FOUND).


Result Code:
0x80004005
Component:
Console
Interface:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}

Anyone?

Posted: 2. May 2008, 07:53
by drhiii3rd
Am stuck on this problem. Help anyone?

Posted: 2. May 2008, 11:16
by Sasquatch
AFAIK, Secondary Master is the cdrom. You can edit the .xml file of the VM to remove the mounted ISO file. There will be a hash, so you don't have to look for a filename. Look for something like this:

Code: Select all

<DVDDrive passthrough="false">
    <Image uuid="{f2eaad64-b683-496a-a438-c55d4365e3f9}"/>
</DVDDrive>

Posted: 3. May 2008, 03:42
by emmjay
The image is saved in /usr/share/virtualbox

Posted: 3. May 2008, 11:04
by drhiii3rd
I'll be dog-gonned. You are exactly right. Was thinking there was something exotic about the problem. And there is was...

Won't even ask about what or how this 'call' changed during the upgrade. But I am back in, happy as a clam, and grateful yet again for this community that comes to the aid of, well, others.

I am learning as I go along...

drh

Sasquatch wrote:AFAIK, Secondary Master is the cdrom. You can edit the .xml file of the VM to remove the mounted ISO file. There will be a hash, so you don't have to look for a filename. Look for something like this:

Code: Select all

<DVDDrive passthrough="false">
    <Image uuid="{f2eaad64-b683-496a-a438-c55d4365e3f9}"/>
</DVDDrive>

Followup -simpler solution

Posted: 6. Sep 2008, 20:02
by rickbsgu
Rather than editing the file, go into the VM settings and turn off the CDROM mount.

This happened to me on a portable system w/ a removable DVD. When I removed it to put it away and subsequently rebooted the system (the next morning), I got the error, because it could find the DVD that it thought was there

Disabled the mount and on the next boot, everything ok (whew!)