[SOLVED] MS-7125 boot from SATA

I have an MS-7125 whose IDE drive just died. I installed a SATA hard drive and successfully installed Ubuntu 9.10 on it but it doesn't show up as bootable in the BIOS.
Is there a BIOS setting which will allow me to boot from the SATA hard drive?
Thanks.
[SOLVED] See my last post. [/SOLVED]

Quote from: Grayone on 17-November-09, 12:54:47
Can you set it as a boot device in Advanced Bios Features -Boot Sequence. Also check to see if the onboard SATA Controller is enabled in Integrated Peripherals -Ide Devices Configuration.
In Advanced Bios Features->Boot Sequence I chose Hard Disk. Under Hard Disk Boot Priority the SATA drive simply doesn't show up. The only choice there is Bootable Add-in Cards. The BIOS doesn't seem to recognize the SATA drive.
Under Integrated Peripherals->IDE Devices Configuration everything is enabled, including SATA1/SATA2 and SATA3/SATA4.
My BIOS is "W7125NMS V1.5B2 052005 15:18:27 provided by MSI & [email protected]" which has worked perfectly for all the hardware we have on these boxes, including the previous IDE drive.
Thanks for your help with this.

Similar Messages

[SOLVED]Unable to boot from SATA, but it works from USB

I have strange problem. I made an Arch installation in VMware virtual computer and then I copied the virtual disk to new SSD. When I install the disk into the real hardware (Intel Canoe Creek D2500CC board), i get the "ERROR: Unable to find root device '/dev/sda1'." error.
The strange thing is, that the computer can boot correctly, when I connect the SSD using SATA->USB bridge.
In the recovery shell there are no disk devices (/dev/sd*) so I think it is not a problem of changed device name (f.e. /dev/sdb1 instead of /dev/sda1), to me it looks like udev is not running.
What can be the problem, that the system boots normally when SSD is connected via USB and can not boot when connected directly to SATA port?
My mkinitcpio.conf:
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect block filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev block filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev block mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev block lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
Last edited by MaVac (2014-08-15 05:55:18)

MaVac wrote:Problem solved! :-) I made update with pacman -Su and then everything is working perfectly. :-)
Then please mark the thread as solved as well.

K7N2G-ILSR: How to boot from SATA when a raid card is installed

The situation:
1. I have a separate raid controller (Silicon chip) with 2 drives on raid 0.
2. I have another drive (my boot drive) that I want to place on the onboard Promise SATA raid controller.
The problem:
The bios doesn't include an option to specifically boot from SATA, only SCSI. So when I place my boot drive to the onboard Promise SATA raid controller, the system won't boot because it's looking for system files on the raid 0 drive.
Is there a workaround for this?

Well, all my drives are IDE. I did try the SATA RAID using lumberjacker's bios but it isn't stable.
Aside from 3 IDE drives, I also have 2 atapi drives (cdr-w, dvd).
Here's my current setup:
ide 0 - boot drive (master), DVD (slave)
ide 1 - cdr-w (master)
onboard ide (sata controller) - (vacant)
SATA 1 - (vacant)
SATA 2 - (vacant)
promise raid card (2 ide ports)- 2 hard drives on raid 0 (both as master)
What I really want to do is place my boot drive on the SATA port (using a pata to sata converter), or on the onboard promise parallel port. So that it can have it's own port.

Wich Sun machines can boot from SATA disk?

Hi,
I would like to know which (newer and older) Sun machines can boot from SATA disks.
I think this is a feature of the OBP - so the question is:
Are there any updated OBPs for older Sun machines to boot from SATA disks?
TIA
Bernd

Hi,
I am aware the limit with earlier openboot revisions that limit ATA drive size to +130GB>>( search the forum for previous threads on this topic ), I recommend using only
supported drives in Sun SPARC systems. What kind of project are you working on? That's my private test environment. Due to my limited budget I use only older machines there (for example, U10, U30, etc). I was thinking about buying a used V120 or something like that to replace my existing fileserver.
A V120 with two internal 500 GB harddisks would be perfect for that .
Looks like I've to wait until used T1000 are available to a reasonable price.
regards
Bernd

