Refind boot menu label

I have created a refind.conf manually:
timeout 3
scanfor manual
textonly true
textmode 1024
menuentry "ArchLinux" {
volume 71bd290b-d32a-4463-b4d7-99ee7c761af4
loader /boot/vmlinuz-linux
options "root=UUID=b61e88c7-153f-456b-9aac-421fc128b08a ipv6.disable=1 rw systemd.unit=graphical.target initrd=/boot/intel-ucode.img"
initrd /boot/initramfs-linux.img
submenuentry "Force fsck" {
add_options "fsck.mode=force"
menuentry "System Rescue CD" {
volume 71bd290b-d32a-4463-b4d7-99ee7c761af4
loader /boot/sysrcd/isolinux/rescue64
options "subdir=/boot/sysrcd setkmap=be docache video=HDMI-A-1:d radeon.audio=0"
initrd /boot/sysrcd/isolinux/initram.igz
All works fine exept that the menu entry say "Boot ArchLinux from 65 Gib FAT volume" and I want to have a menu entry that simply say "Archlinux". Is that possible? By the way Archlinux is on a ext4 volume, not FAT (refind has the driver to read it). Note that everything works fine except that cosmetic problem.
Last edited by olive (2015-02-27 16:54:20)

Similar Messages

Arch Linux OS X Boot Menu Label

Hi guys,
I am pretty new to Linux. I just finished installing Arch Linux on my macbook pro. I followed the instructions on the wiki and now I'm able to boot into Arch Linux by selecting the "EFI Boot" option from the menu after holding down the alt key on startup. Everything is working pretty smoothly so far but I was wondering if its possible to change the label of the Arch Linux option in the menu from "EFI Boot" to "Arch Linux". On the manpage for bless it says the following:
--label name Render a text label used in the firmware-based OS picker
I tried using the following commands to bless the boot partition, but they have no effect on the label.
$ sudo bless --folder="Arch Linux" --file="Arch Linux/System/Library/CoreServices/boot.efi" --label=ArchLinux
$ sudo bless --mount="Arch Linux" --file="Arch Linux/System/Library/CoreServices/boot.efi" --label=ArchLinux
Anyone have any ideas?
Thanks,
Ahmed

heleos wrote:
This line:
Waiting for 30 seconds for device /dev/disk/by-label/ARCH-201005...
You need to make sure that's the exact name of your iso disc. If it's not, it isn't a big deal. I've run into problems on this with my arch USB drive.
Once you get to the [ramfs /]# prompt, type in:
mv /dev/disk/by-label/(insert name of the current cd here) /dev/disk/by-label/ARCH-201005
exit
It should then be able to boot from the cd
did:
mv /dev/disk/by-label/(insert name of the current cd here) /dev/disk/by-label/ARCH-201005
exit
shows:
ERROR: mounting was successful, but /bootmnt/isomounts file doex not exist.
Then I checked:
cd /bootmnt
ls
archlinux-2010.05-core-i686.iso
exit
shows another problem /boot/init does not exist
exit
kernel panic!

EFI/refind boot- how to get kernel vmlinuz in /boot/efi/EFI/arch?

I have a MacBook Pro Retina (10,2) running arch. It EFI boots using rEFInd, booting from /boot/efi/EFI/arch. This problem has been happening since I first installed the system in July - when I use pacman to update to the latest kernel, the mkinitcpio hooks generate for the current kernel, not the one that was just installed. If I don't manually run mkinitcpio after the update, I'm left with an unbootable system (the ususal "Unable to find root device" error, and dumped to recovery shell) because of a kernel/initrd mismatch (I think).
So I think the problem isn't mkinitcpio, but rather that the "linux" package is installing the kernel at /boot/vmlinuz-linux (which I later manually copy to /boot/efi/EFI/arch/vmlinuz-linux), but mkinitcpio is looking in the correct path (/boot/efi/EFI/arch) for the kernel... which is the last kernel, since I haven't copied it there yet.
As an example (yeah, I know I went a LONG time between updates, mainly due to nvidia issues), yesterday I did a full update that bumped me from 3.9.8-1 to 3.10.10-1. But here's the mkinitcpio output during the pacman run:
upgrading linux...
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/efi/EFI/arch/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/efi/EFI/arch/initramfs-linux.img
==> Starting build: 3.9.8-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
==> ERROR: module not found: `usbhid'
-> Running build hook: [fsck]
-> Running build hook: [resume]
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Creating gzip initcpio image: /boot/efi/EFI/arch/initramfs-linux.img
==> WARNING: errors were encountered during the build. The image may not be complete.
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/efi/EFI/arch/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/efi/EFI/arch/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.9.8-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
==> ERROR: module not found: `usbhid'
-> Running build hook: [fsck]
-> Running build hook: [resume]
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Creating gzip initcpio image: /boot/efi/EFI/arch/initramfs-linux-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly
Is there any solution to this problem? Because of the nature of rEFInd, I can't (don't think I can? I remember trying it and having problems) just symlink /boot/efi/EFI/arch/vmlinuz-linux to /boot/vmlinuz-linux.
Any ideas/help would be greatly appreciated.
Here's the uncommented lines in /etc/mkinitcpio.conf:
MODULES=""
BINARIES=""
FILES=""
HOOKS="base udev autodetect modconf block filesystems keyboard fsck resume"
And from /etc/mkinitcpio.d/linux.preset, which I manually specify on the command line (-p linux) when I re-run mkinitcpio after copying vmlinuz into place:
ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/efi/EFI/arch/vmlinuz-linux"
PRESETS=('default' 'fallback')
default_image="/boot/efi/EFI/arch/initramfs-linux.img"
fallback_image="/boot/efi/EFI/arch/initramfs-linux-fallback.img"
fallback_options="-S autodetect"
Is the right solution just changing ALL_kver to /boot/vmlinuz-linux and then copying that into /boot/efi/EFI/arch after the install, or is there some nicer solution so that this can actually be an automatic process?
Thanks for any advice/tips/suggestions.
PS - I'm running arch on the Retina with KDE. All of my configuration after the initial working install is handled by Puppet, and the module I use (along with the initial instructions and a list of what is and isn't working so far) is available at https://github.com/jantman/puppet-archl … bookretina

Thanks, Rod! I agree, a simple mount -L esp /boot configuration is definitely ideal for a single installation system. That was what I first tried when I first installed my UEFI board. But I keep multiple installations on disk, and multiple configs per install, so I would often run into issues with installations interfering with one another's /boot files.
I also tried unique file names per installation - like prepending installation identifiers to filenames - but that required changing defaults at install, /boot monitor scripts and services and of course I would occasionally forget to implement it for an installation and be right back at square one. It was a headache.
Eventually I settled on the solution I described above because it was simply implemented, portable without modification, provided me a sane /boot tree, seemed to play nicely with default options across the board, and, well, because it was the best I could come up with. I figured that UEFI had already imposed the mandatory FAT32 partition on me so I might as well use it for all it was worth. I mean, even Windows fits in right along with the rest. This way I could interface with UEFI and linux bootloaders in the pre-UEFI customary way with simple configuration edits in /etc/fstab and in /boot, thanks mostly, of course, to rEFInd and what I learned reading rodsbooks.
I realize that I'm probably in violation of the GNU filesystem standard with the root-level /esp mount, but, to me, it seemed the intuitive place to put it. And frankly, I really don't know any better. Perhaps it belongs in /var/run or something? I'm fully confident GNU will have resolved a standard mount point for it once and for all sometime in the next decade or so.
Still, as you say, esp as /boot is ideal. Creshal very elegantly described it on the UEFI Bootloaders wiki Talk page like this:
efibootmgr -c -l /vmlinuz-linux -u "$(cat /proc/cmdline)"
Super simple, assuming an esp at /dev/sda1. He doesn't mention the necessary /boot entry in /etc/fstab or the various possible issues with efibootmgr/UEFI NVRAM though, which is of course perfectly acceptable in Talk. Still, I mentioned these things in reply to him there and described my solution like this:
$ mkdir -p /esp; mount -L {,/}esp
$ mkdir -p /esp/EFI/boot/<NEW_SYSTEM>/; mv /boot/* $_; mount --bind $_ /boot
$ cat <<'EOF' >/etc/fstab
LABEL=<NEW_ROOTFS> / <FSTYPE> defaults 0 0
LABEL=esp /esp vfat defaults 0 0
/esp/EFI/boot/<NEW_SYSTEM> /boot none defaults,bind 0 0
EOF
$ sed -ri 's/root=[^ ]*/root=LABEL=<NEW_ROOTFS>/g' /boot/refind_linux.conf
Probably that code works, though it's entirely possible I've stumbled on syntax somewhere as I haven't tested it as written. It is admittedly less elegant than Creshal's proffered solution, but it includes an operable /etc/fstab, skeleton that it is, and edits your refind_linux.conf to boot. Assuming gpt partition labels and a rEFInd install it should do the job with very few required modifications if any aside from replacing the <VAR> strings and adding /etc/fstab entries as appropriate.
I am troubled, though, by the possible incompatibilities you mention with a vfat filesystem mounted at /boot and default symlinking behavior there. Which distributions behave this way? I don't think I've encountered it, though my default install is arch so I suppose it's possible I've just overlooked it.
I ask mainly because I've also added this to the wiki as a Sync EFIStub Kernel option and would like to highlight any inherent incompatibilities there or remove it if necessary, especially considering that I've already so boldly stated: "The following method should work similarly with any distribution or any combination thereof." Guess I jumped the gun on that one, huh?
Anyway, thanks again for rEFInd and your considerable work on rodsbooks.
-Mike
Last edited by mikeserv (2013-09-30 23:04:51)

[SOLVED] Using Apple's UEFI boot menu with Arch

Hello,
I've successfully installed arch on my mid-2012 (5,1) 11" Macbook Air, and now I'm trying to get an entry in apple's boot menu (the one that shows when you hold 'option' when starting the computer). From the author of rEFInd's install instructions (http://www.rodsbooks.com/refind/installing.html#osx) it sounds like I can just add some files to `/dev/sda1` (a vfat directory that contains the stuff needed to boot macos), and then run apple's `bless` command and we're good to go. Unfortunately I've tried this a bunch of different ways, to no avail. I think some of my failure is simply because of a misunderstanding of UEFI, here are some questions I (partially) don't understand and my current understanding of them:
1. Do I even need a bootloader on a pure GPT/UEFI system? It seems like the answer is no, and I can just use the UEFI firmware and the linux kernel to load Arch (per: https://wiki.archlinux.org/index.php/UE … ux_Kernel). Note: I'd like to have as little software between the firmware and the os, for speed and simplicity. However, I'd still like to dual boot, but it sounds like the firmware can handle showing me a menu as long as there are entries pointing to parts of each OS.
2. Will grub/rEFInd/syslinux do some of the work for me initially/on a kernel update? I think the answer is yes, which would be motivation (esp when I need to update the kernel) to just use a multibootloader and have it handle arch and the firmware pass control to either that or MacOS
3. Will `efibootmgr` brick my mac? https://wiki.archlinux.org/index.php/UE … FI_systems says it will, but I think the `grub-install` command uses `efibootmgr`, so should I not try grub on here (this package: https://www.archlinux.org/packages/core … fi-x86_64/ ). Also some of the other packages (like rEFInd-efi) depend on efibootmgr, so does that mean any kind of an install from them (a command from the package, not the `pacman -S pkg` command) will also brick my system? (see rEFInd-efi dependencies: https://www.archlinux.org/packages/extr … efind-efi/ )
I've been searching a bunch of different things, output of the `bless` commands I've been running, and have found the following:
* https://bbs.archlinux.org/viewtopic.php?id=148647
* Using OSX to install rEFInd manually (moving the files around and using OSXs `bless` command) http://www.rodsbooks.com/refind/installing.html#osx , I used the rEFInd files from Archs repos: https://www.archlinux.org/packages/extr … efind-efi/ )
* The Wiki docs on rEFInd https://wiki.archlinux.org/index.php/UE … ing_rEFInd
To summarize, I'm trying to set up a dual boot between MacOS (installed) and Arch (also installed, there's just no way to boot it on my system yet) using Apple's built in menu that deals with the EFI partition on /dev/sda1 . Thanks in advance for any help!
end
Last edited by enduser (2013-03-18 12:00:17)

enduser wrote:I've successfully installed arch on my mid-2012 (5,1) 11" Macbook Air, and now I'm trying to get an entry in apple's boot menu (the one that shows when you hold 'option' when starting the computer). From the author of rEFInd's install instructions (http://www.rodsbooks.com/refind/installing.html#osx) it sounds like I can just add some files to `/dev/sda1` (a vfat directory that contains the stuff needed to boot macos), and then run apple's `bless` command and we're good to go.
Not quite. That makes a boot loader bootable, but it doesn't add an entry to Apple's boot manager menu. There's a blog post somewhere by Matthew Garrett that describes the steps necessary to add something to Apple's boot manager, but I couldn't find it in a quick Web search. Maybe you'll have better luck, or be able to track down the same information somewhere else. As I recall, it involves using a separate HFS+ volume, creating two or three dummy files, and using "bless" in OS X.
1. Do I even need a bootloader on a pure GPT/UEFI system?
Yes, you do need a boot loader. It's important to distinguish between a boot loader and a boot manager, though. The former is a program that loads a kernel, and perhaps associated data, into memory and transfers control to the kernel. A boot manager presents a user interface that enables you to select which OS (or which boot loader) to launch. A boot manager is not strictly necessary, and Apple's EFI implementation includes its own simple boot manager, which is what you've been unsuccessful in configuring.
Note: I'd like to have as little software between the firmware and the os, for speed and simplicity. However, I'd still like to dual boot, but it sounds like the firmware can handle showing me a menu as long as there are entries pointing to parts of each OS.
Many people make do with the firmware's own boot manager, but this can be rather inflexible. I'm not even sure if Apple's boot manager can handle passing options to Linux kernels' EFI stub loaders. This ability is not absolutely required, but without it you must compile your options into your kernel at compile time, which greatly reduces flexibility since you can't modify the options on a per-boot basis -- say, to boot into single-user mode if this is required.
2. Will grub/rEFInd/syslinux do some of the work for me initially/on a kernel update?
The usual Arch Linux method of handling kernel updates is to overwrite an old kernel with a new one, so no boot loader/boot manager changes are required. If you want to keep numbered kernels around (as most other distributions do), GRUB provides scripts that can help automate changes, but they are required in the grub.cfg file. rEFInd can auto-detect boot loaders, and if you're using the EFI stub loader, that means that the kernel is its own boot loader, and with a proper configuration, rEFInd can detect new kernels without changing its configuration file.
SYSLINUX has some very early and very experimental EFI support. The one and only time I tried it (about a month ago), it wouldn't compile for me. (I don't know of a precompiled binary available on the Web -- the support is that new!) I don't recommend trying it unless somebody who's gotten it to work offers to help you personally.
3. Will `efibootmgr` brick my mac? https://wiki.archlinux.org/index.php/UE … FI_systems says it will, but I think the `grub-install` command uses `efibootmgr`, so should I not try grub on here (this package: https://www.archlinux.org/packages/core … fi-x86_64/ ).
There were reports of efibootmgr damaging Mac firmware several months ago (I believe over a year ago). Since then I've seen claims that this problem has been fixed with recent kernels (3.0 and later, IIRC), but I've seen no substantiation one way or the other. Overall, I recommend caution....
Also some of the other packages (like rEFInd-efi) depend on efibootmgr, so does that mean any kind of an install from them (a command from the package, not the `pacman -S pkg` command) will also brick my system? (see rEFInd-efi dependencies: https://www.archlinux.org/packages/extr … efind-efi/ )
On a Mac, I recommend installing rEFInd (or any other EFI boot loader) from OS X rather than from Linux. (Note that I'm rEFInd's maintainer, so that's an official recommendation from the software's developer.) Offhand, I don't know if the Arch package for rEFInd runs efibootmgr automatically on boot or just has it as a dependency because efibootmgr is the usual way to register a boot loader on UEFI systems. If the latter, it should be safe to install the Arch package for rEFInd, copy its files, and then reboot to OS X to run bless on it. It would be just as easy, if not easier, to install it completely from OS X, though.

No recovery option in boot menu

Howdy.
I'm working on a Toshiba Satellite u845w-s400. The hard drive crapped out on me recently, so I replaced it with an SSD. Unfortunately, the factory installed tiny SSD with the recovery drive doesn't present an option to do any sort of repair or recovery when I try the "0" key or "F8" key for the boot menu when I restart my computer.
I can see the recovery partition in both linux or when I run a windows 7 installation from USB, but I can't access it. I'm currently seeing if fiddliong with some master boot file tools can fix the issue.
I tried installing the OS from a Windows 7 Professional USB image I used for my computer and hoped to pair it with the OEM label on the bottom of the computer, but no dice thus far. I sure as hell am not willing to pay Toshiba for a disk that can handle a simpler installation than plenty of complex builds and installs I've done over the last 20 years.
I also can't seem to find the right driver for the wi-fi on the computer, despite trying three different ones listed on the Toshiba support page and attempting to install via USB drive. They seem to extract the files, then do nothing else. Windows doesn't recognize them as relevant driver files when I try to manually update.
Am I overlooking some weird trick for either getting the recovery partition to be accessible or do I need some wireless driver that's not on the toshiba website?
Thanks

Your support site, including drivers, is here
I could be wrong but I don't think the recovery partition is on that 32GB mSATA ssd. I believe the hidden recovery partition is on your HDD. If the HDD is kaput, then you no longer have access to the recovery partition. Unless you made a set of recovery media while things were still working, then you'll have to order a set from Toshiba. Did you happen to create a backup image(s) of your system while it was still working. This is the best way to preserve your system in case of HDD failure.
L305-S5955, T9300 Intel Core 2 Duo, 4GB RAM, 60GB SSD, Win 7 Ultimate 64-bit

[SOLVED]rEFInd booting hangs

Hi all.
I have installed Arch, but when i boot, rEFInd hangs. I get to menu and select the right Arch menu point, but then it gets the screen where it hangs.
It says:
rEFInd - Booting OS
Starting vmlinuz-arch.efi
Using load options 'vmlinuz-arch.efi initrd=EFI\arch\initramfs-arch-fallback.img
Maybe it is getting the wrong initrd?
I'm running on UEFI on a Lenovo L430
Thanks
\\Batnas
Last edited by batnas (2012-10-21 10:52:30)

Sorry about the missing info, I'll try again.
I installed Arch following the Beginners Guide step by step.
Pretty much the only thing I've changed is the partitioning; it is done as following:
/dev/sda1 - 512MB - FAT32 - This is my UEFISYS partition
sda2 - 128MB - Ext4 - Boot
sda3 - 32GB - Btrfs - / (root)
sda4 - 16GB - Btrfs - /var
sda5 - ~70GB - Btrfs - /home
I do not have a swap partition, but I can't imagine how that could affect the boot-process.
All this is on a 128GB SSD
When I boot, I get a menu similar to this, but with only an Arch-entry:
When I select the Arch-entry, I get to the screen described above. I can post an image with the screen, but It has no more information than what I've written before.
The refind_linux.conf:
"Boot to defaults" "root=/dev/sda3 rootfstype=btrfs ro systemd.unit=graphical.target"
"Boot to terminal" "root=/dev/sda3 rootfstype=btrfs ro systemd.unit=multi-user.target"
If there is anything else you need to know, please ask.
Thanks
\\Batnas
Last edited by batnas (2012-10-20 21:31:58)

How do I add mutiple horizontal submenus to one menu label.

For Muse, how do I add mutiple horizontal submenus to one menu label. In other words, I have Interior,Graphic and Web as one menu. Under Interior I want a horizontal submenu with Kitchens, bathrooms, closets,etc. Then under Kitchens I may want Bars, Islands and pantries.. Windows 7.

In plan view drag all of the pages you want in a submenu under the page you have set for the top level menu. So in your situation you would want kitchens, bathrooms, clostets etc under the interior page in plan view.

Yoga 3 Pro - Accessing BIOS, boot menu and System Recovery

The following tutorial will explain the following topics
How to access the BIOS Setup
Choosing a boot menu
Start a system recovery
It is not the idea to explain every single option of the above, since many of them are complex and it would be too extensive for such a tutorial like this.
To execute any of the tasks above you need to press the button marked with the red arrow in the picture below:
Press the button when the Y3P is off! Use a small pointing device, I use the tablet pen of one of my Thinkpad tablets
Once you press the button you will be presented with the following screen:
Use the cursor keys to move up and down, press Enter to choose an option.
1) BIOS Setup
The BIOS is where you can get technical information about your device, as well to change boot parameters and setting up security passwords. Be very careful when changing certain values, since it can affect the way the Y3P works and/or affect performance and security settings.
Information Screen
It gives the hardware details of the Y3P, like CPU, installed RAM, SSD capacity and so on. This is a display only screen, no settings can be changed here:
Configuration Screen
Time and date can be changed in this screen. Furthermore to deactivate the Wireless LAN and enable the Intel Virtual Technology. If you plan to use Virtual Machine software in your Y3P this setting must be enabled
Passwords can be set up in this section. Secure Boot settings can be changed here.
Primarily designed to protect users from rootkits and other malware attacks by blocking unauthorized executables and drivers from being loaded during the boot process, it must be deactivated if you plan to install Linux or having paralel operating systems
Boot Screen
Boot modes can be selected in this screen, you can disable booting from a USB stick or from a network for example
2) Boot Menu
This option is useful if you have Linux installed (using managers like LILO, GRUB, etc).
If you only use Win8 or higher there 's no much you can change.
3) System Recovery
This option will allow you to restore the system to either its factory setup, or to a previous backup done within Windows
A factory set up will leave the Y3P as it was shipped from Lenovo your private data and installed apps and/or programs will be wiped out. So make sure you have an external backup before such a reset

