You are not logged in.
Hi. I had my previous Windows on sda1. My new Windows 7 is on sda7 and It was working until I removed this one from sda1. So, I changed my menu.lst. I changed "hd(0,0)" to "hd(0,6)" and the result is:
Error 12: Invalid device requestedI'm shure it is this number, so I don't know what is the problem. Here is my cfdisk:
cfdisk (util-linux 2.19.1)
Urządzenie: /dev/sda
Rozmiar: 250059350016 bajtów, 250.0 GB
Głowic: 255 Sektorów na ścieżce: 63 Cylindrów: 30401
Nazwa Flagi Typ partycjSystem plików [Etykieta] Rozmiar (M
B------------------------------------------------------------------------------
sda1 Rozruch Główna ntfs 25004,86
sda2 Rozruch Główna ext3 34998,57
sda5 Logiczna swap 2048,10
sda6 Logiczna ext3 158007,63
sda7 Rozruch, NK Logiczna ntfs 29996,88*
Gł/Log Wolne miejsce 3,34*(Rozruch == Boot, Główna == Master, Logiczna == Logical, NK == ???, Wolne miejsce == free space)
and menu.lst:
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst
# DEVICE NAME CONVERSIONS
#
# Linux Grub
# -------------------------
# /dev/fd0 (fd0)
# /dev/sda (hd0)
# /dev/sdb2 (hd1,1)
# /dev/sda3 (hd0,2)
#
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# for more details and different resolutions see
# http://wiki.archlinux.org/index.php/GRUB#Framebuffer_Resolution
# general configuration:
timeout 30
default 0
color light-blue/black light-cyan/blue
splashimage=(hd0,1)/boot/grub/arch-simplyblack-gts.xpm.gz
# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*
# (0) Arch Linux
title Arch Linux
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/sda2 ro vga=792 video=vesafb quiet console=tty1 splash=silent,theme:arch-black
initrd /boot/kernel26.img
# (1) Arch Linux Pro Audio
title Arch Linux Pro Audio
root (hd0,1)
kernel /boot/vmlinuz26rt root=/dev/sda2 ro vga=792 video=vesafb quiet console=tty1 splash=silent,theme:arch-black
initrd /boot/kernel26rt.img
# (2) Windows
title Windows
rootnoverify (hd0,6)
makeactive
chainloader +51What may cause the problem? And how may I solve it?
my home page and my blog
Offline
why +51?
maybe you have to count only existing partitions.
ezik
Offline
I had my previous Windows on sda1. My new Windows 7 is on sda7 and It was working until I removed this one from sda1.
That chainloader +51 thing probably is just a typo. But even chainloader +1 probably will not work now. I imagine the boot loader files for both Windows systems were in that primary partition. A Windows installer will never agree to putting boot loader files in a logical partition. You can mount those NTFS partitions and browse them for bootmgr and the /Boot folder. The partition with those is the one to target with chainloader. If you don't find those things, well...
Last edited by stoat (2011-09-25 20:25:09)
Offline
You cant have 2 partition with boot flag. Only 1 primary partition should have the boot flag and windows bootloader files (bootmgr and BCD) exist in that partition (formatted as ntfs).
When you installed Windows 7 in /dev/sda7, it installed its bootloader in /dev/sda1. But you formatted that partition. To correct this use bcdboot from Recovery console in Windows 7 ISO.
Also chainloader command should point to the partition where bootmgr is installed, not the partition which you selected when you installed Windows.
My new forum user/nick name is "the.ridikulus.rat" .
Offline