You see the menu.lst points to
hd2,1
So at install Linux HD was 3rd
Try shifting it in the BIOS
and try booting again
Now that was something interesting!
I tried booting from all 3 HD…
(Order from BIOS boot menu)
Hitachi 900GB (DATA) => Windows
Maxtor 3S… 250Gb => BOOTMGR is mising, press CTRL-ALT-DEL to restart
Maxtor 4M… 250Gb => Windows
Are you saying
With the HDs’ in that order in the BIOS
You are not getting grub menu at boot?
Try running the grub install again to (hd0)
Find should see the menu now on (hd2.1)
@p_t_a may have some better advice based on the missing device map
I’m not seeing GRUB at all.
What do you mean by:
Find should see the menu now on (hd2.1)
?
According to findgrub output - which also displays Windows bootloaders - there is no Windows bootloader on this drive. The only one it found was in sda1.
Weird, I agree.
Maybe findgrub has some issues with Vista/Seven new bootloading software?
If you boot a Live CD or Parted Magic and open a terminal (su -)
>grub
>find /boot/grub/menu.lst
It should report it: (hd2,1)
Then you do
>root (hd2,1)
After the terminal reports the file system, you do
>setup (hd0)
Terminal should report:
>Checking if /boot/grub/stage1 exists … yes Computer finally returns this-- Succeeded…Done
Does the Live CD a chroot?
Where is actually /boot/grub?
Should the root partition not be mounted first?
According to the Web one has not to mount anything before doing all that. Every other time it worked just fine, no mounting no anything.
Find keeps telling me (hd1,1). And I suppose that if I was to give grub root(hd1,1) it would say that it is an ext partition.
(edit: I’m always using OpenSUSE net CD - Rescue system)
We don’t need to chroot at this point
Follow the guide I gave you earlier
http://forums.opensuse.org/new-user-how-faq-read-only/unreviewed-how-faq/429971-re-install-grub-quickly-parted-magic.html#post2097786
If you find /boot/grub/menu.lst on hd1
Then either you don’t have the Linux HD set 3rd in the BIOS
Or whatever you are using to do the find is seeing things wrongly
If you use Parted Magic is the partitioner seeing the Linux HD as sdc (hd2)?
I’m back from Parted Magic.
Linux FS are on sdb.
menu.lst is still found on (hd1,1)
Since it’s 9 pm here, I shall continue my fight against the PC to-morrow.
Linux FS are on sdb.
But you are sure it’s set as 3rd in BIOS?
@p_t_a
Hope he has advice
Sometimes the Mobo SATA connectors are important
Check your Mobo details
Until you get the Linux HD as sdc. You’ll not succeed.
At least that’s my conclusion.
why do you need this trouble in your life?
I have not the faintest idea whether it is 3rd or not.
(And having 2 hd from the same producer and with the same size does not help)
My what? Where?
Pray, do not say so!
I clearly remember that when I installed openSUSE it was on sdb. Why then I should try to make my computer change his mind?
Meaning?
I didn’t say we need one. But when you do find in a Grub shell on a live CD, where does it look and what does it find? The other commands will work, but I don’t think that find is reliable.
I just tried on a computer with plenty of Grubs … and that’s what it says:
From PartedMagic:
grub> find /boot/grub/menu.lst
(hd0,1,f)
(hd0,2,b)
(hd1,1,f)
(hd1,2,f)
None of (hd0,1), (hd0,2), (hd1,1) and (hd1,2) is a Linux partition, nor contains Grub. There are all BSD partitions. lol!
Back on topic, both, /boot/grub/menu.lst and findgrub -M refer to the second BIOS drive (hd1). However you’re loading the 3rd disk (hd2). That’s the problem here.
###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 12.1
** root (hd2,1)**
kernel /boot/vmlinuz-3.1.0-1.2-desktop **root=/dev/disk/by-path/pci-0000:00:11.0-scsi-1:0:0:0-part2 ** resume=/dev/disk/by-path/pci-0000:00:11.0-scsi-1:0:0:0-part1 splash=silent quiet showopts vga=0x31a
initrd /boot/initrd-3.1.0-1.2-desktop
--- DEVICE.MAP: sdb is ata drive hd1
--- DEVICE.MAP: - /dev/sdb
--- DEVICE.MAP: - /dev/disk/by-id/ata-MAXTOR_STM3250820AS_9QE2BXPD
--- DEVICE.MAP: - /dev/disk/by-id/scsi-SATA_MAXTOR_STM32508_9QE2BXPD
--- DEVICE.MAP: - **/dev/disk/by-path/pci-0000:00:11.0-scsi-1:0:0:0**
--- DEVICE.MAP: => sdb might be BIOS drive **hd1**
Ok, so, if I boot my live CD again and use the usual commands modified accordingly (how? Pray tell me) it might just work?
edit: no need to quote it all
@simosito,
Well … Either you did one of this:
- edited /boot/grub/menu.lst yourself for whatever reason and wrote root (hd2,1) there
- switched hard disk boot order in BIOS setup
- switched SATA ports
- boot with an external drive set as first boot device and reinstall Grub
Actually having 2 hard disks of the same size and of the same model is not as safe as it might sound. I already had a similar mess after a kernel update under openSUSE: it simply changed everything from (hd1) to (hd2) in menu.lst or vice-versa.
Or you did nothing and your mainboard is starting to confuse SATA ports and play crazy. I happens (actually too often with these cheap onboard SATA controllers).
Well, I hope that it did not get crazy after less than a month…
Probably I messed up big time after installing Windows.
So now what?
I don’t know which mainboard you have, but if it cost less than $200, it’s ****. Most people won’t notice because they don’t have more than 2 hard disks. With 3 hard disks, you start to enjoy the real power of your SATA controller.
Or it’s a coincidence. There is an unwritten rule with computers: 2 unrelated problems always occure at the same time.
IMO the best setup when you have Linux and Windows on separate hard disks is the one @jdmcdaniel3 has explained in several posts. He might correct me if I’m wrong because I’m not a Windows user.
on the mainboard:
- SATA1: Windows
- SATA2: Linux
- SATA3: data
in the BIOS (boot order):
- hd0: Linux
- hd1: Windows
- hd2: data
You install Grub in the MBR of hd0, which becomes the boot disk.
You boot Windows with this entry in menu.lst
rootnoverify (hd1,0)
map (hd1) (hd0)
map (hd0) (hd1)
chainloader +1
Mainboard’s ASUS.
Are you suggesting that I should open my PC and move HD around?