OK article. Doesn't answer my questions.

[Forum FAQ]How to customize Windows 7 & Windows 8.1 dual boot menu

Scenario 1:
When you install Windows 8.1 on Windows 7 based computer, the default boot option is Windows 8.1 boot options menu which is shown as Figure 1:
If you want to use the old Windows 7 boot menu, follow these steps:
Start the computer and then go into
Windows 8.1 boot options menu which is shown as Figure 1.
Click
Change defaults or choose other options, and Options menu appears which is shown as Figure 2.
Click
Choose a default operation system option.
Click
Windows 7 Enterprise option to set Windows 7 as the default operating system in the Choose a default operating system menu which is shown as Figure 3.
Restart, and it will be changed to
Windows 7 boot options menu which is as shown as Figure
Scenario 2:
If you have Windows 7 and Windows 8.1 dual-boot configuration, and the default boot menu is Windows 7 boot options menu which is shown as Figure 4.
If you want to get the GUI as Windows 8.1 style, follow these steps:
Boot into Windows 8.1 computer, open the
command Prompt (Admin).
Type the following command
bcdboot c:\Windows and press Enter.
Restart, and you'll see the Windows 8.1 boot options menu which is as shown Figure 1.
Scenario 3:
When you have dual-boot system, one of the system disappear from the boot menu. We could follow these steps to get it back:
Boot the computer from the installation media (Here my example is Windows 7) that works fine system.
Go into
System Recovery Options menu, which is as shown as Figure 6.
Click
Command Prompt link to open the command prompt window
Use the
diskpart and list volume commands to confirm the OS boot drive, the commands are shown as Figure 7.
Backup the bcd file, rename it.
Rebuild a new bcd file. It will scan all disk to confirm all Windows installation on your computer and ask if you want to add them to boot list.
Type
Y to agree with adding to boot list. In next boot, you will get all boot options back in the boot menu.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Since you've selected as default OS as Windows 8.1 you can go to disk management console and format the drive as required.
You can remove the Win 7 entry from boot loader:
To launch msconfig:
Click Start
In the Search text box, type msconfig
Launch msconfig by selecting it from the search results above the search text box.
After msconfig is launched:
Go to the Boot tab
Slect the boot entry you want to delete.
Click the Delete button and then click OK.
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Lenovo G580 boot menu is not working when pressing F2 and F12 key

