Hi,
I recently changed the login to a NAS on my system network and since then when I start VB (version 4.1.8 r75467) I get a dialog box showing :
"One or more virtual hard disks, CD?DVD or floppy media are not currently accessible. As a result, you will not be able to operate virtual machines that use these media until they become accessible later..."
I press the <Check> button and it comes up with a list comprising all of my .vdi files. None of my virtual machines seem broken so can anyone tell me what the problem is ?
Thanks,
Boo
Error - Virtual hard disks ... are not currently accessible
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Error - Virtual hard disks ... are not currently accessi
The problem is probably due to changing the NAS login. Hard to say with so little information. What did/does the NAS supply to the guest/s?
Is it shares or the actual guest/s ?
Is it shares or the actual guest/s ?
-
Boo2
- Posts: 9
- Joined: 1. Nov 2011, 21:41
- Primary OS: MS Windows 7
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: windows, linux, qnx
Re: Error - Virtual hard disks ... are not currently accessi
Sorry, I was not very clear but AFAIK nothing that VirtualBox depends upon is stored on the NAS but it may have been mounted as a network drive before, I can't remember.Perryg wrote:The problem is probably due to changing the NAS login. Hard to say with so little information. What did/does the NAS supply to the guest/s?
Is it shares or the actual guest/s ?
As I said, the VMs reported to have noc currently accessible media all work without issue so it seems to be something wrong with VirtualBox Manager.
Any ideas gratefully received,
Boo
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Error - Virtual hard disks ... are not currently accessi
Well that really didn't clear it up for me.
If there were shared folders that had been mapped to the NAS that could produce the warning.
Do the guests actually start and are they functional?
Did you log in as a different user on the host?
If there were shared folders that had been mapped to the NAS that could produce the warning.
Do the guests actually start and are they functional?
Did you log in as a different user on the host?