PIIX3 cannot attach drive to the Secondary Master.

calou · Post by **calou** » 28. May 2007, 19:13

I'm new to VirtualBox. I'm running vb on Ubuntu 7.04 with WindowsXP HOME SP2 as a virtual machine. I have several hard drives on my system and was trying to create a secondary (ide) slave. Anyway it didn't work, now every time I try to run my virtual machine I get the error message "PIIX3 cannot attach drive to the Secondary Master.
VBox status code: -102 (VERR_FILE_NOT_FOUND)." and can't get around it. Does anyone have an idea of how to get around this so I can run my vm? javascript:emoticon(':oops:')

Post by **bodhi.zazen** » 28. May 2007, 19:22

What are you trying to do exactly ?

If you are trying to share a hard drive between host and guest, that is not the way it is done.

If you are trying to boot a HD image, well that is not the way it is done either.

calou · Post by **calou** » 28. May 2007, 20:11

Thanks for the rapid reply; what I was trying to do at this point is relatively unimportant but here it is. I have 2 ext3 (Linux) drives and one NTFS drive on my computer, one of the ext3 drives is where I loaded Linux and the various softwares that come with UBUNTU the other is empty. The NTFS drive is where Windows XP and all my windows software is. I am in the process of abandoning Windows in favor of Linux but still need the crutch of maintaining my Windows environment for various reasons which is why I'm using VirtualBox on my Linux side as a bridge to windows. When I created my virtual machine, WindowsXP, I believed I only could see one of my Linux drives (the one I was running Linux and VirtualBox on) what I was hoping to do is "mount" my other Linux drive. That failed, I don't remember the error message, so I canceled the process (thinking that by canceling VirtualBox would "forget" my attempt). However when I tried to run my virtual machine I get the described error message (which makes me think that VirtualBox is still trying to "mount" the second drive). Now what I think I need to do is "backout" what ever I did to confused VirtualBox but I don't even know where to look. To a newbee the error message doesn't help much. So I'm looking for someone who can tell me what file I need to cleanup/remove so I can "rollback" to where I was before I stated messing with my VM configuration.

Post by **bodhi.zazen** » 28. May 2007, 20:29

Depends on how you added the drive

If you added it in the gui, under hard drive, remove it from the list.

To share your hard drive is easy :

http://doc.gwos.org/index.php/VirtualBo ... hard_drive

calou · Post by **calou** » 28. May 2007, 20:46

I removed the drive under secondary (ide) slave, now I don't have any drives listed, when I search for .vdi files I can't find any. Guess I'll just have to start from scratch.

Post by **bodhi.zazen** » 28. May 2007, 20:51

He .vdi drives are located in

~/.VirtualBox/VDI

where ~ = /home/username

The dot ( . ) makes it "hidden"

Try this :

Code: Select all

ls ~/.VirtualBox/VDI/

calou · Post by **calou** » 28. May 2007, 21:00

tried that, I can see it but when I try to run the VM I get the same ol' error "
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}"

I think my only hope is to rebuild the virtual machine. Fortunately I hadn't put much working into this virtual machine so its no biggy . . . . maybe I should read the documentation first next time LOL. Thanks for the help. javascript:emoticon(':lol:')

bvidinli · Post by **bvidinli** » 10. Feb 2008, 10:53

i upgraded from gutsy to hardy alpha 4

virtualbox was not working,

i removed using aptitude,
downloaded deb package for gutsy from virtualbox site

installed using dpkg -i
dpkg installer re-compiled for my kernel: 2.6.24-7-generic

started VirtualBox

old virtual machine did not work at first..

deleted virtual machine,
re-added virtual machine with old hd image.

now working with no problem...

guttersnipe · Post by **guttersnipe** » 22. Mar 2008, 01:41

deleted virtual machine,
re-added virtual machine with old hd image.

now working with no problem...

I had this same issue. I followed the above steps, and it fixed the problem.

Thanks!
Good Carma to you.

jtk174 · Post by **jtk174** » 2. May 2008, 15:32

I had the exact same problem on a windows host. The vdi had been working for weeks and stopped working!
However, the instructions given solved my problem.
Many thanks.

n0tepad · Post by **n0tepad** » 24. May 2008, 10:49

delete virtual machine and re-add using old image?
wtf are you kidding?
the virtual machine and the image are the same file.

Half-Borg · Post by **Half-Borg** » 24. May 2008, 16:18

n0tepad wrote:delete virtual machine and re-add using old image?
wtf are you kidding?
the virtual machine and the image are the same file.

no they aren't
there is a file which stores the specification of the virtual computer (like which soundcard is emulated) and the .vdi that stores the harddisk of the virtual system

igorp · Post by **igorp** » 27. May 2008, 23:24

It really works. The only problem is you have to set your shared folders and pheripherals again.

salvox · Post by **salvox** » 8. Jul 2008, 01:20

The solution is even easier, dont need to go back your virtual machine. Maybe you were using a CD on your last session of your VM and after you turned off the VM you took out the CD, Hence, the VM is looking for that disk on the startup. Enter to Mount/Unmount CD options and unmount anything in there.

drdods · Post by **drdods** » 8. Jul 2008, 06:39

Worked for me.
Unmounted the CD and it booted up fine (after upgrading to Hardy today).
Many thanks salvox!

virtualbox.org

PIIX3 cannot attach drive to the Secondary Master.

PIIX3 cannot attach drive to the Secondary Master.

working on ubuntu hardy