QuestionI bought a new Lenovo G580 series laptop. After installation of Windows 7 Ultimate x64 bit edition, a problem revealed when Lenovo driver get installed.
When I installed Intel HD 3000 graphics driver and restarted laptop, the Window was unable to start normally. It displayed an error, so a recovery program started which was recommended. But this program failed to resolve the problem. Later, I tried again to load Windows normally but the blue screen fatal error showed up.
I attempted to reinstall Windows again, but after restarting window, the boot menu was not showing up after pressing F12 key. F2 key was also not working either.
I spoke to a Lenovo techincal assistance expert and they suggested me to remove battery and charger and press start key for 30 seconds.
My problem still remains the same, and I am unable to access boot menu.
The bios version is 62cn34ww. ls there a way I can get this running again?
AnswerPlease take note that the suggestion below is just a troubleshooting guide. If the steps could not fix the issue, you need to send you machine in for service for further assistance.
Try removing the hard disk , then press F2 button to enter BIOS
If you are successful in entering the bios, pleaes load set up defaults
Save setting by pressing F10 and shut the machine down
Connect the hard drive back and check if can enter BIOS via F2 and F12 to see boot menu

"OK, I will retain my sanity.... changed & of course forgot windows 7 password on my Lenovo H430 desktop. (about a month ago) came accross my windows disc & was going to see if I could boot from it (wouldn't from the pasword unlocker i downloaded) Anyhow, i evidently have a password to enter bois setup which i attempted to "guess" baaad idea. i am now looking at Fatal Error.....System halted on my Lenovo H430 desktop. how do i proceed without doing any damage??? HELP...

