Home  ›  Fatal Could Not Read From Boot Medium Virtualbox

Fatal Could Not Read From Boot Medium Virtualbox

Written By Friday, 4 March 2022 Add Comment Edit

[Solved] FATAL: Could non read from the boot medium! System Halted!

Discussions related to using VirtualBox on Mac Bone 10 hosts.

  • Answer with quote

[Solved] FATAL: Could non read from the kick medium! System Halted!

Hi

I am trying to boot Window eight.1 on Mac El Capitan 10.11.6.

Am using Virtualbox 5.1.18

I updated final night to this versions and all was well. Went to boot upwards this afternoon and got the mistake bulletin FATAL: Could not read from the boot medium! Sysytem Halted.

I have looked through previous posts and can't observe anything that is the same equally that which I am experiencing and would be grateful for some assistance.

Here is the log in case it helps:

[Mod edit: removed partial, text only VBox.log]

Cheers in accelerate...

Concluding edited by socratis on 30. Mar 2017, 01:40, edited 2 times in total.
Reason: Marked as [Solved].

Hoggio
Posts: 17
Joined: 22. Mar 2017, xviii:33
  • Answer with quote

Re: FATAL: Could not read from the boot medium! System Halted!

Postby socratis » 22. Mar 2017, 19:13

Partial logs are not that useful. Please ZIP and attach the whole VBox.log.

But to confirm, this was a previously working VM, and you were not trying to commencement from a CD/DVD.

Do NOT transport me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do Not reply with the "QUOTE" push button, please use the "Post Respond", at the lesser of the form.
If you lot obfuscate whatsoever data requested, I will obfuscate my response. These are virtual UUIDs, not existent ones.

socratis
Site Moderator
Posts: 27690
Joined: 22. Oct 2010, xi:03
Location: Hellenic republic
Primary Bone: Mac Os X other
VBox Version: PUEL
Invitee OSses: Win(*>98), Linux*, OSX>x.v
  • Reply with quote

Re: FATAL: Could non read from the boot medium! Arrangement Halted!

Postpast Hoggio » 22. Mar 2017, 21:09

Equally far as I am aware it boots from an ISO but have also tried vdi which might be the incorrect way of going well-nigh information technology!

The ISO file though says it was created in March 2015 and hasn't been used since. Mayhap the current ane has been deleted? Or am I getting that incorrect?

Anyway, total log attached.

Attachments
VBox.log
(63.43 KiB) Downloaded 275 times
Hoggio
Posts: 17
Joined: 22. Mar 2017, 18:33
  • Reply with quote

Re: FATAL: Could not read from the boot medium! System Halted!

Postby socratis » 23. Mar 2017, 00:09 

00:00:07.877870 VMMDev: Guest Log: BIOS: Boot : bseqnr=3, bootseq=0002
00:00:07.928889 VMMDev: Guest Log: BIOS: Booting from Hard disk...
...
kaboom

Have you checked your host'south physical hard drive for errors? Do you have a backup?

Do NOT ship me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Exercise Non respond with the "QUOTE" push, please utilize the "Mail service Respond", at the bottom of the class.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not existent ones.

socratis
Site Moderator
Posts: 27690
Joined: 22. Oct 2010, xi:03
Location: Greece
Primary Os: Mac OS Ten other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>ten.v
  • Reply with quote

Re: FATAL: Could not read from the boot medium! System Halted!

Postby Hoggio » 23. Mar 2017, 01:51

Yes, I do have a backup.

I haven't checked the physical difficult bulldoze for errors. How would I do that?

Hoggio
Posts: 17
Joined: 22. Mar 2017, xviii:33
  • Reply with quote

Re: FATAL: Could not read from the kick medium! System Halted!

Postpast socratis » 23. Mar 2017, 09:35

Hoggio wrote:Yes, I do take a backup.

Excellent, non many do ;). You might need information technology...

Hoggio wrote:I haven't checked the physical hard drive for errors. How would I practice that?

Open up Utilities » Disk Utility » Offset Aid. Postal service any error messages.

Do Non ship me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do Not reply with the "QUOTE" button, please employ the "Post REPLY", at the lesser of the grade.
If you obfuscate whatever data requested, I volition obfuscate my response. These are virtual UUIDs, not real ones.

socratis
Site Moderator
Posts: 27690
Joined: 22. Oct 2010, xi:03
Location: Hellenic republic
Primary Bone: Mac Os X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>ten.5
  • Reply with quote

Re: FATAL: Could not read from the boot medium! System Halted!

Postby socratis » 23. Mar 2017, 12:09

OK, then you should restore the backup and hope for the best...
Accept you backed upwards the whole folder (/Users/timhodgson/VirtualBox VMs/), the VM folder (/Users/timhodgson/VirtualBox VMs/Windows viii.1 Full/), or simply the VDI (/Users/timhodgson/VirtualBox VMs/Windows viii.1 Full/Windows 8.i Full (original).vdi) ?

Do NOT transport me Personal Letters (PMs) for troubleshooting, they are simply deleted.
Do Non reply with the "QUOTE" button, please use the "POST Reply", at the bottom of the form.
If you obfuscate whatever data requested, I will obfuscate my response. These are virtual UUIDs, not real ones.

socratis
Site Moderator
Posts: 27690
Joined: 22. Oct 2010, xi:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
  • Reply with quote

