this post was submitted on 24 Apr 2026
8 points (90.0% liked)

Linux 101 stuff. Questions are encouraged, noobs are welcome!

1498 readers
1 users here now

Linux introductions, tips and tutorials. Questions are encouraged. Any distro, any platform! Explicitly noob-friendly.

founded 2 years ago
MODERATORS
 

@linux4noobs@lemmy.world @linux4noobs@programming.dev @casualconversation can someone please suggest me a way out ??

Basically, l'm installing virtual box on a windows 10 laptop. Here, l'm going to try out MX Linux fluxbox and tinker with linux in a sandboxed environment, so that my experiments don't harm the main system.

In the screenshot, you can see where l got stuck. In the storage part, it says that the controller ide optical drive is empty. The controller sata MX fluxbox.vdi is inaccessible.

top 4 comments
sorted by: hot top controversial new old
[–] tofu@lemmy.nocturnal.garden 8 points 1 month ago

Out of what? What are you trying to achieve?

[–] e0qdk@reddthat.com 2 points 1 month ago (1 children)

Hmm. I assume the "Inaccessible" is what you're trying to fix? Is the vdi file where it's supposed to be (on your host system) -- like, it didn't get deleted or quarantined by anti-virus or fucked around with by OneDrive or something like that, right?

I don't use VirtualBox or Win10, so my ability to help here is limited, but sanity checking that the file is OK is where I'd start.

[–] codewizard@hear-me.social 0 points 1 month ago (1 children)

@e0qdk it was a folder. I cut it and pasted it onto my desktop.

[–] e0qdk@reddthat.com 3 points 1 month ago* (last edited 1 month ago)

Isn't it supposed to be a file? (Maybe that's your issue?) Is this the first time you're setting up this VM or are you trying to move it from somewhere else?

Assuming first time, I'd expect you'd create a disk image to install to, load an ISO for the distro into the simulated optical drive, and then boot from the optical drive and format the blank disk inside the VM. I don't know what VirtualBox specifically does, but that seems like the kind of thing there should be a wizard for; there is in other VM software, at least, for creating new VMs...

If you're trying to migrate an existing VM between computers, I'd expect you'd just copy the disk image file and recreate the machine metadata to make sure it points to it correctly and you should be good...? Could be some VB specific crap I'm unaware of though.