Windows 8.1 flex 14-2 boot menu direct to windows no usb or bios setting start up

Windows 8.1 > yesterday suddenly to make a selection from more boot menu ; ( Fn - F12) He takes no bios setup or a USB boot stick more but starts right after selection windows again? These have put a lenovo flex 2-14 with a self built-in SSD 250 840EVO disk where I am in the bios Boot UEFI mode to Lagacy support. Via de novo button I can still get into the bios and change the settings here ; Boot menu ; legacy support boat priority ; legacy first USB boot ; enabled All updates are automatically done so I suspect something has changed what is causing this problem?

Latest Bios installed.
Bios Priority; usb stick firts, SSD drive last.
Still direct from boot menu to windows

Laptop won't load OS, won't enter BIOS/Boot Menu.

I recently installed Windows 7 Professional on my Compaq CQ56 PC, on a 260Gig HHD partition. I then installed Opensuse linux on the remainind 60Gig. However half way through installation my PC ran out of power and dhut down. I tried booting and changing the Boot Device menu, so that I complete installation, but it won't allow me to go into the boot menu (simply stops on the compaq start screen - fan and cd-rom will be working.) Is there a way for me to rectify this without losing my data?

It sounds as if you were never warned to always do an OS installation or anything that has to do with partitioning while on external power.
Please identify your notebook with more than just the model type. You have given an incomplete picture of your hardware configuration while reporting an extreme hardware/firmware issue. IT would help to remove the battery and take a look at the service tag. Please post the p/n (product number) here in your thread
There are a few things to try.
Remove the hard disk. Connect the power adapter and press the power button. Does the BIOS screen appear and warn that it can not find a bootable disk?
If it does not, then try a hard reset.
Try a hard reset as follows:
1) Remove the battery and unplug the DC power adapter.
2) Press and hold the power button for more than fifteen seconds.
3) Plug in the DC power adapter (leave the battery out for now)
4) Press the power button
Please post your positive or negative results here in your thread.
You can put the hard disk in an external housing and connect it to another PC to try torecover your data. What you will see will depend on the operating system of the PC that you use for data recovery.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Can't remove PC-DOS from Windows 7 Boot menu after using PC-Doctor for DOS Bootable CD

