Javascript required
Skip to content Skip to sidebar Skip to footer
Home / Fatal: Could Not Read From the Boot Medium! System Halted. Kali Virtualbox

Fatal: Could Not Read From the Boot Medium! System Halted. Kali Virtualbox

[Solved] FATAL: Could not read from the kicking medium! Organization Halted!

Discussions related to using VirtualBox on Mac Bone X hosts.

  • Reply with quote

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

How-do-you-do

I am trying to kicking Window viii.1 on Mac El Capitan 10.eleven.half-dozen.

Am using Virtualbox five.one.18

I updated last night to this versions and all was well. Went to boot up this afternoon and got the error bulletin FATAL: Could non read from the boot medium! Sysytem Halted.

I have looked through previous posts and can't find anything that is the aforementioned as that which I am experiencing and would exist grateful for some help.

Here is the log in example it helps:

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

Thanks in advance...

Terminal edited past socratis on xxx. Mar 2017, 01:twoscore, edited 2 times in full.
Reason: Marked as [Solved].

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

Re: FATAL: Could non 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.

Just to confirm, this was a previously working VM, and you lot were non trying to first from a CD/DVD.

Practise Not send me Personal Messages (PMs) for troubleshooting, they are merely deleted.
Do Non reply with the "QUOTE" button, please apply the "Post Reply", at the lesser of the form.
If you obfuscate any information 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.five
  • Reply with quote

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

Postby Hoggio » 22. Mar 2017, 21:09

As far as I am aware it boots from an ISO but have also tried vdi which might exist the wrong style of going nearly it!

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

Anyway, full log attached.

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

Re: FATAL: Could not read from the kicking medium! Organization 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 Hd...
...
kaboom

Have you lot checked your host's physical hard drive for errors? Practise you have a backup?

Do NOT transport me Personal Letters (PMs) for troubleshooting, they are only deleted.
Do Non answer with the "QUOTE" push button, please employ the "Postal service Respond", at the bottom of the form.
If you lot obfuscate any information requested, I volition obfuscate my response. These are virtual UUIDs, not real ones.

socratis
Site Moderator
Posts: 27690
Joined: 22. October 2010, 11:03
Location: Hellenic republic
Chief OS: Mac OS X other
VBox Version: PUEL
Invitee OSses: Win(*>98), Linux*, OSX>x.5
  • Reply with quote

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

Postby Hoggio » 23. Mar 2017, 01:51

Yep, I do have a backup.

I haven't checked the physical hard bulldoze for errors. How would I practise that?

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

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

Postby socratis » 23. Mar 2017, 09:35

Hoggio wrote:Yes, I practice have a fill-in.

Excellent, not many do ;). Yous might need it...

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

Open Utilities » Disk Utility » Outset Help. Post any error messages.

Do NOT ship me Personal Letters (PMs) for troubleshooting, they are but deleted.
Practice Non answer with the "QUOTE" push, delight use the "Post REPLY", at the bottom of the course.
If you obfuscate whatsoever data requested, I will obfuscate my response. These are virtual UUIDs, not real ones.

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

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

Postby socratis » 23. Mar 2017, 12:09

OK, so you lot should restore the fill-in and hope for the best...
Have you backed up the whole folder (/Users/timhodgson/VirtualBox VMs/), the VM binder (/Users/timhodgson/VirtualBox VMs/Windows 8.one Full/), or but the VDI (/Users/timhodgson/VirtualBox VMs/Windows eight.1 Total/Windows 8.1 Full (original).vdi) ?

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

socratis
Site Moderator
Posts: 27690
Joined: 22. October 2010, eleven:03
Location: Greece
Primary Os: Mac Bone Ten other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.five
  • Reply with quote

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

Postby Hoggio » 23. Mar 2017, 13:28

I have all options backed upwardly in timemachine.

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

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

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

Postby socratis » 23. Mar 2017, 17:07

I'm sad... what??? Can you please clarify the last message? Did I understand correctly that you lot had a problem, and so you made a copy of the .VDI, and then you posted the message nearly the problem, after you lot've switched HDs in the VM configuration? Did I understand information technology correctly?

Exercise NOT send me Personal Letters (PMs) for troubleshooting, they are merely deleted.
Practice NOT reply with the "QUOTE" button, please use the "POST Answer", at the bottom of the form.
If you lot obfuscate whatsoever information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.

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

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

Postby Hoggio » 23. Mar 2017, 18:24

I do have a trouble. I am unable to boot the VM and am getting the 'FATAL: Could non read...' fault message.

I'm a little bit miffed here now. What have I washed wrong?

The mistake came later on updating to 5.1.xviii. I tried to find out how to solve the trouble and accept had no luck and accept ended here on this forum every bit could really do with some help.
Have I done something wrong?

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

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

Postby socratis » 23. Mar 2017, 19:00

I empathise that you take a problem.
I understand that you desire assist.
Practice you understand that if you desire help you accept to reply the questions?
It'south simple... You answer the questions => you get help.

Do NOT transport me Personal Letters (PMs) for troubleshooting, they are only deleted.
Do NOT reply with the "QUOTE" button, delight employ the "POST Respond", at the bottom of the form.
If you obfuscate whatever information requested, I volition obfuscate my response. These are virtual UUIDs, not existent ones.

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

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

Postpast Hoggio » 23. Mar 2017, xix:xi

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

All the same, to clarify:
I got the FATAL: Could non read... error 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 issue and found various ways including some suggestions on this forum but nix seemed to match my problem exactly.
I then found a video on youtube which I used to try to fix the issue. As office of doing this (then that I had a duplicate state) I duplicated the vdi which is why y'all tin meet there is the original and another).
I made a feeble attempt of changing Main Master and Primary Slave merely I nonetheless got the same error bulletin. Frustratingly my bluetooth mouse and keyboard besides disconnect which means I have to reboot my mac!

I hope this helps to clarify. Perhaps we can continue now?

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! Arrangement Halted!

Postby socratis » 23. Mar 2017, xix:31

I asked you a simple question:

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

That was it. You came back with repeating the error message (I've memorized it by at present) and you didn't reply the question, but questioned what y'all did incorrect. the just matter wrong is that you didn't tell me the whole story from the beginning. Have you heard "I swear to tell the truth, the whole truth, and aught but the truth" ? Well, that "whole" part was missing. You just answered information technology in your last postal service. Now I can have a clearer picture of what happened.

If you made a copy of a corrupt file, and then the copy will exist decadent likewise. So irresolute disks, moving them from primary to secondary or annihilation else won't matter. Your but promise is that the backup is non corrupt.

Since yous know how to supplant a VDI in a VM, I'm going to try and proceed information technology uncomplicated for you and me:

  • Release the current HD from the VM.
  • You lot can delete it if you want, just brand certain that if you go to the Media Manager (Cmd-D) it's not there.
  • Restore the VDI from the TimeMachine backup and add it back to your VM.

Exercise NOT send me Personal Messages (PMs) for troubleshooting, they are merely deleted.
Practise NOT reply with the "QUOTE" push, please use the "POST REPLY", at the bottom of the form.
If y'all obfuscate whatever information requested, I will obfuscate my response. These are virtual UUIDs, not existent ones.

socratis
Site Moderator
Posts: 27690
Joined: 22. October 2010, 11:03
Location: Greece
Chief Bone: Mac OS 10 other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>ten.5

Render to VirtualBox on Mac OS X Hosts

Who is online

Users browsing this forum: HoshiYamazaki and 21 guests

Fatal: Could Not Read From the Boot Medium! System Halted. Kali Virtualbox

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