Mainboard PM8M-V cannot boot from SATA

Mainboard PM8M-V does not have BOOT FROM SATA in the BIOS settings. In fact nowhere in the entire bios SATA is mentioned.
The SATA HDD is properly partitioned. Windows is installed on it, but it boots from an IDE HDD and then continues to load from the SATA.
I tried to set the bios to boot from SCSI, but in vain.
I checked if there is a bios update, but the MSI website linked me to Live Update 5, which even cannot find drivers for the mainboard, not to speak for a bios update.
The version of the BIOS is
Manufacturer : Phoenix Technologies, LTD
Version : 6.00 PG
Date : 03/23/2005 (mm/dd/yyyy)
HELP!

The boot options are:
Floppy, LS120, IDE0,SCSI,CDROM,IDE1,IDE2,IDE3,ZIP100,USB-FDD,USB-CDROM,USB-HDD,LAN,DISABLED
I tried to remove the IDE HDD (also no USB drives were connected) while installing windows, it won't boot anyway.
Even if windows did not write correctly the MBR (well, I used the repair console to with FIXMBR and FIXBOOT), the BIOS should probably say something like "No boot sector", but it just hangs.
After that I installed with an IDE HDD connected.
Presuming that "as i recall boards of yours age listed all drives as ide" is true, shouldn't I have IDE5, since there are 4 IDE channels anyway? I will try all the IDE options, anyway.
I did not understand this question "is the make and size of the sata in that list"?
Quote from: Henry on 06-July-12, 07:31:06
It should ID the drive by model number or at least by brand & size as Wonkanoby said, at least it does on newer MBs.
Some options of the device are shown during boot (some RAID adjustments), but it is not displayed anywhere in the BIOS setup.
Also, on most bioses during oot a message is displayed "Press key XXX for boot options", but this one does not display something like this. Any clue if there could be such a key? F1 and F8 do not work.

How to boot from SATA on a K7N2 Delta2 Platinum

Hi guys,
here is my problem, I've just bought a brand new HD Samsung SATA II 2504C, once connected to the MB I can' t boot from it, even if I change the boot sequence.
I have already two HDs connected to IDE ports, under XP I can format it, I can even install a Linus distro such as Elive, but it refuses to boot.
Is there a trick?
K7N2 Delta2 Platinum
BIOS: B5 1/20/2005
AMD 3000+
2 HDs UMDA 133
2 DVD writer LG and SAMSUNG
1 HD on SATA, which causes me troubles.

disable IDE RAID and ensure SATA is enabled in BIOS
disconnect any other IDE HDDs before you install Windows to your SATA drive; they can be reconnected again afterwards.
make sure that the SATA drive is listed first in 'Hard Disk Priority' under 'Boot Order' in BIOS

[SOLVED] can't boot from ssd after "reset" from recovery usb flash drive

