I reported this problem some time ago but I still cannot boot my FC6 disk. I have been poking around the GRUB source and I now have a better understanding of what GRUB does but I don't understand this problem.
I have 2 disks, one is a SATA disk that has Windows XP on it. The other disk is an IDE that has my FC6 on it. When I try to boot to the FC6 disk, the machine just reboots over and over again. I then boot from the rescue disk and look at the partitions using fdisk. Everything looks normal. The Windows stuff is on /dev/sda and the FC6 stuff is on /dev/hdk. /boot/grub/device.map contains:
(hd0) /dev/sda (hd1) /dev/hdk
If I enter GRUB in interactive mode and do
# geometry (hd0,0)
I get the output I expect but when I do
# geometry (hd1,0)
GRUB tells me that there is no such disk. The reason GRUB won't boot is that is fails the root (hd1,0) command in the grub.conf file.
I even re-installed GRUB
# grub-install /dev/hdk
with no problems but when I go back inro GRUB it still tells me there is no hd1.
Can anyone give me somewhere else to look for clues? If GRUB looks at device.map to figure that hd1 means /dev/hdk and grub-install is OK installing on /dev/hdk, why doesn't GRUB recognize the 2nd disk?
Steve
zephod@cfl.rr.com wrote:
I reported this problem some time ago but I still cannot boot my FC6 disk. I have been poking around the GRUB source and I now have a better understanding of what GRUB does but I don't understand this problem.
I have 2 disks, one is a SATA disk that has Windows XP on it. The other disk is an IDE that has my FC6 on it. When I try to boot to the FC6 disk, the machine just reboots over and over again. I then boot from the rescue disk and look at the partitions using fdisk. Everything looks normal. The Windows stuff is on /dev/sda and the FC6 stuff is on /dev/hdk. /boot/grub/device.map contains:
(hd0) /dev/sda (hd1) /dev/hdk
If I enter GRUB in interactive mode and do
# geometry (hd0,0)
I get the output I expect but when I do
# geometry (hd1,0)
GRUB tells me that there is no such disk. The reason GRUB won't boot is that is fails the root (hd1,0) command in the grub.conf file.
I even re-installed GRUB
# grub-install /dev/hdk
with no problems but when I go back inro GRUB it still tells me there is no hd1.
Can anyone give me somewhere else to look for clues? If GRUB looks at device.map to figure that hd1 means /dev/hdk and grub-install is OK installing on /dev/hdk, why doesn't GRUB recognize the 2nd disk?
Steve
The problem with rebooting without a rational cause happened to me booting from a xen kernel. Are you booting from a xen enabled kernel? Chances are that this is not your problem but just in case it is your problem.
Regarding the no such disk problem. I had problems on two different Dell computers which the secondary drive was disabled in BIOS. Fedora itself recognized the disks but grub did not because of the BIOS setting. Are your BIOS settings set to show all disks?
Regarding Grub interactive. I had to use it myself today for the first time. It is highly cryptic but not too hard once you get through the vague documentation.
CAUTION: (I don't know what the heck I'm doing in the grub shell yet this is a question only) What would happen if you entered root (hd1,0) followed by setup (hd0)
Basically, boot is the first partition on the second hard drive and grub is booted from MBR.
I had to do this on a computer which I moved boot from sdb2 to sdb1 changed fstab reference and /boot/grub/grub.conf references but did not run grub-install before rebooting.
Why are you trying geometry?
Jim
----- Original Message ----- From: Jim Cornette fc-cornette@insight.rr.com Date: Tuesday, February 6, 2007 11:00 pm Subject: Re: Boot problems (still) To: For users of Fedora fedora-list@redhat.com
zephod@cfl.rr.com wrote:
I reported this problem some time ago but I still cannot boot my FC6 disk.
snip
Steve
The problem with rebooting without a rational cause happened to me booting from a xen kernel. Are you booting from a xen enabled kernel? Chances are that this is not your problem but just in case it is your problem.
The kernel that would be booted if I could get to that point is a xen kernel and this problem started after I installed a xen kernel but right now I can't even get to a GRUB menu and so there is no kernel involved yet.
Regarding the no such disk problem. I had problems on two different Dell computers which the secondary drive was disabled in BIOS. Fedora itself recognized the disks but grub did not because of the BIOS setting. Are your BIOS settings set to show all disks?
I am thinking that the BIOS is the problem because the IDE drive does not show up in the primary or secondary drive list but it does show up in the list of bootable devices. In addition, the BIOS has it's own menu that allows you to pick which device you want to boot from and the IDE drive does show up there.
Regarding Grub interactive. I had to use it myself today for the first time. It is highly cryptic but not too hard once you get through the vague documentation.
CAUTION: (I don't know what the heck I'm doing in the grub shell yet this is a question only) What would happen if you entered root (hd1,0) followed by setup (hd0)
Basically, boot is the first partition on the second hard drive and grub is booted from MBR.
The root(hd1,0) command fails because GRUB says there is no hd1.
I had to do this on a computer which I moved boot from sdb2 to sdb1 changed fstab reference and /boot/grub/grub.conf references but did not run grub-install before rebooting.
Why are you trying geometry?
Because geometry lists the device and the C/H/S information in its output so I can see that hd0 is /dev/sda and it is my 120G SATA drive and not my 160GB IDE drive.
Steve.
Jim
-- QOTD: "If he learns from his mistakes, pretty soon he'll know
everything."
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
zephod@cfl.rr.com wrote:
Why are you trying geometry?
Because geometry lists the device and the C/H/S information in its output so I can see that hd0 is /dev/sda and it is my 120G SATA drive and not my 160GB IDE drive.
Steve.
Thanks for the information. I did not know what the option was used for. I only used the grub shell a few times and the latest was because I did not have a rescue disc available. I had to guess and use pretty vague hits from google to get my system booting again.
Jim
On Tue, 2007-02-06 at 22:59 -0500, Jim Cornette wrote:
zephod@cfl.rr.com wrote:
I reported this problem some time ago but I still cannot boot my FC6 disk. I have been poking around the GRUB source and I now have a better understanding of what GRUB does but I don't understand this problem.
I have 2 disks, one is a SATA disk that has Windows XP on it. The other disk is an IDE that has my FC6 on it. When I try to boot to the FC6 disk, the machine just reboots over and over again. I then boot from the rescue disk and look at the partitions using fdisk. Everything looks normal. The Windows stuff is on /dev/sda and the FC6 stuff is on /dev/hdk. /boot/grub/device.map contains:
(hd0) /dev/sda (hd1) /dev/hdk
If I enter GRUB in interactive mode and do
# geometry (hd0,0)
I get the output I expect but when I do
# geometry (hd1,0)
GRUB tells me that there is no such disk. The reason GRUB won't boot is that is fails the root (hd1,0) command in the grub.conf file.
I even re-installed GRUB
# grub-install /dev/hdk
with no problems but when I go back inro GRUB it still tells me there is no hd1.
Can anyone give me somewhere else to look for clues? If GRUB looks at device.map to figure that hd1 means /dev/hdk and grub-install is OK installing on /dev/hdk, why doesn't GRUB recognize the 2nd disk?
Steve
The problem with rebooting without a rational cause happened to me booting from a xen kernel. Are you booting from a xen enabled kernel? Chances are that this is not your problem but just in case it is your problem.
Regarding the no such disk problem. I had problems on two different Dell computers which the secondary drive was disabled in BIOS. Fedora itself recognized the disks but grub did not because of the BIOS setting. Are your BIOS settings set to show all disks?
Regarding Grub interactive. I had to use it myself today for the first time. It is highly cryptic but not too hard once you get through the vague documentation.
CAUTION: (I don't know what the heck I'm doing in the grub shell yet this is a question only) What would happen if you entered root (hd1,0) followed by setup (hd0)
Basically, boot is the first partition on the second hard drive and grub is booted from MBR.
I had to do this on a computer which I moved boot from sdb2 to sdb1 changed fstab reference and /boot/grub/grub.conf references but did not run grub-install before rebooting.
Why are you trying geoometry
The above grub coammands shold work, and the boot block should be placed on /dev/sda. ======================================================================= Everyone wants results, but no one is willing to do what it takes to get them. -- Dirty Harry ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
zephod@cfl.rr.com wrote:
I reported this problem some time ago but I still cannot boot my FC6 disk. I have been poking around the GRUB source and I now have a better understanding of what GRUB does but I don't understand this problem.
I have 2 disks, one is a SATA disk that has Windows XP on it. The other disk is an IDE that has my FC6 on it. When I try to boot to the FC6 disk, the machine just reboots over and over again. I then boot from the rescue disk and look at the partitions using fdisk. Everything looks normal. The Windows stuff is on /dev/sda and the FC6 stuff is on /dev/hdk. /boot/grub/device.map contains:
(hd0) /dev/sda (hd1) /dev/hdk
If I enter GRUB in interactive mode and do
# geometry (hd0,0)
I get the output I expect but when I do
# geometry (hd1,0)
GRUB tells me that there is no such disk. The reason GRUB won't boot is that is fails the root (hd1,0) command in the grub.conf file.
I even re-installed GRUB
# grub-install /dev/hdk
with no problems but when I go back inro GRUB it still tells me there is no hd1.
Can anyone give me somewhere else to look for clues? If GRUB looks at device.map to figure that hd1 means /dev/hdk and grub-install is OK installing on /dev/hdk, why doesn't GRUB recognize the 2nd disk?
Steve
Dumb question - does your BIOS know about the IDE drive? If not, then chances are you will not be able to boot from it. You may have to make space for the /boot directory on the SATA drive.
If your BIOS does know about the IDE drive, running "grub-install --remap" may help. You may also want to try running "geometry (hd2,0)" and "geometry (hd3,0)" just in case the BIOS is skipping numbers when mapping drives.
With the drive being /dev/hdk, it sounds like the drive is on a controller card, and not off the motherboard... Is this the case?
Mikkel
----- Original Message ----- From: "Mikkel L. Ellertson" mikkel@infinity-ltd.com Date: Tuesday, February 6, 2007 11:28 pm Subject: Re: Boot problems (still) To: For users of Fedora fedora-list@redhat.com
zephod@cfl.rr.com wrote:
I reported this problem some time ago but I still cannot boot my
FC6
disk.
snip
Steve
Dumb question - does your BIOS know about the IDE drive? If not, then chances are you will not be able to boot from it. You may have to make space for the /boot directory on the SATA drive.
Not a dumb question at all and I think the answer is... maybe.
The IDE drive does not show up in the BIOS list of primary or secondary IDE devices but it does show up in the BIOS list of hard drives. Also, this BIOS (ASUS P5G2 Deluxe or something close to that) can present a menu of devices that you can boot from and the IDE drive shows up in that list. This is how I was booting this disk before with FC5. This used to work and when I upgraded to FC6 it appeared to work for a short while. The BIOS hasn't changed but GRUB went from 0.95 to 0.97 in the upgrade. I have been avoiding messing with the Windows dusk since that the only way for me to communicate at the moment.
If your BIOS does know about the IDE drive, running "grub-install --remap" may help. You may also want to try running "geometry (hd2,0)" and "geometry (hd3,0)" just in case the BIOS is skipping numbers when mapping drives.
I will try the --remap option. I have already tried hd numbers all the way up to 9 with no luck.
With the drive being /dev/hdk, it sounds like the drive is on a controller card, and not off the motherboard... Is this the case?
You are correct sir! Originally, I could not get the BIOS to see the IDE drive when I connected it to the motherboard so I plugged in an old IDE controller and hooked the drive up to that. This worked fine for ~1yr.
Steve
Mikkel
Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
zephod@cfl.rr.com wrote:
----- Original Message ----- From: "Mikkel L. Ellertson" mikkel@infinity-ltd.com Date: Tuesday, February 6, 2007 11:28 pm Subject: Re: Boot problems (still) To: For users of Fedora fedora-list@redhat.com
zephod@cfl.rr.com wrote:
I reported this problem some time ago but I still cannot boot my
FC6
disk.
snip
Steve
Dumb question - does your BIOS know about the IDE drive? If not, then chances are you will not be able to boot from it. You may have to make space for the /boot directory on the SATA drive.
Not a dumb question at all and I think the answer is... maybe.
The IDE drive does not show up in the BIOS list of primary or secondary IDE devices but it does show up in the BIOS list of hard drives. Also, this BIOS (ASUS P5G2 Deluxe or something close to that) can present a menu of devices that you can boot from and the IDE drive shows up in that list. This is how I was booting this disk before with FC5. This used to work and when I upgraded to FC6 it appeared to work for a short while. The BIOS hasn't changed but GRUB went from 0.95 to 0.97 in the upgrade. I have been avoiding messing with the Windows dusk since that the only way for me to communicate at the moment.
If your BIOS does know about the IDE drive, running "grub-install --remap" may help. You may also want to try running "geometry (hd2,0)" and "geometry (hd3,0)" just in case the BIOS is skipping numbers when mapping drives.
I will try the --remap option. I have already tried hd numbers all the way up to 9 with no luck.
This sounds like the BIOS may not be giving it a number, unless you boot from it. The fact that Grub does not see it tends to support this.
With the drive being /dev/hdk, it sounds like the drive is on a controller card, and not off the motherboard... Is this the case?
You are correct sir! Originally, I could not get the BIOS to see the IDE drive when I connected it to the motherboard so I plugged in an old IDE controller and hooked the drive up to that. This worked fine for ~1yr.
While it was working, were you telling the BIOS to boot from this drive? If so, then I think you should be telling Grub to use hd0, and not hd1. At least the BIOS's I have used map the drive that you boot from as the first hard drive. This was needed by older versions of Windows that had to boot from the first hard drive. This gets tricky because you do not get this change of mapping when you boot from the CD/DVD drive. So the map created when installing/upgrading from a CD/DVD is not the same as when you tell the BIOS to boot from the IDE drive instead of the SATA drive.
Now, if you are using the Windows XP boot loader to load Grub, then you will probably need to update the boot file you created from the boot record on the IDE drive to reflect the upgraded version of Grub. This is because the file locations on the drive for stage 2 (or stage 1.5) are hard coded into stage 1, and it is stage 1 that you copy to Windows. Chances are, the file locations changed in the upgrade. But part of the old files may still be there.
Mikkel
Mikkel,
I will try the --remap option. I have already tried hd numbers
all the
way up to 9 with no luck.
This sounds like the BIOS may not be giving it a number, unless you boot from it. The fact that Grub does not see it tends to support this.
I think you are onto something here. At lunch I went into the BIOS and changed the priority of the drives so that my IDE drive is now the first drive and the SATA drive is second. FC6 now boots. Yea!!
The strange thing is that I didn't change GRUB's device.map file which still says that hd0 is /dev/sda and hd1 is /dev/hdk, meanwhile my grub.conf file says to boot from hd0. (I had been experimenting with diffferent settings and I need to go back and correct all this now.) When I shut down FC6, it trashed my video memory (big horizontal dashes all over the screen) and I had to power off but when I restarted I used the BIOS menu to boot the Windows partition which worked just fine. I will experiment some more tonight.
With the drive being /dev/hdk, it sounds like the drive is on a controller card, and not off the motherboard... Is this the
case?
You are correct sir! Originally, I could not get the BIOS to see
the
IDE drive when I connected it to the motherboard so I plugged in
an
old IDE controller and hooked the drive up to that. This worked
fine
for ~1yr.
While it was working, were you telling the BIOS to boot from this drive? If so, then I think you should be telling Grub to use hd0, and not hd1. At least the BIOS's I have used map the drive that you boot from as the first hard drive. This was needed by older versions of Windows that had to boot from the first hard drive. This gets tricky because you do not get this change of mapping when you boot from the CD/DVD drive. So the map created when installing/upgrading from a CD/DVD is not the same as when you tell the BIOS to boot from the IDE drive instead of the SATA drive.
I don't remember but given the results I just got I think it must have been so.
So it would seem that if I use the BIOS menu to say which disk to boot from, the BIOS will always say that disk is disk 0 no matter what the BIOS disk priority order says and the BIOS does not give the second disk a number. That would explain things.
Eventually, I want to use Xen and make the Windows disk a virtual machine and I can just boot the one disk but I've got alot of reading to do before I get there.
Now, if you are using the Windows XP boot loader to load Grub, then you will probably need to update the boot file you created from the boot record on the IDE drive to reflect the upgraded version of Grub. This is because the file locations on the drive for stage 2 (or stage 1.5) are hard coded into stage 1, and it is stage 1 that you copy to Windows. Chances are, the file locations changed in the upgrade. But part of the old files may still be there.
Mikkel
No, I'm not using the Windows boot loader.
Thanks Steve.
On Wed, 7 Feb 2007, zephod@cfl.rr.com wrote:
Mikkel,
I will try the --remap option. I have already tried hd numbers
all the
way up to 9 with no luck.
This sounds like the BIOS may not be giving it a number, unless you boot from it. The fact that Grub does not see it tends to support this.
I think you are onto something here. At lunch I went into the BIOS and changed the priority of the drives so that my IDE drive is now the first drive and the SATA drive is second. FC6 now boots. Yea!!
The strange thing is that I didn't change GRUB's device.map file which still says that hd0 is /dev/sda and hd1 is /dev/hdk, meanwhile my grub.conf file says to boot from hd0. (I had been experimenting with diffferent settings and I need to go back and correct all this now.) When I shut down FC6, it trashed my video memory (big horizontal dashes all over the screen) and I had to power off but when I restarted I used the BIOS menu to boot the Windows partition which worked just fine. I will experiment some more tonight.
I have encountered this as well. Sometime between FC4 and FC6, how it paid attention to the BIOS settings changed. Looking at the settings, it should have never worked with FC4, but it did.
You wouldn't happen to have an Intel motherboard?
----- Original Message ----- From: alan alan@clueserver.org Date: Wednesday, February 7, 2007 3:51 pm Subject: Re: Boot problems (still) [SOLVED] To: For users of Fedora fedora-list@redhat.com
On Wed, 7 Feb 2007, zephod@cfl.rr.com wrote:
Mikkel,
I will try the --remap option. I have already tried hd numbers
all the
way up to 9 with no luck.
This sounds like the BIOS may not be giving it a number, unless
you
boot from it. The fact that Grub does not see it tends to support this.
I think you are onto something here. At lunch I went into the
BIOS and
changed the priority of the drives so that my IDE drive is now the first drive and the SATA drive is second. FC6 now boots. Yea!!
The strange thing is that I didn't change GRUB's device.map file
which> still says that hd0 is /dev/sda and hd1 is /dev/hdk, meanwhile my
grub.conf file says to boot from hd0. (I had been experimenting
with
diffferent settings and I need to go back and correct all this
now.)
When I shut down FC6, it trashed my video memory (big horizontal dashes all over the screen) and I had to power off but when I restarted I used the BIOS menu to boot the Windows partition which worked just fine. I will experiment some more tonight.
I have encountered this as well. Sometime between FC4 and FC6, how it paid attention to the BIOS settings changed. Looking at the settings, it should have never worked with FC4, but it did.
You wouldn't happen to have an Intel motherboard?
No, it's an ASUS P5G2 Delux.
Steve
-
Aaron Konstam -
Alan -
Jim Cornette -
Mikkel -
Steve Blackwell