I have a T60, Win 7 Pro
I had some issues and tried the PC-Doctor for Dos bootable CD to run some diagnostics. Since then, upon bootup, I have a PC-DOS option in my boot menu that just won't go away.
Using EasyBSD, the only os supposed to be in the bootloader menu is Win 7, yet, everytime I boot up, I get the boot menu.
I even tried using bcdedit to sstop displaying the boot menu but it still appears (for a split second).
Looking for some help in steps to remove the PC-DOS option from my windows 7 boot menu.

Hi,
I have tried something like that with ZenWalk (Slackware- based distro) and it worked for me on my Lenovo b305 with ATI 5450, no problems like that. Not sure about how Ubuntu will deal with these AIO systems. But I have a feeling that it is not your HD or booting, sounds like a video problem. ATI and Linux don't get on well.
Can you see the console y Alt +F1? perhaps you have to reconfigure Xorg manually.
My advice is to ask in Ubuntu forums they might have better ideas. ATI 5??? line is still "new" for Linux and the open drivers need time to work properly.
Also keep in mind IdeaCentre was not build for Linux...Issues like this might happen also post install.
Hope this helps,
Sergio

Windows 7 hangs from boot menu

Hi,
my Windows 7 partition refuses to start from boot menu, system just hangs and does nothing. I've not made any changes to the disk layout, only thing I can think of is the upgrade to 10.9.4 which probably changed the recovery partition.
History:
- iMac Mavericks 10.9.3 with boot camp 5.1.2 and Windows 7, used to start into Windows by pressing Alt on start up, then reboot from Windows menu or from Windows boot camp application into OS X and back without problems
- installed the 10.9.4 Build 13E28 upgrade some days ago
- Change today: rebooted from the boot camp system tray app into OS X, worked without a problem
- reboot from OS X into boot menu, select Windows 7 partition, system hangs
I've found this thread, describing a similar problem Repairing Boot Camp after creating new partition I think, however since my Index output only lists 4 partitions I think my problem might be a bit different.
Here's the output from: sudo gpt -r -vv show disk0
gpt show: disk0: mediasize=500107862016; sectorsize=512; blocks=976773168
gpt show: disk0: Suspicious MBR at sector 0
gpt show: disk0: Pri GPT at sector 1
gpt show: disk0: Sec GPT at sector 976773167
      start       size index contents
          0          1         MBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6
         40     409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640 816890832      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