I have a Twist s230u with the original Hitachi 500GB hdd, running Windows 8.1. I want to replace the Hitachi 500GB hdd in my Twist s230u with a PNY 240GB SSD that i've purchased.
While running Windows from the Hitachi HDD drive I followed the "create a recovery drive" procedure to create a recovery usb. Then I removed the Hitachi HDD from the s230u and installed the PNY 240 SSD in its place. I booted the s230u from the recovery flash drive that I made. I selected the "Reset Your PC" option and then the option to wipe all partition/files. After the Reset completes, I try booting from the SSD but am unable to do so. I just go back to the F12 boot menu.
I put the SSD in a drive dock attached to another computer. Disk Management shows the partitions as follows -
I've looked at the partitions on the SSD after the Reset - Disk Management console shows a 1000 MB Recovery partition, a 260MB EFI System partition, and a 221GB primary partition with volume label Windows8_OS. It is not marked as Boot, Page File, or Crash Dump.
Diskpart shows an an additional 128MB Reserved partition between the EFI partition and the primary partition.
I do notice that the 10.6 Lenovo Recovery partition is not present - but I did make sure that I included that partition on the recovery key - though the files on the recovery key only use 8.03 GB for some reason. Made the key on two different flash media.
Diskpart also shows the following for the SSD:
DISKPART> attributes disk
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
(It also looks like this when I run DISKPART from the recovery media with the SSD inside the internal drive bay of the s230u.)
When I did the Reset on the SSD in the s230u, and when I tried to boot from it - I had the Secure Boot disabled, the "Legacy Boot first" option set, etc.
Can anyone point me in the right direction to be able to boot Windows 8.1 from this SSD in the s230u? I've been working on this for a couple of days.
(I also tried cloning the HDD to the SDD using Minitool Partition Wizard, Macrium Reflect, Clonezilla, Acronis, etc - the SSD wouldn't boot after those clone operations either, and I thought maybe I'd have better luck with a reinstall from the USB recovery media.
(I also tried installing from a Windows 8 iso I burned to a DVD. I got a product id mismatch message when I tried to install from that, and I was not allowed to proceed.)

well, I seem to have solved my own problem. Maybe someone will learn from my mistakes.
I went into System Setup, went to the Startup tab, and changed the boot setting from "Both" to "UEFI Only". After doing this I booted from my USB recovery drive, and Reset the PC. After the Reset, I booted the s230u from the ssd, and I booted into a fresh Windows 8 installation.
It seems that the Reset operation could not work properly while the boot setting was "Both" (UEFI and Legacy) and "Legacy First."
I got a clue when I looked at the contents of the EFI System Partition and there was nothing there except a Temp folder. The EFI System Partition had not been properly written by the Reset operation. I got some helpful hints on how to see the contents of the EFI System Partition here - http://www.fixedbyvonnie.com/2013/12/how-to-repair-the-efi-bootloader-in-windows-8/#.U-Qz2_ldW7q
I've also buggered up my original HDD now, so that it won't boot to Windows now. Now to fix that!

Booting From SATA on K8N Neo2 Plat

I've read all the posts I can find. I downloaded the newer nforce drivers. I've tried running from 3/4 instead of 1/2. I've done the install every which way, no floppy driver install, install just bridge driver and install bridge+raid.
Here's the deal. Using just one 74Gig Raptor I want to install XP and boot from it. I get completely through the install but I get a boot error when XP reboots and tries to run from the HD for the first time.
If I install the raid driver I can see and setup the HD in the Raid config app during boot. But, it still gives me the same boot partition error when it hits the drive.
Any ideas?

This may be pertinent or it may not.
I recently spent 2-3 days trying to get 64 bit Windoze to boot on my system after successfully installing XP Pro with no difficulties whatsoever. I think what I did wrong was to install the OS with my IDE drive disabled.
Since I did not partition my SATA drive I found that I had to install x64 on another partition due to shared "Program File" issues with 32-bit and 64-bit apps.
I then discovered that even though I told the BIOS to boot off the SATA drive before the IDE drive that x64 wanted to order the drives differently. It insisted on putting the DOS partition on my IDE drive first, the SATA drive second, and the NTFS partition on my IDE drive third. It then wrote the boot.ini info for x64 onto the DOS partition instead of the SATA.
Long story short I could not get it to see x64 when it rebooted the first time. I tried screwing around with the boot.ini settings until I was blue in the face.
I finally decided to buy Partition Magic and partition the SATA drive. I installed x64 onto it and it once again wrote the boot.ini info to my DOS partition instead of the SATA first partition so I edited the boot.ini record on my SATA drive to point it to the second partition and it worked.
The bottom line is that I think there are some real compatibility issues with x64 in a dual boot environment. MS is also editing the private news group so lessons like this don't see the light of day to scare off the other human guinea pigs who are beta testing their crapware for free. Caveat emptor. TANSTAAFL.

Boot from SATA not IDE

When i have my main drive (wich is a 160Gb SATA drive pluged into SATA3) on its own it boots up fine. However when i have a 40Gb IDE drive pluged into the primary master the system trys to boot from this rather than the 160Gb drive. The only way I have found to boot from the 160Gb drive is to press F11 on boot and select it. This is annoying as the machine cant just switch on. Is there a way to change this? Thanks alot.
Mike

In the BIOS you need to change the boot priority to the SATA drive.
I cant remeber which section it is in, but it is there.

Boot from SATA HD

Hello,
I want to buy one Mobo MSI K9NGM2 and booting from a single HS SATA (without RAID configuration). How can I do? What are the different steps (not clear in the manual).
Thanks.

Nothing special you have to do, just set it to Native Sata and install Windows on it.
That the way it worked for my K9N Plat and K9A Plat

PT880 Neo-FSR not booting from SATA device

Hi everybody!
MSI PT880 Neo-FSR http://global.msi.com.tw/index.php?func=proddesc&maincat_no=1&cat2_no=&cat3_no=&prod_no=608
As read on the topic subject, I'm having trouble trying to boot up using my new SATA DVD-RW. This device works perfect while running Windows XP on my PC, but when I try to boot from it, I simply can't.
My PT880 Neo-FSR mobo is running the latest avalaible BIOS version (2.0) and Internal SATA controller and SATA boot ROM function are enabled. Looking inside the booting options, I just can't set my SATA DVD-RW as a valid device for booting up (I only see my IDE HDDs, FDD and LAN as booting options).
This is my first time triying to boot up from this SATA device and the first time I realized that I can actually use it for anything but booting, which is so weird! I even tried installing this device on my brother's PC and booted up succesfully there, so my mobo is the problem here.
If you're asking yourselves how I installed Win XP on this PC with no CD/DVD booting: My former IDE DVD-RW is now my sister's, so I kept previously instalation and just changed devices.
I need to run some utlities from a boot-CD and re-install Windows on this PC real soon, so I'd appreciate some help.
P.S. I tried to do my best with my 'rusty' English, so I hope you could fully understad what I've written above.

Quote from: Henry on 03-September-08, 14:26:24
Are you saying it does work but you simply can't boot from it? Have you tried by using the F11 boot menu?
Yes! This device has been working great, but the only problem I get is when I try to use it for booting.
I alredy tried using the F11 boot menu and nothing happened... It's so weird!

[VIA] Cannot Boot From SATA PCI Controller With On Board RAID Enabled

Hi.
I have a KT3 ULTRA 2 with onboard RAID controller. I have installed a SUNIX 2 port SATA PCI Controller which works perfectly & appears in the selectable boot devices. This is not a problem except for the fact that I have 4 devices on the On-Board Raid Controller. When the on-board raid controller is enabled, the SATA device dissapears from the boot options & I can no longer boot from the SATA controller.
Any help is greatly appreciated.
Many Thanks

I had already tried that....
I set the boot sequence to use the SATA card & then renabled the on-board raid, but after reboot the sata card is not available as a possible boot device & asks me to insert system disk...even if the boot sequence is set to boot from other devices.
Really annoyying this, looks like I am going to have to get a different motherboard for something so silly. I am already at the latest bios release.

[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.

[SOLVED]Hanging after booting from installation media

Yesterday I booted from a rw-DVD got to the terminal and could execute commands, connect to the internet and use elink etc no problem. I didn't go through with installation as I wanted to read up more on partitioning my drives for dual booting before actually doing so.
Trying the same thing today, and it hangs soon after I boot, regardless of whether I do anything. Printing the following:
nouveau E[ DRM] failed to idle channel 0xcccc0000 [DRM]
pci_pm_runtime_suspend(): nouveau_pmops_runtime_suspend+0x0/0xf0 [nouveau] returns -16
INFO: rcu_preempt detected stalls on CPUs/tasks: { 6} (detected by 1, t=18002 jiffiess, g=974, c=973, q=604)
This is without me typing anything. If I try to execute a command quickly after booting it sometimes works, but after a couple of minutes it will complain of a soft lockup.
I've tried burning another disk, and using a USB installation media, but the same thing happens. Any thoughts?
Edit: Trying to run it on a laptop with i7-4700MQ, 16GB ram, and Intel(R) HD Graphics 4600 / NVIDIA GeForce GTX 770M
Second Edit: Booted with nomodeset, which worked and allowed me to install. Just trying to sort out the sodding boot loaders now...
Last edited by glfharris (2014-07-11 22:42:31)

Welcome to the forum.
First of all, you should get in the habit of using [ code ] tags when posting code, not [ quote ] tags (well, unless you want to apply some styling to it, like bold, italic, etc).
This is wrong:
# umount /dev/sdc
This is correct:
# umount /dev/sdc1
You were trying to unmount the drive as a whole, which obviously isn't mounted, instead of the first (and probably only) partition. Had you followed the advice from the note to use blkid and check if it's mounted, this wouldn't have happened. But the fact that a DVD produced that error puzzles me... I have no experience with UEFI, but I think you need to press F10, F11, or something like that, to able able to get to a UEFI boot menu, and choose the optical unit as source.
I hope you used a BitTorrent client when downloading the ISO, and not some direct link (which are prone to CRC errors). If you used a direct link, then check the MD5 and make sure that it matches the one from the Download page. For future reference, torrents are checked while they're being downloaded.

[SOLVED] UEFI system booting from MBR partition table and GRUB legacy

I'm trying to understand once and for all the process by which Arch can be booted from a system with UEFI firmware and an MBR partition table. Some of the information on the wiki seems conflictual / non-nonsensical at times. Apologies in advance if this has been answered time and time again, but I did search around and all I found was fixes to get Arch to boot rather than comprehensive explanations of the boot process.
Now, the way I would imagine it works is that it's just completely identical to the way it would work with a BIOS firmware. The UEFI firmware detects an MBR partitioning scheme (or is configured to know it's an MBR partitioning scheme), activates some "legacy" mode and executes the MBR boot code, just like a BIOS firmware would.
The wiki however, says different. From the Macbook article: "Do not install GRUB onto /dev/sda !!! Doing so is likely to lead to an unstable post-environment."?
So what is there in the MBR boot sector? Nothing?
How does the firmware know what to boot if there's no 0xEF BIOS boot partition and no Grub stage 1 in the MBR boot sector?
Also, how does installing Grub stage 1 to a partition work? Does it have to be at the beginning of the partition? Wouldn't that overwrite some existing data?
I'm especially puzzled since many guides to installing Vista on a macbook recommend simply formatting as MBR, and installing as normal, which I suppose entails having the Windows installation process write its boot code to the MBR, ie the equivalent of installing grub stage 1 to /dev/sda rather than to the /boot partition, as the Macbook article suggests.
Any input is appreciated.
P.S. I realize it's probably simpler, if I just want to dual boot Windows and Arch, to install Windows 7 in UEFI-GPT mode, let it create the EFI System Partition, and then install GRUB 2 to that partition, but I'm still curious about the UEFI-MBR boot process.
Last edited by padavoine (2012-06-06 09:35:10)

padavoine wrote:
CSM in UEFI firmwares do the exact same job as normal BIOS firmware.
So it's something specific to the Mac that it's able to boot from a partition's VBR while ignoring the MBR?
The reason that warning is given is because grub-legacy modifies more than just the MBR boot code region. It can overwrite some parts of GPT header.
Not true, the instruction is given in the context of an MBR format, not in the context of a GPT format, so there's nothing to overwrite and Stage 1.5 should be safely embeddable in the post-MBR gap.
In BIOS boot (normal case in non-UEFI firmwares or CSM in UEFI firmwares) does not read the partitition table (atleast it is supposed to be dumb in this regard), it simply launches whatever boot code exists in the 1st 440-byte of the MBR region.
So again, you're saying it's specific to the Mac UEFI that it lets you choose a partition whose VBR to load, regardless of what's in the MBR?
I haven't used Macs so I can't comment on Mac firmware behaviour. But normal BIOS firmwares (legacy and CSM) launch only the MBR boot code and not the partition boot code. We need some chainload capable boot manager in the MBR to launch the partition VBR.
grub-legacy does not know anything about GPT. So when you install grub-legacy to /dev/sda, it install the MBR boot code (stage1) and stage 1.5 code to the (supposed) post MBR gap. Since there is no actual post MBR gap in GPT (which has been taken over by the header and partition table), grub-legacy does not check for GPT and it assumes the post MBR gap actually exists which is invalid in case of GPT. grub-legacy embeds the stage 1.5 code in GPT header and table region (which grub assumes to be unused post MBR gap) and thus corrupts it.
0xEF is the MBR type code for UEFISYS partition. grub stage 1 (used in grub-legacy, not in grub2) is the 440-byte boot code stored in MBR for use in BIOS boot.
That's precisely my point: with neither proper executable code in the MBR (since grub was installed to a partition, not to the MBR) nor a UEFI system partition, what does the firmware default to, and how does it know what partition to boot from?
In that case it might fallback to UEFI Shell (if it exists) or give an error similar to the case where BIOS does not find any bootable code in 440-byte MBR region.
So even with bootcamp/CSM, the disk also needs to be MBR partitioned. So Macs use something called "Hybrid GPT/MBR" ( http://rodsbooks.com/gdisk/hybrid.html ) where the MBR table is synced to match the first 3 partitions in the GPT table.
I know what Bootcamp does, and that's not what I was referring to. I was referring to standalone Vista installs. I wasn't puzzled at the fact that they were using MBR, I was puzzled at the fact that contrary to the recommendations for the standalone Arch install on the wiki (with MBR partitioning, not GPT), they didn't do anything to try and prevent Windows from writing to the MBR.
You can't prevent Windows from overwriting the MBR region. You have to re-install the bootloader (grub2/syslinux etc.) after installing Windows. That is the reason why it is recommended to install Windows first and linux later.
Thats not true. I actually find it is much easier to install Windows UEFI-GPT using USB rather than a DVD.
I haven't done it since the only UEFI system I own has no DVD drive, but I was under the impression that it was simply a matter of choosing DVD UEFI boot in the firmware's boot menu.
format the USB as FAT32 and extract the iso to it. That it.
No, thats not it, precisely, it doesn't work out of the box with a standard Windows install USB, you need to fiddle around:
2.3 Extract bootmgfw.efi from [WINDOWS_x86_64_ISO]/sources/install.wim => [INSTALL.WIM]/1/Windows/Boot/EFI/bootmgfw.efi (using 7-zip aka p7zip for both the files), or copy it from C:\Windows\Boot\EFI\bootmgfw.efi from a working Windows x86_64 installation.
2.4 Copy the extracted bootmgfw.efi file to [MOUNTPOINT]/efi/microsoft/boot/bootmgfw.efi .
Most of the Windows isos already have /EFI/BOOT/BOOTX64.EFI file, so no need to extract the bootmgfw.efi file.
There is no difference between in BIOS booting in UEFI firmwares and BIOS booting with legacy firmware.
There has to be a difference, at least in the Mac firmware (sorry, I keep switching), since legacy firmware, AFAIK, cannot chainload a bootloader in a partition's VBR without there being some sort of "stage1" code in the MBR.
No idea about Mac EFI. Apple made a spagetti out of UEFI Spec. To actually understand how Mac firmwares work, read the blog posts by Matthew Garrett of Redhat, about his efforts in getting Fedora to boot in Macs.

[SOLVED] MS-7125 boot from SATA

Similar Messages

Maybe you are looking for