I recently got an ASUS M32AD Desktop with Windows 8.1 OEM'd on a SATA 1 TB HD, (Disk0). I'm trying to chainload a PATA Maxtor 160GB HD with deb 7 from my old Desktop. W-8 acknowledges the drive is there, (Disk1), Local Disk (E:).
The UEFI BIOS Utility won't acknowledge the MBR of the 2nd HD. [Disk 0: Partition Style: GUID Partition Table (GPT)] [Disk 1: Partition Style: Master Boot Record (MBR)]
I've installed Paragon ExtFS for Windows and installed the appropriate IDE Adapter.
I downloaded rEFInd [http://www.rodsbooks.com/refind/installing.html]. I'm having difficulty understanding the Installation Drill In Step 3. The downloaded files are currently located:
I am not a Windows/MS user so I am lost and feeling rather sheepish. I don't know if I was supposed to move them, unpack them, or what. I ran Step 2:
C:\Windows\system32> mountvol S: /S
C:\Windows\system32> cd /S
The system cannot find the path specified.
C:\Windows\system32> cd /S:
The filename, directory name, or volume label syntax is incorrect.
If volume /S is mounted, how do I verify it?
FWIW, per W-8.1
Microsoft DiskPart version 6.3.9600
DISKPART> select disk 1
Disk 1 is now the selected disk.
DISKPART> list partition
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 9 GB 31 KB
Partition 2 Primary 486 MB 9 GB
Partition 3 Primary 27 GB 9 GB
Partition 0 Extended 13 GB 37 GB
Partition 4 Logical 13 GB 37 GB
So far, in the UEFI Bios Utility, I've disabled the [Fast Boot] option and changed [Launch CSM] from [Auto] to [Enabled].
Nevertheless; [Boot Manager][Boot Menu] still reads:
Windows Boot Manager (P1: Toshiba DTO1....)
(P4: ATAPI DH-24AESH)
(P1: Toshiba DT01... (953869MB)
I've been at this for weeks. I'm totally frustrated. I was fixin' to go out and beat a Mazda to death with the neightbour's cat; ... which I would deeply regret since I've always been a car person.
rooster64
Last edit: rooster64 2014-11-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You need to unpack the rEFInd .zip file and cd into it. It will not be on the S: drive; it will probably be on the C: drive, but that depends on where you unpack it. Thus, you'd do something like cd \path\to\refind, without referencing S: or /S.
There is another way to do this, though, which you might find easier:
Using any working, download and prepare the USB flash drive or CD-R version of rEFInd. There are download links on the rEFInd downloads page. If you're comfortable with Linux, you should have no trouble creating a boot medium in Linux. I'm not sure what tools you'd use to copy the USB flash drive image file in Windows, though.
If necessary, disable Secure Boot on your target computer.
Boot to the rEFInd medium, using the target computer's own built-in boot manager. (You typically use a function key during boot to get to it, but that's variable from one model to another.)
You should now be able to boot your old Debian installation using rEFInd. If you do not have a separate /boot partition, just locate the kernel and hit Enter. If you used a separate /boot partition, though, you'll need to hit F2 or Insert twice and add a root={whatever} specification to identify your root filesystem.
Once Debian boots, install the rEFInd Debian package.
If you want to use Secure Boot, you'll need to install a Shim binary, as described on the rEFInd Secure Boot page; then you'll have to re-enable Secure Boot in your firmware.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First, it feels peculiar addressing someone with my name and initials...
"If necessary, disable Secure Boot on your target computer." This was giving me no end of grief... the drills I found on the net don't work for the OEM installation of Windows 8.1 I got. There isn't an "Update and recovery" clickable where 'the problem solvers' have it on their PCs. To make a short story of it, under [Boot \ Secure Boot Menu], although there is no way to Disable Secure Boot in the BIOS as you well know, there is the option to choose {Other OS}. When I did this, Boot Menu Pop UP changed: the Maxtor HD designation changed from unavailable to available. I was able to boot my Linux HD from the UEFI BIOS Utility.
The upshot here is, I don't think I need your lovely Boot Manager. But I must say, I learned a lot from your labours and numerous postings. Goodonya.
Happy trails,
roderick w. s.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is driving me crazy. It worked before. Now it just goes back to that goddam windows.
The BIOS pop up no longer shows the option to boot into my Maxtor HD.
DAmn!!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are at least two possible explanations, which may interact with one another:
Windows sometimes gets compulsive about setting its own boot loader as the default boot program. The result is a difficulty in getting any other default to "stick."
Some EFIs are badly broken in any of a million different ways. With respect to your specific symptoms, some EFIs can "forget" settings that you enter.
There are a number of solutions, although some might be better called "workarounds:"
Update your firmware. (Manufacturers call it a "BIOS," but really it isn't; it's an EFI.) Note that this may require re-registering your boot programs with the firmware (with efibootmgr in Linux, bcdedit in Windows, etc.).
Using efibootmgr (or whatever is convenient), remove all the boot program registrations and then add back the ones you want. This is risky, though; some computers may misbehave and refuse to boot after you do this. Thus, I recommend trying this only as a last resort.
Use the Windows bcdedit command to set the default boot program. This tends to make Windows behave itself. You could set rEFInd (or anything else that lets you select the OSes you want) as the default in this way. The rEFInd Windows install instructions tell you how to set up rEFInd from Windows, but if the program is already installed, you really only need steps #1 and #9 (and maybe #2, to check a filename). You'd adjust the command for whatever program you want to set up.
Rename the Windows boot loader and put your preferred boot program in its place. This approach is described in the rEFInd documentation. This is an ugly hack, but it gets the job done with some of the more broken EFIs. A similar hack is to use the default boot program filename (EFI/BOOT/bootx64.efi) for your preferred boot program, and de-register everything else.
Completely remove Windows, including its boot loader. This helps some systems to "settle down" and behave themselves, at least a bit.
Return the computer to the store and tell the manufacturer why you did so! EFIs have been almost universal for over two years now, so there's no longer an excuse for such badly broken EFIs. If manufacturers don't see returns because of these problems, though, they'll keep pushing out junk. Unfortunately, many people are reluctant to return their computers over these issues. Of course, this option only applies if you believe the problem is fundamentally caused by the EFI, not by Windows or something else.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Roderick;
Your response is greatly appreciated. Delay acknowledging on my part unavoidable; ... long story.
You wrote: "Update your firmware. (Manufacturers call it a "BIOS," but really it isn't; it's an EFI.) Note that this may require re-registering your boot programs with the firmware (with efibootmgr in Linux, bcdedit in Windows, etc.)"
I'm having go at this. I'm still stuck with W-8.1. I trust what you've written. Same time, I'm pretty sure I've been 'getting the run around' by the seller, MS on-lne support personnel, and by a couple of other sources that I suspect have vested interests in supporting MS. To whit: "For most PCs, you can disable Secure Boot through the PC’s firmware (BIOS) menus. For logo-certified Windows RT 8.1 and Windows RT PCs, Secure Boot is required to be configured so that it cannot be disabled." http://technet.microsoft.com/en-us/library/dn481258.aspx
I take this with a grain of NaCl only because my sense is MS would be subject to "Restraint of Trade" in the US and several "Non-competion" clauses in Canada if they colluded with agents or suppliers, e.g., ASUS, to prevent Open Source Operating Systems to function on/with their OEM Software.
My point being, I can't figure out a way to disable "Secure Boot" in the BIOS. Those who are able to do this have a [Security] option in the UEFI BIOS Utility* Banner along with [Advanced] and [Boot]. "Note Before setting BCDEdit options you might need to disable or suspend BitLocker and Secure Boot on the computer."
<SNIP> "The easiest way to create a new boot entry is to copy an existing entry and then modify it as you need. To do this, use BCDEdit with the /copy option." http://msdn.microsoft.com/en-us/library/windows/hardware/ff541231%28v=vs.85%29.aspx#adding_a_new_boot_entry_in_windows_vista_and_later
FYI
BIOS Version ............. 0507 x64
ME Version ................9.0.30.1482
Build Date .................. 04/02/2014
South Bridge Stepping 05/02
So my questions are:
1. Can I disable Secure Boot?
2. How can I find an existing entry to copy for the Maxtor HD? I got it to boot once.
roderick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Microsoft's requirements are that Secure Boot must be disable-able on x86 and x86-64 PCs, but that it must not be disable-able on ARM-based computers. If your computer has an x86 or x86-64 CPU (the only CPUs supported by my own binary builds of rEFInd at the moment), then either there is an option to disable it in your firmware (no matter how hard to find) or the manufacturer is in violation of its agreement with Microsoft.
I'm afraid that I can't tell you where the option to disable Secure Boot is on your device because there's no standardization of this detail. Some manufacturers have hidden this option quite thoroughly, by using obscure names (such as "Windows boot mode" for Secure Boot) or by hiding the relevant option until some other option is set.
As to finding an entry to copy it, the information you've quoted is from the Microsoft site and refers to Microsoft's tools. I'm far from an expert with these tools, so I can't help with that. You should be aware, though, that you do not boot disks in EFI; you boot program files. That may sound like splitting hairs, but if you come at EFI with too much BIOS-related mental baggage, you'll find yourself going down twisty dead-ends.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I recently got an ASUS M32AD Desktop with Windows 8.1 OEM'd on a SATA 1 TB HD, (Disk0). I'm trying to chainload a PATA Maxtor 160GB HD with deb 7 from my old Desktop. W-8 acknowledges the drive is there, (Disk1), Local Disk (E:).
The UEFI BIOS Utility won't acknowledge the MBR of the 2nd HD.
[Disk 0: Partition Style: GUID Partition Table (GPT)]
[Disk 1: Partition Style: Master Boot Record (MBR)]
I've installed Paragon ExtFS for Windows and installed the appropriate IDE Adapter.
I downloaded rEFInd [http://www.rodsbooks.com/refind/installing.html]. I'm having difficulty understanding the Installation Drill In Step 3. The downloaded files are currently located:
I am not a Windows/MS user so I am lost and feeling rather sheepish. I don't know if I was supposed to move them, unpack them, or what. I ran Step 2:
The system cannot find the path specified.
The filename, directory name, or volume label syntax is incorrect.
If volume /S is mounted, how do I verify it?
FWIW, per W-8.1
Microsoft DiskPart version 6.3.9600
DISKPART> select disk 1
Disk 1 is now the selected disk.
DISKPART> list partition
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 9 GB 31 KB
Partition 2 Primary 486 MB 9 GB
Partition 3 Primary 27 GB 9 GB
Partition 0 Extended 13 GB 37 GB
Partition 4 Logical 13 GB 37 GB
So far, in the UEFI Bios Utility, I've disabled the [Fast Boot] option and changed [Launch CSM] from [Auto] to [Enabled].
Nevertheless; [Boot Manager] [Boot Menu] still reads:
Windows Boot Manager (P1: Toshiba DTO1....) (P4: ATAPI DH-24AESH)(P1: Toshiba DT01... (953869MB)
I've been at this for weeks. I'm totally frustrated. I was fixin' to go out and beat a Mazda to death with the neightbour's cat; ... which I would deeply regret since I've always been a car person.
rooster64
Last edit: rooster64 2014-11-22
You need to unpack the rEFInd
.zipfile andcdinto it. It will not be on theS:drive; it will probably be on theC:drive, but that depends on where you unpack it. Thus, you'd do something likecd \path\to\refind, without referencingS:or/S.There is another way to do this, though, which you might find easier:
/bootpartition, just locate the kernel and hit Enter. If you used a separate/bootpartition, though, you'll need to hit F2 or Insert twice and add aroot={whatever}specification to identify your root filesystem.Roderick;
First, it feels peculiar addressing someone with my name and initials...
"If necessary, disable Secure Boot on your target computer." This was giving me no end of grief... the drills I found on the net don't work for the OEM installation of Windows 8.1 I got. There isn't an "Update and recovery" clickable where 'the problem solvers' have it on their PCs. To make a short story of it, under [Boot \ Secure Boot Menu], although there is no way to Disable Secure Boot in the BIOS as you well know, there is the option to choose {Other OS}. When I did this, Boot Menu Pop UP changed: the Maxtor HD designation changed from unavailable to available. I was able to boot my Linux HD from the UEFI BIOS Utility.
The upshot here is, I don't think I need your lovely Boot Manager. But I must say, I learned a lot from your labours and numerous postings. Goodonya.
Happy trails,
roderick w. s.
This is driving me crazy. It worked before. Now it just goes back to that goddam windows.
The BIOS pop up no longer shows the option to boot into my Maxtor HD.
DAmn!!!
There are at least two possible explanations, which may interact with one another:
There are a number of solutions, although some might be better called "workarounds:"
efibootmgrin Linux,bcdeditin Windows, etc.).efibootmgr(or whatever is convenient), remove all the boot program registrations and then add back the ones you want. This is risky, though; some computers may misbehave and refuse to boot after you do this. Thus, I recommend trying this only as a last resort.bcdeditcommand to set the default boot program. This tends to make Windows behave itself. You could set rEFInd (or anything else that lets you select the OSes you want) as the default in this way. The rEFInd Windows install instructions tell you how to set up rEFInd from Windows, but if the program is already installed, you really only need steps #1 and #9 (and maybe #2, to check a filename). You'd adjust the command for whatever program you want to set up.EFI/BOOT/bootx64.efi) for your preferred boot program, and de-register everything else.Roderick;
Your response is greatly appreciated. Delay acknowledging on my part unavoidable; ... long story.
You wrote:
"Update your firmware. (Manufacturers call it a "BIOS," but really it isn't; it's an EFI.) Note that this may require re-registering your boot programs with the firmware (with efibootmgr in Linux, bcdedit in Windows, etc.)"
I'm having go at this. I'm still stuck with W-8.1. I trust what you've written. Same time, I'm pretty sure I've been 'getting the run around' by the seller, MS on-lne support personnel, and by a couple of other sources that I suspect have vested interests in supporting MS. To whit:
"For most PCs, you can disable Secure Boot through the PC’s firmware (BIOS) menus. For logo-certified Windows RT 8.1 and Windows RT PCs, Secure Boot is required to be configured so that it cannot be disabled."
http://technet.microsoft.com/en-us/library/dn481258.aspx
I take this with a grain of NaCl only because my sense is MS would be subject to "Restraint of Trade" in the US and several "Non-competion" clauses in Canada if they colluded with agents or suppliers, e.g., ASUS, to prevent Open Source Operating Systems to function on/with their OEM Software.
My point being, I can't figure out a way to disable "Secure Boot" in the BIOS. Those who are able to do this have a [Security] option in the UEFI BIOS Utility* Banner along with [Advanced] and [Boot].
"Note Before setting BCDEdit options you might need to disable or suspend BitLocker and Secure Boot on the computer."
<SNIP>
"The easiest way to create a new boot entry is to copy an existing entry and then modify it as you need. To do this, use BCDEdit with the /copy option."
http://msdn.microsoft.com/en-us/library/windows/hardware/ff541231%28v=vs.85%29.aspx#adding_a_new_boot_entry_in_windows_vista_and_later
FYI
BIOS Version ............. 0507 x64
ME Version ................9.0.30.1482
Build Date .................. 04/02/2014
South Bridge Stepping 05/02
So my questions are:
1. Can I disable Secure Boot?
2. How can I find an existing entry to copy for the Maxtor HD? I got it to boot once.
roderick
Microsoft's requirements are that Secure Boot must be disable-able on x86 and x86-64 PCs, but that it must not be disable-able on ARM-based computers. If your computer has an x86 or x86-64 CPU (the only CPUs supported by my own binary builds of rEFInd at the moment), then either there is an option to disable it in your firmware (no matter how hard to find) or the manufacturer is in violation of its agreement with Microsoft.
I'm afraid that I can't tell you where the option to disable Secure Boot is on your device because there's no standardization of this detail. Some manufacturers have hidden this option quite thoroughly, by using obscure names (such as "Windows boot mode" for Secure Boot) or by hiding the relevant option until some other option is set.
As to finding an entry to copy it, the information you've quoted is from the Microsoft site and refers to Microsoft's tools. I'm far from an expert with these tools, so I can't help with that. You should be aware, though, that you do not boot disks in EFI; you boot program files. That may sound like splitting hairs, but if you come at EFI with too much BIOS-related mental baggage, you'll find yourself going down twisty dead-ends.