817300472    1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
818570008       1256
818571264 158201856      4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
976773120         15
976773135         32         Sec GPT table
976773167          1         Sec GPT header
and this one is from: sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 60801/255/63 [976773168 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 -     409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [    409640 - 816890832] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 817300472 -    1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 818571264 - 158201856] HPFS/QNX/AUX
and, just in case: diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Calimera                418.2 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data Windows 7               81.0 GB    disk0s4
I guess something mixed up the MBR since I would have expected line 4 of the fdisk output to show something 'Windows' like instead of HPFS/QNX/AUX, but even if that is correct, the question is how can the boot problem be fixed?
The Windows partition is accessible from OS X, so copying the data is not a problem if everything else fails. As far as I remember, the boot camp version in windows is 3.3 (it's an older iMac model).
GDisk is available, command line not a problem, if you need any further info let me know, any help appreciated.
thanks,
jk

Hi,
> Does the Bootcamp partition show up in Finder and can you see files in it?
Yes, the partition shows up in Finder and I can see and copy files.
> In Disk Utility, does the Bootcamp partition report as NTFS?
Yes it does, "Get Info" from Finder also reports it as a NTFS volume.
> Do you have any third party NTFS drivers?
Yes I have, Paragon NTFS tools.
> If you hold the ALT key can you boot into Windows?
No, system just hangs and needs to be rebooted via power-off.
> If you came from 10.9.3 to 10.9.4, the Recovery HD should have existed under 10.9.3.
Yes it did, I did a clean install from USB media when Mavericks came out, the Recovery HD is also visible - and has been - in the boot menu.
> The one strange part is that your volume says "Windows 7". Were any diskutil commands run to change volume names?
No, just a left click on the Volume Name in Finder and then change Bootcamp to Windows 7.
Output of dd:
00000000 eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS    .....|
00000010 00 00 00 00 00 f8 00 00 3f 00 ff 00 00 68 ca 30 |........?....h.0|
00000020 00 00 00 00 80 00 80 00 ff f7 6d 09 00 00 00 00 |..........m.....|
00000030 00 00 0c 00 00 00 00 00 02 00 00 00 00 00 00 00 |................|
00000040 f6 00 00 00 01 00 00 00 d7 f9 07 a2 27 08 a2 26 |............'..&|
00000050 16 1d 72 73 fa 33 c0 8e d0 bc 00 7c fb 68 c0 07 |..rs.3.....|.h..|
00000060 1f 1e 68 66 00 cb 88 16 0e 00 66 81 3e 03 00 4e |..hf......f.>..N|
00000070 54 46 53 75 15 b4 41 bb aa 55 cd 13 72 0c 81 fb |TFSu..A..U..r...|
00000080 55 aa 75 06 f7 c1 01 00 75 03 e9 dd 00 1e 83 ec |U.u.....u.......|
00000090 18 68 1a 00 b4 48 8a 16 0e 00 8b f4 16 1f cd 13 |.h...H..........|
000000a0 9f 83 c4 18 9e 58 1f 72 e1 3b 06 0b 00 75 db a3 |.....X.r.;...u..|
000000b0 0f 00 c1 2e 0f 00 04 1e 5a 33 db b9 00 20 2b c8 |........Z3... +.|
000000c0 66 ff 06 11 00 03 16 0f 00 8e c2 ff 06 16 00 e8 |f...............|
000000d0 4b 00 2b c8 77 ef b8 00 bb cd 1a 66 23 c0 75 2d |K.+.w......f#.u-|
000000e0 66 81 fb 54 43 50 41 75 24 81 f9 02 01 72 1e 16 |f..TCPAu$....r..|
000000f0 68 07 bb 16 68 70 0e 16 68 09 00 66 53 66 53 66 |h...hp..h..fSfSf|
00000100 55 16 16 16 68 b8 01 66 61 0e 07 cd 1a 33 c0 bf |U...h..fa....3..|
00000110 28 10 b9 d8 0f fc f3 aa e9 5f 01 90 90 66 60 1e |(........_...f`.|
00000120 06 66 a1 11 00 66 03 06 1c 00 1e 66 68 00 00 00 |.f...f.....fh...|
00000130 00 66 50 06 53 68 01 00 68 10 00 b4 42 8a 16 0e |.fP.Sh..h...B...|
00000140 00 16 1f 8b f4 cd 13 66 59 5b 5a 66 59 66 59 1f |.......fY[ZfYfY.|
00000150 0f 82 16 00 66 ff 06 11 00 03 16 0f 00 8e c2 ff |....f...........|
00000160 0e 16 00 75 bc 07 1f 66 61 c3 a0 f8 01 e8 09 00 |...u...fa.......|
00000170 a0 fb 01 e8 03 00 f4 eb fd b4 01 8b f0 ac 3c 00 |..............<.|
00000180 74 09 b4 0e bb 07 00 cd 10 eb f2 c3 0d 0a 41 20 |t.............A |
00000190 64 69 73 6b 20 72 65 61 64 20 65 72 72 6f 72 20 |disk read error |
000001a0 6f 63 63 75 72 72 65 64 00 0d 0a 42 4f 4f 54 4d |occurred...BOOTM|
000001b0 47 52 20 69 73 20 6d 69 73 73 69 6e 67 00 0d 0a |GR is missing...|
000001c0 42 4f 4f 54 4d 47 52 20 69 73 20 63 6f 6d 70 72 |BOOTMGR is compr|
000001d0 65 73 73 65 64 00 0d 0a 50 72 65 73 73 20 43 74 |essed...Press Ct|
000001e0 72 6c 2b 41 6c 74 2b 44 65 6c 20 74 6f 20 72 65 |rl+Alt+Del to re|
000001f0 73 74 61 72 74 0d 0a 00 8c a9 be d6 00 00 55 aa |start.........U.|
00000200
So, you think running the Windows startup repair will fix the problem? Is there something that I should be aware of in terms of interfering with the OS X partition?
jk

OS X Mavericks not showing up in boot menu?

Hi,
I recently applied to the OS X Yosemite Beta program and downloaded and installed the Beta. I have a 1TB Hard drive in my MacBook Pro which is was partitioned in two partitions, one for OS X Mavericks and one for Bootcamp. I decided I wanted to keep my original partitions intact so I installed the Yosemite beta onto an external hard drive so I wouldn't affect my main system. The Yosemite Beta installed and booted fine from the external hard drive but when I rebooted my computer I was presented with option to boot into my Bootcamp partition or an OS X Yosemite Installer. I can boot into Windows fine but not OS X Mavericks. The OS X Mavericks partition is still intact but does not show up during start up. I tried using a third-party bootloader like rEFIt but doesn't seem to work. Any help would be greatly appreciated.
Here is an image showing my boot menu, the items in orange are my external hard drive with the Yosemite Beta on it.

Thanks for the reply, I managed to solve my problem by forcibly unmounting the install partition and booting into Bootcamp (My only option). From there I selected my OS X Mavericks partition from the Bootcamp menu in Windows and I rebooted successfully into it. For some reason it still wont show up in the boot menu but rEFIt now works and will detect it along with the Bootcamp partition

Refind boot menu label

Similar Messages

Maybe you are looking for