Re: FATAL: Could not read from the boot medium! System Halted!

Postby Hoggio » 23. Mar 2017, 13:28

I have all options backed upwardly in timemachine.

Windows viii.1 Full.vdi is simply a duplicate of Windows 8.i Full(Original).vdi which I made just in case when this all happened and I was trying various options before contacting you lot.

Hoggio
Posts: 17
Joined: 22. Mar 2017, xviii:33
  • Reply with quote

Re: FATAL: Could not read from the boot medium! Arrangement Halted!

Postpast socratis » 23. Mar 2017, 17:07

I'm sorry... what??? Tin you please analyze the concluding message? Did I understand correctly that you had a problem, and then you lot made a copy of the .VDI, and so yous posted the message about the problem, after y'all've switched HDs in the VM configuration? Did I sympathise it correctly?

Do Non ship me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do Non reply with the "QUOTE" button, please use the "Post Respond", at the bottom of the form.
If you obfuscate any information requested, I volition obfuscate my response. These are virtual UUIDs, not real ones.

socratis
Site Moderator
Posts: 27690
Joined: 22. Oct 2010, 11:03
Location: Greece
Principal Os: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
  • Answer with quote

Re: FATAL: Could non read from the boot medium! System Halted!

Postby Hoggio » 23. Mar 2017, 18:24

I do have a problem. I am unable to boot the VM and am getting the 'FATAL: Could not read...' error message.

I'm a picayune fleck miffed hither at present. What have I done incorrect?

The error came after updating to five.1.18. I tried to find out how to solve the problem and have had no luck and take ended here on this forum every bit could actually do with some assist.
Have I done something wrong?

Hoggio
Posts: 17
Joined: 22. Mar 2017, xviii:33
  • Reply with quote

Re: FATAL: Could not read from the kicking medium! Arrangement Halted!

Postpast socratis » 23. Mar 2017, 19:00

I understand that you take a trouble.
I understand that you lot want help.
Exercise y'all empathize that if you want help you have to answer the questions?
It's uncomplicated... You reply the questions => you go help.

Exercise Not ship me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do Non reply with the "QUOTE" push, please use the "POST Reply", at the bottom of the form.
If you obfuscate any data requested, I will obfuscate my response. These are virtual UUIDs, non real ones.

socratis
Site Moderator
Posts: 27690
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary Os: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
  • Reply with quote

Re: FATAL: Could not read from the boot medium! System Halted!

Postby Hoggio » 23. Mar 2017, 19:11

My apologies! I idea I had answered the question. I'yard not sure why I am getting this reaction.

However, to clarify:
I got the FATAL: Could not read... mistake the morning/afternoon I had updated to 5.1.18. The evening I updated the VM ran fine.
Upon getting the error message I looked upwardly if there was a way to solve the outcome and found various ways including some suggestions on this forum but nothing seemed to friction match my problem exactly.
I then constitute a video on youtube which I used to endeavour to fix the issue. Equally part of doing this (so that I had a indistinguishable country) I duplicated the vdi which is why y'all tin can meet at that place is the original and some other).
I made a feeble effort of irresolute Chief Master and Primary Slave just I still got the same error message. Frustratingly my bluetooth mouse and keyboard also disconnect which ways I have to reboot my mac!

I hope this helps to clarify. Perhaps we tin continue at present?

And, yes, after doing all that I posted on here considering I had hit a brick wall!!

Hoggio
Posts: 17
Joined: 22. Mar 2017, 18:33
  • Reply with quote

Re: FATAL: Could not read from the boot medium! System Halted!

Postby socratis » 23. Mar 2017, 19:31

I asked you a simple question:

socratis wrote:you fabricated a copy of the .VDI, and and then ... yous've switched HDs in the VM configuration?

That was it. You came dorsum with repeating the error message (I've memorized it by now) and you lot didn't respond the question, only questioned what you did wrong. the simply thing wrong is that you didn't tell me the whole story from the beginning. Accept you heard "I swear to tell the truth, the whole truth, and nil but the truth" ? Well, that "whole" role was missing. You merely answered it in your concluding mail service. Now I can take a clearer picture of what happened.

If you lot made a re-create of a corrupt file, and then the copy will be corrupt as well. And then changing disks, moving them from primary to secondary or anything else won't matter. Your simply hope is that the backup is not decadent.

Since you know how to replace a VDI in a VM, I'm going to attempt and go along it simple for you and me:

  • Release the current HD from the VM.
  • You can delete it if you desire, simply make sure that if you go to the Media Managing director (Cmd-D) information technology's not there.
  • Restore the VDI from the TimeMachine backup and add it back to your VM.

Do Not send me Personal Letters (PMs) for troubleshooting, they are just deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If yous obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.

socratis
Site Moderator
Posts: 27690
Joined: 22. Oct 2010, eleven:03
Location: Hellenic republic
Primary OS: Mac Os X other
VBox Version: PUEL
Invitee OSses: Win(*>98), Linux*, OSX>10.v

Return to VirtualBox on Mac OS X Hosts

Who is online

Users browsing this forum: No registered users and 20 guests

brobstthismillond1946.blogspot.com

Source: https://forums.virtualbox.org/viewtopic.php?t=82365

0 Response to "Fatal Could Not Read From Boot Medium Virtualbox"

Post a Comment

Subscribe to: Post Comments (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel