Blue screen when booting from USB drive in UEFI mode (2013.07)

SOLUTION for me was to update the firmware on my ASRock mb as thatu pdate changed the EFI software (by American Megatrends) version from 2.00 to 2.31. However, other users are still experiencing the blue screen.
SHORT VERSION
When I try to boot Arch Linux 2013.07 with an USB drive in UEFI mode (for installation), I get a blue screen (which is rather a literal description and not a hint towards the old Windows' one) with the message
Failed to install override security policy (14): Not found
LONG VERSION
I made an USB installation media (product: Intenso Rainbow) by following this advice on the wiki.
I used the july release of Arch for that. First of, after installing the image to the USB stick I found that I needed to correct the label in the archiso-x86_64.conf file to ARCH_201307 (or was it the label of the usb stick, can't remember right now). (Pretty sure it was the same problem with "Linux Live USB Creator" which I used 3-4 months ago...)
After doing that, I rebooted and selected the entry
UEFI Intenso Rainbow
from this list of entries:
SATA HDJ ... something (the hard drive where Win 7 64 bit is installed with all programs)
SATA something (hard drive which only contains data)
Windows Boot Manager
USB: Intenso Rainbow
UEFI: Intenso Rainbow
It went to a blue screen with a message in white text saying
Failed to install override security policy (14): Not found
Below that was an OK button which had a black rectangle over it.
After I experienced the bluescreen, I tried booting the
USB Intenso Rainbow
entry and the boot process then worked fine, I got to that Arch menu where I could choose
Boot Arch Linux (x86_64)
Boot Arch Linux (i686)
Boot existing OS
Run Memtest...
and so on...
But just to make sure, I then did the check for UEFI mode according to this and only saw a folder acpi and ... something else I can't really remember, but it definitely was not efi. Thing is, I needwant to boot into UEFI mode as I have Win 7 already installed in UEFI mode.
Some info about my motherboard: it's from ASRock and is called H67M. The BIOS is dated to 2011-10-26 and is version 1.7.
So far, I only found a mention of the problem here at superuser.com.
Last edited by jones (2013-07-15 07:15:18)

Ok then, so this thread has also become about the blank screen problem when booting (in this particular case, Arch 2013.06 since 2013.07 seems to be worse).
srs5694 wrote:Typically, you adjust kernel boot options using your boot manager or boot loader. In GRUB, you hit the "e" key to open an editor. In rEFInd, you hit F2 or Insert twice. I don't recall offhand what key does the job for gummiboot (which I'm pretty sure the Arch installer uses), but I'm certain it's got the feature.
You are right. Thanks. I realized I had the gummiboot config right in front of me all the time. It's the file 'archiso-x86_64.conf' in \loader\entries (on Windows).
An addendum: I think the USB: Intenso Rainbow boot option takes me into a GRUB menu. Hitting 'e' in this "big" and fully designed menu didn't do anything IIRC. Hitting 'Tab' did the trick to get into editing the boot command line.
Hitting 'e' worked in the gummiboot menu though.
So I tried booting with the following options (also by combining some of them)
nomodeset
acpi_backlight=vendor
radeon.modeset=0 (I have a Gigabyte 7870 card in this desktop machien)
i915.modeset=0
but it did not help.
To be rather safe than sorry: I should mention that there are two grey-ish bars visible on the top and bottom of the screen after I try to boot the first entry, Arch Linux archiso x86_64 UEFI USB. Always has been with those two older Arch version (2013.05+2013.06). I also found another thread where one user talks about using the VGA port of the monitor, which I am currently not, I am using the DVI one, so that's worth a try too. EDIT It did not help either. What I did was setting the primary graphics adapter in the UEFI north bridge configuration menu to 'onboard' which worked immediately when rebooting (I hit the button labeled "Source" on my monitor and it showed it is using the "Analog" mode), but the problem just stayed the same. Adding aforementioned boot options or a combination thereof did not change anything.
Thanks for the e-mail addresses, I sent one to James Bottomley.
Last edited by jones (2013-07-07 11:12:05)

Similar Messages

X200 with OCZ ssd blue screens when booting from docking station

The x200 blue screens when booting from the docking station. If I take the laptop out of the docking station to boot and then dock once booted the laptop is fine.
The issue started happening when you I upgraded the laptop form xp to windows 7 and installed an OCZ vertex 2 solid state drive.
I have tried updating the firmware on the ssd using this utility
http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-69806
The program showed that my ssd was running firmware version 1.29 and did not need to be updated.
I have also tried updating the x200 to the latest BIOS. Nothing seems to work.
Any ideas or suggestions are greatly appreciated.
Solved!
Go to Solution.

you need to modify a registry value before going from AHCI to IDE. (or viceversa).
http://www.ocztechnologyforum.com/forum/showthread.php?69682-Change-from-IDE-to-AHCI-after-Installat...

[SOLVED] Attempting to boot from USB key in UEFI mode

I am attempting to boot from a USB Key in UEFI mode to dual boot windows 8 and arch linux. I'm unsuccessful in getting the USB key to boot in UEFI mode.
I am following the guide on page: https://wiki.archlinux.org/index.php/Un … _Interface due to the fact that I am receiving error " No loader found. Configuration files in /loader/entries/*.conf are needed."
I am attempting to use the archiso media and have created refind.conf according to https://bugs.archlinux.org/task/31894#comment102233 in (USB)/EFI/boot/refind.conf
However, I'm stuck on the initial step from the wiki: Install refind-efi pkg. In the usb's filesystem, overwrite the file EFI/boot/bootx64.efi with /usr/lib/refind/refind_x64.efi.
My question is: How do I install the refind-efi package onto the USB key using an arch linux host machine and the USB plugged into the machine.
Last edited by tonysoprano (2013-02-13 04:09:56)

swordfish wrote:1. Might be possible, that the uefi integration is pretty bad. Have you already looked for an update of the uefi bios?
This is my thought, too. The "memory map has changed" message sounds like the firmware is messing with the way memory is laid out in the middle of the boot process. A firmware update, if available, is likely to be the best way to deal with this problem. If not, trying Fedora's patched GRUB Legacy and GRUB 2 are also worth doing; it's conceivable that one of them includes a workaround for the problem.
2. In your first posting you mention Windows 8 on this machine. Is W8 starting in uefi mode?
This is important, but if the disk uses GPT partitioning, then Windows is starting in EFI mode.
3. If W8 is starting in uefi mode, are you sure that secure boot is disabled?
It is; if it weren't, neither rEFInd nor ELILO could start -- or even if they were configured to start in Secure Boot mode, ELILO doesn't launch its kernels in a way that respects Secure Boot, so the ELILO failure can't be caused by Secure Boot. Also, when launched with Secure Boot active, rEFInd returns a clear error message about a security violation and then returns to its main menu; it doesn't hang the computer.
One possible workaround occurs to me if all else fails: Have rEFInd launch a BIOS version of GRUB. The setup procedure, in outline, is as follows:
Create a BIOS Boot Partition on the disk.
Install the BIOS version of GRUB 2.
Configure rEFInd to include a scan for BIOS-mode boot loaders by uncommenting the "scanfor" line in refind.conf and adding "hdbios" to it.
Thereafter, you'll see a new "generic" icon, which should launch GRUB, which should launch Linux in BIOS mode, even though Windows launches in EFI mode. This will work on most modern UEFI-based computers with a single hard disk, but things get trickier with multiple disks and with some UEFI implementations that lack the necessary firmware features. If a future firmware update fixes the problem, or if a future kernel's EFI stub loader includes a workaround, the EFI-mode booting will become an option once again.

Blue screen when boot from cd and cannot open diskutil

HEllo
i have problem my macbook pro 2011 i7 when i boot up after apple logo display white screen , when i boot from cd display blue screen , i'm format my ssd but same problem
when i'm try open diskutil with CMD +R open Recovery network
Any body can help me ?

when i'm try open diskutil with CMD +R open Recovery network
I don't understand what you are talking about.
Startup - Blue Screen
Startup - Gray, Blue or White screen at boot, w/spinner/progress bar
Startup Issues - Resolve
Startup Issues - Resolve (2)

[RESOLVED] "Isolinux.bin missing or corrupt" when booting from USB.

Just giving root cause explanation and resolution to closed topic:
https://bbs.archlinux.org/viewtopic.php?id=107241
where "Isolinux.bin missing or corrupt" when booting from USB. I hope maybe someone will find it rather than closed topic 107241 :-(
Windows DD and unetbootin-windows are created for single ISO partition. That's why old Archlinux like 2010-05 will run.
The newest one archlinux-2014.01.05-dual.iso will not work like that because there is UEFI pre-boot (two partitions). That's why it can't find then Isolinux.bin and report it's missing. Of course this kind of issue will appear on old motherboard without / old UEFI support as they can't understand bootstrap and real root fs later.
unetbootin tool is partition driven so it can't do split well 32 UEFI + remaining root.
Resolution:
If you really don't have any Linux based machine to use Linux DD there is work around:
1. Install WIndows Virutalbox and extension pack
2. Download latest Archlinux ISO and run VM from it + USB support map real pendrive
3. In guest VM booted form Arch ISO just run DD if=/dev/sr0 of=/dev/sda (pay attention that SDA is real USB device then).
4. Wait about 8minutes. halt. unplug usb. Voila.
Last edited by varsovie (2014-01-15 22:20:37)

I am having this exact problem but with dd on Ubuntu 12.04 (my main distro on my main machine).
Perhaps my version of dd is too old?

Tecra M2 - boot from USB drive

Hello
Why Tecra M2 don't have boot from USB drive in BIOS?
Is posible implemented this function in new BIOS.
Bye

Hello
Good question. You should ask this the Toshiba engineers.
However, I agree with Terentino and you can do nothing.
Greets

Stuck on blank blue screen when booting- HELP!

When I boot up up I get the normal grey screening with spinning pin wheel, but then it goes to a blank blue screen and just hangs there. Tried resetting the PRAM but didn't work, also want to boot from the install cd but I can't the cd drive door to open from the keyboard button.
Help please!

Hold the mouse down during startup to get the drive to open.
Or use the OPTION key to stop at boot selector and do it then.
I would make sure to have a working bootable backup of your drive at all times, and an emergency boot drive/partition.
What might help:
Boot from another drive. Turn off journaling. Repair drive.
Once at Finder desktop, delete the caches folders on your main drive.
/Library/Caches
/System/Library/Caches
/System/Library/Extensions.mkext
If the repair was "successful" and DU is not 100% certain to see and fix all possible errors, for that Disk Warrior or TTPro would be needed.
At the least, repair from current DVD of OS X, or SAFE BOOT, or Single User Mode and run FSCK.
Then do Safe Boot from your main drive.
But do install OS X to another drive to work from.
PRAM only affects settings. If you mean PRAM/NVRAM from cold boot, that would help with corrupt nvram due to hardware changes.
If you have or suspect a corrupt boot drive I would invest in Disk Warrior and/or TechTool Pro/Deluxe to use along with Apple Disk Utility.

Won't boot from USB Drive

I am trying to replace my internal drive. I got a WD Scorpio from OWC and formatted and installed OS 10.6. But when I boot from the drive I get the panic screen.
The drive otherwise behaves normally. I can see the files, etc.
Also, strangely, the drive is only recognizable as bootable from the right USB port. That doesn't really make any sense to me.
Please help! The OWC folks have sent me multiple drives and have really tried to get this working, but I have the same result each time. Anyone out there have a solution?
Thanks.

Try prepping the drive this way:
Drive Preparation
1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.

Cannot boot from USB drive!!!!!!!!!!!!!

Hi
I have 3-4 120Gb 2.5inch drives which I clone my MacBook Pro to on rotation.
I have always been able to boot from these drives UNTIL NOW!
Suddenly I can no longer boot from them, the boot process starts and gets well through and then the drives all seem to just 'hang'.
The only significant change is that a local Apple support company upgraded my stock 120gb drive to a 160Gb drive.
Any ideas what the issue coiuld be?
Cheers.
Robin

Hi robster,
If the USB drive contains a valid OS you should be able to verify and repair the permissions on that drive, give that a try.
Also i suggest running DiskWarrior 4 on it.
The replaced internal drive should have no effect on this unless some settings got changed when the new OS got installed on it that now prevents the mac from being able to read your USB drive.
Does the USB drive need a driver ? if so is the latest version of that driver properly installed ?
If the USB drive checks out and all is OK maybe a re-install of the OS on your internal drive would help.
For now try disk utility and diskwarrior if you can that could narrow things down

Booting from USB drive on PPC

Hello everyone!
I know I will have people agree with me or possibly disagree with me, but if you goto the following site and see my pictures of my 2003 G4 MDD booting up Leopard from an external USB drive, you will see that this is fully supported. Also, what is strange is that although I found the tip through macfixit.com and other sites, one really doesn't have to go into the firmware and do anything.
As the pictures show, my USB 2.0 drive booted right into Leopard in less than 20 secs.. Please visit
http://s704.photobucket.com/albums/ww50/psychomacuser/ and see for yourself USB 2.0 in action on my system. Sorry if you have trouble reading the cyrillic, I have my system set up in Russian.

{quote}Also, what is strange is that although I found the tip through macfixit.com and other sites, one really doesn't have to go into the firmware and do anything.{quote}
Hey Nadav, thanks for the post.
What tip did you find exactly? Just that you can boot from USB?
R.

Kernel Panic when booting external USB drive (WD Essential 250GB)

Greetings...I recently was tasked with setting up three bootable external volumes for a co-worker, so I purchased a Western Digital Essential 250 GB drive.
Everything worked just fine on my end, I was able to boot into each of the three external volumes continually and then shipped the drive to my co-worker, who when he tries to boot into any of the three drives gets a kernel panic.
We are using different models of MacBookPro (15 in. 2.16 Ghz Intel Core 2 Duo) for me and MacBookPro (15 in., 2.2 Ghz dual-processor Intel) for him. We THINK it might have to do with a firmware mismatch from the two machines:
Mine:
Boot ROM Version: MBP22.00A5.B07
SMC Version: 1.12f5
His:
Boot ROM Version: MBP31.0070.B07
SMC Version: 1.16f8
...but we've never had these types of problems before, even with mismatched hardware. The OS and kernel versions (10.4.11, Darwin 8.11.1) we're running are identical, according to ASP.
The only other weird thing is his panic log registers a different kernel version than what ASP reports, though that might be normal since hardware is not my thing:
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
In short, if anyone has any ideas how we can get these drives to boot or can confirm that it is impossible with the mismatched firmware so we can move forward with a plan B, I would greatly appreciate it.

Yes, sort of.
I used 10.4.8 disks to install, but used the Apple Software Update to upgrade to 10.4.11 on two of the volumes. I was still able to boot with my machine after that however.
As an update, my co-worker was able to "fix" one of the drives by upgrading with some 10.4.9 disks he had. He is now able to boot from that drive. That is not an option with the two others since they are already at 10.4.11.

Kernel panic when booting from USB

Hi guys, I'm trying to install arch on a cd-less HW (www.linutop.com) but during boot from USB
I get this kernel panic:
:: Waiting for devices to settle...
usb 2-3.1: configuration #1 chosen from 1 choice
:: Waiting 16s for USB devices
scsi 2:0:0:0: Direct-Access CBM Flash Disk 4.00 PQ: 0 ANSI: 2
sd 2:0:0:0: [sdb]: Assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: [sdb] Attached SCSI removable disk
:: Scanning for boot device...
:: Scanning cd drives...
:: Scanning usb drives...
/dev/sdb1
squashfs: version 3.4 (2008/08/26) Phillip Lougher
Registering unionfs 2.5 (for 2.6.27-rc6)
:: Mounting root (union) filesystem
:: Mounting images
::: Binding /bootmnt to bootmnt
:: Passing control to Arch Linux Initscripts...Please Wait
/bin/run-init: opening console: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
This happens with both images archlinux-2009.02-2-ftp-i686.img and archlinux-2009.02-core-i686.img.
Have checked md5's of the downloaded files and they were correct, have also tried to double write it
to the usb stick but still the same kernel panic message.
(I can play play space invaders from the grub menu though :-) )
Many thanks for any info on this.
UPDATE:
Ups, it uses AMD Geode processor and google doesn't suggest it's i686 compatible. Can this be the reason? Please confirm and I'll mark this as solved.
Last edited by inetic (2009-03-22 23:56:39)

It is Geode LX. Thanks
Last edited by inetic (2009-03-23 12:11:32)

Logic crashing when booting from system drive clone

Hi,
So I've been copying system drive clones to another drive for backup, but I find when booting from the (internal HD) clone, Logic 9 will consistently crash on me when trying to open various brands/types of plug-ins.
For cloning I've tried SuperDuper, which I own, and Carbon Copy Cloner, which I'm running the 30 day trial of, and had identical results.
Yeah I know it's lame to be using Logic 9, but I have several important projects originally started on 9 that I need to be finishing up now, and those projects don't play nicely with Logic X.
I'd like to update my OS and Logic X versions, but want to have a working system clone before risking it.
Suggestions?
Thanks.

Um right after posting the query I remembered what I had learned probably right here back in yesteryear, and that is there is one thing that doesn't translate in the clone.
When doing Get Info on the Logic 9 app, there is a check box for "Open in 32-bit mode". I need to have that unchecked, so I can run in 64-bit mode, but for the "clone", that box gets automatically checked, it is NOT actually a clone, hence the issue I was having with plug-ins causing crashes.
Un-checking that box on the clone solved my issue.

Booting Arch-ISO from USB-Stick in UEFI mode fails

Hi there,
I'm running an Asrock H77M-ITX UEFI mobo. On this system I've already installed Arch on a Samsung 830 SSD (GPT formatted) - but in BIOS legacy mode because I've written the Arch-ISO image with "dd" to an USB-Stick (and UEFI boot mode wasn't even presented at boot).
Out of curiosity I've re-formatted the stick and copied Arch-ISO following https://wiki.archlinux.org/index.php/Un … B_from_ISO.
Now I could start the ISO in UEFI mode, but it failed to start gummiboot with the "No loader found. Configuration files in \loader\entries\*.conf are needed." error message, concerning a problem with gummiboot.
Following some advice on the forum, I did this:
- install refind-efi 0.4.7-2
- copy /usr/lib/refind/refindx64.efi to [USB]/EFI/boot and renaming it to bootx64.efi (i.e. replacing the original bootx64.efi from gummiboot)
- Create a new file in the same directory ([USB]/EFI/boot/) called refind.conf
- Add this to it:
textonly
scanfor manual
menuentry Arch {
loader /arch/boot/x86_64/vmlinuz
initrd /arch/boot/x86_64/archiso.img
options "gpt loglevel=7 add_efi_memmap none=UEFI_ARCH_x86_64"
With this I can launch Arch-ISO from the USB-Stick in UEFI mode and I can choose Arch from rEFIND. Then Arch-ISO starts booting but it always stops at the same point with this message:
sd 6:0:0:0: [sdb] No Caching mode page present
sd 6:0:0:0: [sdb] Assuming drive cache: write through
sd 6:0:0:0: [sdb] Attached SCSI removable disk
ERROR: '/dev/disk/by-label/' device did not show up after 30 seconds ...
Falling back to interactive prompt
You can try to fix the problem manually, log out when you are finished
sh: can't access tty: job control turned off
[rootfs /]#
sdb is the USB-Stick from which I start Arch-ISO. Again - I didn't use dd to write the ISO to the stick.
Maybe this is pretty easy to solve, but I have to admit that I'm somewhat stuck
Last edited by swordfish (2012-11-19 21:31:43)

WonderWoofy wrote:See what the difference is between archiso and archboot maybe? Seriously, have you made any effort whatsoever?
Of course. Read:
The "Main Page" ( https://www.archlinux.org/ ) states:
"You've reached the website for Arch Linux, a lightweight and flexible Linux® distribution that tries to Keep It Simple."
"Keep It Simple". Yeah!
In line with that, the "The Arch Way" page ( https://wiki.archlinux.org/index.php/The_Arch_Way ) states:
"The following five core principles comprise what is commonly referred to as the Arch Way, or the Arch Philosophy, perhaps best summarized by the acronym KISS for Keep It Simple, Stupid."
The ArchWiki ( https://wiki.archlinux.org/ ) links to several other pages, such as these:
The "Forum Etiquette" page ( https://wiki.archlinux.org/index.php/Forum_Etiquette ) states under "Ineffective Discussion":
"Arch is a Do It Yourself community" and "treat others as you would be treated; respect them and their views". I am very much a "do it yourself" person -- that's why I like The Arch Way. I also go by the Golden Rule stated here.
Now, everyone is a newbie at some time. I and other posters here are obviously newbies with respect to ArchLinux. Even experts were newbies at one time. Newbies, by definition, do not necessarily know what they're doing, or where to find information. Hence, Arch's "Beginners' Guide" and such. Hence, posts on this board from newbies asking for help.
As regards initial installation of ArchLinux, and consistent with the above, the FAQ ( https://wiki.archlinux.org/index.php/FAQ ), under "Q) Arch needs an installer. Maybe a GUI installer", states:
"A) Since installation doesn't occur often (read the rest of this article to know more about what rolling release means), it is not a high priority for developers or users. The Installation Guide and Beginners' Guide have been fully updated to use the command-line method. If you're still interested in using an installer, consider using Archboot."
So the basic installation instructions explicitly state that Archboot is not needed.
The "Installation Guide" ( https://wiki.archlinux.org/index.php/Installation_Guide ) says nothing about either Archboot or Archiso.
The "Beginners Guide" ( https://wiki.archlinux.org/index.php/Beginners%27_Guide ) says nothing about either Archboot or Archiso.
The "Archboot" page ( https://wiki.archlinux.org/index.php/Archboot ) is consistent with the above information, because it states:
"Archboot is a set of scripts to generate bootable media for CD/USB/PXE.
It is designed for installation or rescue operation."
The "Archiso" page ( https://wiki.archlinux.org/index.php/Archiso ) states:
"Archiso is a small set of bash scripts that is capable of building fully functional Arch Linux based live CD and USB images. It is a very generic tool, so it could potentially be used to generate anything from rescue systems, install disks, to special interest live CD/DVD/USB systems, and who knows what else."
So the pages describing both Archboot and Archiso clearly state that these tools are oriented towards already-existing installations -- even though it seems that they might be used, in certain circumstances, for initial installations.
I happen to be very new at playing around with installing Linux distros (although I've used Unix/Linux as a regular user for more than 30 years), and am brand new with respect to ArchLinux. I only began playing with it this past Saturday. So I would expect a bit of useful help as opposed to "RTFM!" I will soon get past the need to RTFM for basic tasks, but I have a way to go.
The fact is that for me and a number of other new ArchLinux users, the installation guides simply do not work. C.f. my post https://bbs.archlinux.org/viewtopic.php?id=153170 . I've done a lot of googling as well as searching the archives on this board, and others have come up against the same show-stopping installation problems that I have. I and others have posted to several recent threads on this board, trying to get past the problems, so far with no success.
Now, the.ridikulus.rat had written:
"You guys are using Archboot's kernel options for Archiso. Thats the issue in both the cases."
Given that neither of these sets of scripts were used by me or swordfish, this comment is not useful.
Given the above, can you or anyone else tell us what Archiso or Archboot might do to help us with our installation problems? Also, can you tell us how we, as newbies, ought to have found out how these might help?
Alan

Macbook will not boot. Locked hard drive. Blue screen when booting

Hi, my little brother decided he wanted a few files off of my mac book, so he went to settings>sharing>file sharing and added my only hard drive to the list and tried removing everyone but his name and password thinking it would only effect people trying to log into my hard drive, not actually me on my computer alone trying to boot mac osx from it.
He came crying to me telling me he paniced because he saw a locked icon on my hard drive and couldn't do anything, so tried to restart the macbook and now i just get a blue screen and nothing happens when i try booting it.
Right now i'm thinking i gotta archive and reinstall from booting the osx disk, but i'm affraid it'll just apply the same settings again and keep me locked out. I need files off of my hard drive since i'm in school and have several assignments that i have not backed up at all.
Any help would be greatly appreciated

after searching the forums deeper i found the solution. it's now working. you may delete this thread.
http://discussions.apple.com/thread.jspa?messageID=2087835

Blue screen when booting from USB drive in UEFI mode (2013.07)

Similar Messages

Maybe you are looking for