Ashley M. Kirchner wrote:
This was posted in a precious email. Yes.
*previous*
--
H| I haven't lost my mind; it's backed up on tape somewhere.
+
Ashley M. Kirchner mailto:[EMAIL PROTECTED] . 303.442.6410 x130
IT
On Mon, Aug 04, 2003 at 12:33:26PM -0600, Ashley M. Kirchner wrote:
Otto Haliburton wrote:
I have a dual boot system with HDA containing XP PRO and RH9 on HDB GRUB
is the boot loader and it is written to the MBR or HDA along with the XP
boot loader. I just removed HDB and guess what I got a
Jack Bowling wrote:
Hi, Ashley. Sorry to butt my head in so late. When you yanked the 2nd
drive, did you go into the BIOS and tell it that it no longer exists?
This was posted in a precious email. Yes.
--
H| I haven't lost my mind; it's backed up on tape somewhere.
Last time around. It appears that stage2 never gets called nor stage1_5
(I don't even see how it gets setup to call, but if it were called it
definitely prints a message GRUB is loading). Also it appears that
there is no error in stage1. So I don't believe that Ashley's problem
is with GRUB at
You haven't gotten the point of the question. GRUB is in the MBR from
the install. It has a location to get to the GRUB directory to load
stage1 (we know that stage1 and stage2 and all other things are in the
GRUB directory look them up yourself). So it locates the GRUB directory
to load
brian davison wrote:
with the additional info from Mr. Kirchner, that the board has scsi
interface on board, I wonder if it also has a self modifying portion in its
cmos... (I've seen a couple of these) where it keeps track of the scsi
devices and bootability.
Good theory, except I have
Otto, you may be missing this point..
Grub isn't loading anything.
Bios is loading the MBR from the drive.
this mbr.. part of grub is being called stage 1.
Yes, this is correct if you read the latter parts of the manual that I
published then you know that stage1 is 512 bytes long so
04, 2003 2:42 AM
To: [EMAIL PROTECTED]
Subject: RE: GRUB failure
Otto, you may be missing this point..
Grub isn't loading anything.
Bios is loading the MBR from the drive.
this mbr.. part of grub is being called stage 1.
Yes, this is correct if you read the latter parts
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ashley
M. Kirchner
Sent: Sunday, August 03, 2003 4:37 AM
To: [EMAIL PROTECTED]
Subject: Re: GRUB failure
brian davison wrote:
Ashley... try not changing the drive to single...
leave
it as the Master
exactly what has
changed. One can only guess otherwise.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Otto
Haliburton
Sent: Sunday, August 03, 2003 5:13 AM
To: [EMAIL PROTECTED]
Subject: RE: GRUB failure
Hi all,
We have all been
- set hda's jumper back to master otherwise BIOS
complains and won't
boot
- shoved floppy in, booted up just fine
- ran grub-install /dev/hda, no errors
- removed floppy, reboot
- BIOS finds hda, knows there's no hdb, goes on to
boot
- black screen, with
-list-
[EMAIL PROTECTED] On Behalf Of Kenneth Goodwin
Sent: Monday, August 04, 2003 11:18 AM
To: [EMAIL PROTECTED]
Subject: RE: GRUB failure
Otto -I think you are missing the big picture here and
Ashley can confirm it or
disprove me -
1 - this system had two IDE drives in it at Linux
To those of you, who have the theory that GRUB is
loading stage1
and can't load stage2 answer the question, how it can
find stage1 and
then can't find stage2?, when both are in the same
GRUB
directory. It
can not find the GRUB directory period.
BIOS loads and starts the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Aug 2003 12:26:05 -0400, Kenneth Goodwin wrote:
ASHLEY - Your grub issue may be that
grub-install may only install an already compiled and loaded
version of the
MBR phase one piece. YOU MAy have to do a GRUB Make to
rebuild the
BIOS loads and starts the code from master boot record,
but code in
MBR fails to load stage1.5 which is located at a fixed
position on
hda. At that point, GRUB does not even know about
directories yet,
since it is this later stage that would give native
access to ext2
fs. The
] On Behalf Of Kenneth Goodwin
Sent: Monday, August 04, 2003 11:51 AM
To: [EMAIL PROTECTED]
Subject: RE: GRUB failure
BIOS loads and starts the code from master boot record,
but code in
MBR fails to load stage1.5 which is located at a fixed
position on
hda. At that point, GRUB
I think this goes too far, and I don't see what it would
change.
IIRC, it has been mentioned that grub-install works
flawlessly when
slave drive is available and even when slave drive is
removed and
system is booted with bootdisk. However, the newly
written GRUB then
fails in MBR as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Aug 2003 13:39:54 -0400, Kenneth Goodwin wrote:
what I am saying is that the MBR may be crafted or rebuild
by anaconda for the two drive setup disk info.
It's grub-install/grub that creates stage1 based on the grub.conf
created by
Kenneth Goodwin wrote:
1 - this system had two IDE drives in it at Linux
installation time.
A (the MASTER) and B (The Slave), There is no SCSI, NO
RAID, no LVM. just a simple plain vanilla LINUX setup.
Nope. The machine had ONE drive upon installation. hdb wasn't
added till months
PROTECTED] [mailto:redhat-list-
[EMAIL PROTECTED] On Behalf Of Michael Schwendt
Sent: Monday, August 04, 2003 12:59 PM
To: [EMAIL PROTECTED]
Subject: Re: GRUB failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Aug 2003 13:39:54 -0400, Kenneth Goodwin wrote:
what I am saying
, 2003 1:25 PM
To: [EMAIL PROTECTED]
Subject: RE: GRUB failure
I have a dual boot system with HDA containing XP PRO and RH9 on HDB
GRUB
is the boot loader and it is written to the MBR or HDA along with the
XP
boot loader. I just removed HDB and guess what I got a black screen
with GRUB
Kenneth Goodwin wrote:
what I am saying is that the MBR may be crafted or rebuild
by anaconda
for the two drive setup disk info. Anaconda may not be able
to go
backwards here, may not be able to undo in a return to
single drive
configuration - most people add hardware, not remove it, it
may have
Otto Haliburton wrote:
I have a dual boot system with HDA containing XP PRO and RH9 on HDB GRUB
is the boot loader and it is written to the MBR or HDA along with the XP
boot loader. I just removed HDB and guess what I got a black screen
with GRUB in the left hand corner.
Welcome to my
Welcome to my world. At that point in the game, I doubt it even
knows about hdb, to even go find the config file. It read the MBR,
and
... fell off the planet.
--
You've never said (that I can remember ) what version of RH you are
running. If it is an old version then you may not
Otto Haliburton wrote:
You've never said (that I can remember ) what version of RH you are
running.
7.3
Also I want to note
that it is not a foregone conclusion that it calls stage1_5. So we
don't know how far it gets into the process, it seems it would print an
error message if it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 04 Aug 2003 12:33:26 -0600, Ashley M. Kirchner wrote:
Otto Haliburton wrote:
I have a dual boot system with HDA containing XP PRO and RH9 on HDB GRUB
is the boot loader and it is written to the MBR or HDA along with the XP
boot loader.
Sent: Monday, August 04, 2003 1:00 PM
To: [EMAIL PROTECTED]
Subject: RE: GRUB failure
This is why you need to read the manual. GRUB does know
the file
structures for the OS it boots the kernel for otherwise
it
chain loads
the boot loader for the other OS's. Remember what GRUB
stands
Michael Schwendt wrote:
If it doesn't print
an error message, it has loaded and jumped into stage2 either with
LBA or CHS geometry.
I'm curious, where does stage1_5 come into play, if what you're
suggesting is that it jumps from stage1 to stage2?
--
W | I haven't lost my mind; it's backed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 04 Aug 2003 13:06:19 -0600, Ashley M. Kirchner wrote:
If it doesn't print
an error message, it has loaded and jumped into stage2 either with
LBA or CHS geometry.
I'm curious, where does stage1_5 come into play, if what you're
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Aug 2003 15:03:08 -0400, Kenneth Goodwin wrote:
Phase 1.5 - Grub OS Loader Part one (OS filesystem
selector) Knows? os fs structures
That one would give considerably more status/error output,
in particular:
GRUB loading, please
what I am saying is that the MBR may be crafted or
rebuild
by anaconda for the two drive setup disk info.
It's grub-install/grub that creates stage1 based on the
grub.conf
created by anaconda.
Grub-install. which I have not seen admittedly, may
be based
on a MAKE environment
-Original Message-
From: [EMAIL PROTECTED] [mailto:redhat-list-
[EMAIL PROTECTED] On Behalf Of Michael Schwendt
Sent: Monday, August 04, 2003 2:12 PM
To: [EMAIL PROTECTED]
Subject: Re: GRUB failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 04 Aug 2003 13:06:19
Kenneth Goodwin wrote:
1 - this system had two IDE drives in it at Linux
installation time.
A (the MASTER) and B (The Slave), There is no SCSI, NO
RAID, no LVM. just a simple plain vanilla LINUX setup.
Nope. The machine had ONE drive upon installation.
hdb wasn't
: Monday, August 04, 2003 1:25 PM
To: [EMAIL PROTECTED]
Subject: RE: GRUB failure
I have a dual boot system with HDA containing XP PRO
and RH9 on HDB
GRUB
is the boot loader and it is written to the MBR or HDA
along with the
XP
boot loader. I just removed HDB and guess what I
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ashley
M. Kirchner
Sent: Monday, August 04, 2003 2:31 PM
To: [EMAIL PROTECTED]
Subject: Re: GRUB failure
Kenneth Goodwin wrote:
what I am saying is that the MBR may be crafted or
rebuild
by anaconda
for the two drive setup disk
Kenneth Goodwin wrote:
yOU DONT GET A BOOT time MESSAGE ABOUTING CHECKING FOR new
hardware?
That's kudzu's job, and it's been long removed. (So the answer to
your question is no, I don't.)
--
W | I haven't lost my mind; it's backed up on tape somewhere.
On Mon, 04 Aug 2003 13:06:19 -0600, Ashley M. Kirchner
wrote:
If it doesn't print
an error message, it has loaded and jumped into stage2
either with
LBA or CHS geometry.
I'm curious, where does stage1_5 come into play, if
what you're
suggesting is that it jumps
PM
To: [EMAIL PROTECTED]
Subject: Re: [RH List] RE: GRUB failure
Kenneth Goodwin wrote:
yOU DONT GET A BOOT time MESSAGE ABOUTING CHECKING FOR
new
hardware?
That's kudzu's job, and it's been long removed. (So
the
answer to
your question is no, I don't.)
--
W | I
Kenneth Goodwin wrote:
I thought Kudzu was replaced by Anaconda I dont recall
seeing it on my RH 8/9 systems
but I may have been asleep at the console at the time...
You skipped a post somewhere...the machine has 7.3 on it.
--
W | I haven't lost my mind; it's backed up on tape
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Aug 2003 15:40:53 -0400, Kenneth Goodwin wrote:
In stage1 source code, the next stage is called stage2. ;)
Now Mike, This is not Fair! You cant keep changing the
nomenclature
like this, It just confuses my poor little brain...
I thought Kudzu was replaced by Anaconda I dont recall
seeing it on my RH 8/9 systems
but I may have been asleep at the console at the
time...
You skipped a post somewhere...the machine has 7.3 on
it.
actually i missed all the early ones and said so.
I only jump in when
Kenneth Goodwin wrote:
Oh, BTW I skipped from 7.1 to 8.0 and rapidly from there to
9.0
I went 5.2 - 6.2 - 7.3 - and currently I have only one machine
that has 8 on it. None has 9...
--
W | I haven't lost my mind; it's backed up on tape somewhere.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Aug 2003 15:43:38 -0400, Kenneth Goodwin wrote:
I thought Kudzu was replaced by Anaconda I dont recall
seeing it on my RH 8/9 systems
but I may have been asleep at the console at the time...
Kudzu and Anaconda are two separate
Of Michael
Schwendt
Sent: Monday, August 04, 2003 4:12 PM
To: [EMAIL PROTECTED]
Subject: Re: [RH List] RE: GRUB failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Aug 2003 15:43:38 -0400, Kenneth Goodwin wrote:
I thought Kudzu was replaced by Anaconda I dont recall
seeing
They both are there trust me. In RH8/9
-Original Message-
From: [EMAIL PROTECTED] [mailto:redhat-list-
[EMAIL PROTECTED] On Behalf Of Kenneth Goodwin
Sent: Monday, August 04, 2003 2:44 PM
To: [EMAIL PROTECTED]
Subject: RE: [RH List] RE: GRUB failure
I thought Kudzu was replaced
PROTECTED]
Subject: RE: [RH List] RE: GRUB failure
They both are there trust me. In RH8/9
-Original Message-
From: [EMAIL PROTECTED] [mailto:redhat-list-
[EMAIL PROTECTED] On Behalf Of Kenneth Goodwin
Sent: Monday, August 04, 2003 2:44 PM
To: [EMAIL PROTECTED]
Subject: RE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Aug 2003 16:16:46 -0400, Kenneth Goodwin wrote:
I dont have the RH 7.2 version of
the grub source to look at. Might have 7.1 levels. The MBR
is probably the same.
If you have source - What does it do after printing out
GRUB, everything
Michael Schwendt wrote:
- is BIOS set to LBA?
Last I checked, it was.
- does grub-install with --force-lba work?
No errors.
- does LILO work?
Ain't trying that. The server is up and running as it should be,
and I can't take it down in the name of science right now.
--
W | I
If this hasn't been tried yet
the bioses don't all need/ want the drives to be set any way but master or
slave.
Ashley... try not changing the drive to single... leave it as the Master.
( as in don't change the jumper when removing the second drive)
the addressing of the drive
Kenneth... I feel Your on the right track here... you may have missed her
post where she said nothing was changed and went on to say she did
switch jumper positions... this changes same parts of the hardware
addressing. so a hard coded go there might not see what a bios call
brian davison wrote:
Ashley... try not changing the drive to single... leave it as the Master.
( as in don't change the jumper when removing the second drive)
No can do. hda has three settings on it: Master, Master w/ Slave,
and Slave. Since hdb was installed, it's been set to Master
Hi all,
We have all been ignoring one fact and that is for some reason
GRUB is loading part of the boot loader on the second drive. It
apparently thinks that linux is on the second drive. A setup where the
boot loader is on the MBR of drive A but linux is on drive B so that the
boot is
Otto Haliburton wrote:
Ashley while I believe you when you say that there
is nothing on drive B would you post a fdisk listing of partitions on
drive b.
You really don't believe me when I say there's -NOTHING- on the
drive, do you? How about this? I've actually killed everything,
including
: Re: GRUB failure
Otto Haliburton wrote:
Ashley while I believe you when you say that there
is nothing on drive B would you post a fdisk listing of partitions on
drive b.
You really don't believe me when I say there's -NOTHING- on the
drive, do you? How about this? I've actually
Otto Haliburton wrote:
What kind of disk contoller do you have and what
kind of computer system(manufacturer) is this computer.
I can tell you Monday when I get to the office and pull the specs on
the board. It's a (custom built) white box containing an Intel board.
One IDE bus, and 2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 3 Aug 2003 04:13:09 -0500, Otto Haliburton wrote:
We have all been ignoring one fact and that is for some reason
GRUB is loading part of the boot loader on the second drive.
Unfortunately, the shown grub.conf does not agree with
-Original Message-
From: [EMAIL PROTECTED] [mailto:redhat-list-
[EMAIL PROTECTED] On Behalf Of Michael Schwendt
Sent: Sunday, August 03, 2003 9:05 AM
To: [EMAIL PROTECTED]
Subject: Re: GRUB failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 3 Aug 2003 04:13:09
BTW the MBR is on HDA
-Original Message-
From: [EMAIL PROTECTED] [mailto:redhat-list-
[EMAIL PROTECTED] On Behalf Of Michael Schwendt
Sent: Sunday, August 03, 2003 9:05 AM
To: [EMAIL PROTECTED]
Subject: Re: GRUB failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 3
On Sun, 2003-08-03 at 02:27, brian davison wrote:
Kenneth... I feel Your on the right track here... you may have missed her
post where she said nothing was changed and went on to say she did
switch jumper positions... this changes same parts of the hardware
addressing. so a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 3 Aug 2003 09:28:56 -0500, Otto Haliburton wrote:
BIOS loads and starts the code from master boot record, but code in
MBR fails to load stage1.5 which is located at a fixed position on
hda. At that point, GRUB does not even know about
-Original Message-
From: [EMAIL PROTECTED] [mailto:redhat-list-
[EMAIL PROTECTED] On Behalf Of Michael Schwendt
Sent: Sunday, August 03, 2003 1:03 PM
To: [EMAIL PROTECTED]
Subject: Re: GRUB failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 3 Aug 2003 09:28:56
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 3 Aug 2003 13:13:46 -0500, Otto Haliburton wrote:
Knowing where the GRUB directory is doesn't have anything to do with
knowing where things are located. The MBR is in the 1st sector of the
drive we agree. Once GRUB is called it goes to a
thanks
-Original Message-
From: [EMAIL PROTECTED] [mailto:redhat-list-
[EMAIL PROTECTED] On Behalf Of Michael Schwendt
Sent: Sunday, August 03, 2003 1:39 PM
To: [EMAIL PROTECTED]
Subject: Re: GRUB failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 3 Aug 2003 13:13
This is excerpts from the GNU GRUB manual. The manual suggests that you
may have a problem with the device map in /boot/grub (this maybe where
it is located). It says that GRUB doesn't know how to translate from
bios disk to OS designations so it uses the device map in the grub
directory. So
Bret Hughes wrote:
Just curious what is in the device.map file? This is where grub assigns
device numbers used in grub.conf. I don't know if this is used in the
installation of grub on the mbr or after but since I don't remember
anything about this I thought I would ask. If it was posted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 1 Aug 2003 19:36:17 -0500, Otto Haliburton wrote:
Is your configuration a SCSI? If it is then there is a explanation
That wouldn't access the harddisk drives as /dev/hda and /dev/hdb,
respectively.
Btw, it would be great if you could trim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 1 Aug 2003 19:47:47 -0400, Kenneth Goodwin wrote:
Anyone know for certain who is printing out the INitial GRUB
message?
The MBR or phase two piece.
MBR (stage1) prints only GRUB because of space constraints. It has
only very few and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 1 Aug 2003 19:40:49 -0500, Otto Haliburton wrote:
There is also a explanation if the volumes are LVM or RAID.
No.
LVM is not available before the initrd is loaded and the kernel is
started. Same for Software-RAID. You boot from a physical
T.
-Original Message-
From: [EMAIL PROTECTED] [mailto:redhat-list-
[EMAIL PROTECTED] On Behalf Of Michael Schwendt
Sent: Saturday, August 02, 2003 2:31 AM
To: [EMAIL PROTECTED]
Subject: Re: GRUB failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 1 Aug 2003 19
.
-Original Message-
From: [EMAIL PROTECTED] [mailto:redhat-list-
[EMAIL PROTECTED] On Behalf Of Michael Schwendt
Sent: Saturday, August 02, 2003 2:31 AM
To: [EMAIL PROTECTED]
Subject: Re: GRUB failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 1 Aug 2003 19:36:17 -0500
]
On Behalf Of Otto Haliburton
Sent: Saturday, August 02, 2003 10:02 AM
To: [EMAIL PROTECTED]
Subject: RE: GRUB failure
This is a test message to see the format. Do not respond to this
message. It has already been sent.
HIII
On Fri, 2003-08-01 at 15:22, Ashley M. Kirchner wrote:
Recently I had to remove /dev/hdb from a server to get it replaced.
The OS is installed entirely on /dev/hda (including swap), and hdb was
a mere backup drive (it was actually added AFTER the server was
initially installed, up and
Michael Gargiullo wrote:
Can you post the output of df with hdb, and a copy of grub.conf?
This has never changed. It's been the same since the machine was
first installed (or last upgraded):
---
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 01 Aug 2003 13:22:57 -0600, Ashley M. Kirchner wrote:
Recently I had to remove /dev/hdb from a server to get it replaced.
The OS is installed entirely on /dev/hda (including swap), and hdb was
a mere backup drive (it was actually
Michael Schwendt wrote:
Give us a look at your /boot/grub/device.map and /boot/grub/grub.conf,
please.
cat /boot/grub/device.map
# this device map was generated by anaconda
(fd0) /dev/fd0
(hd0) /dev/hda
grub.conf was posted a moment ago.
--
W | I haven't lost my mind; it's backed up on
: GRUB failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 01 Aug 2003 13:22:57 -0600, Ashley M. Kirchner wrote:
Recently I had to remove /dev/hdb from a server to get it
replaced.
The OS is installed entirely on /dev/hda (including swap), and hdb
was
a mere backup drive
Barry Johnson wrote:
Just do a grub-install /dev/hda to reinitialize grub on the correct
partition and everything should be fine, KISS.
You'd think it'd be that easy. It wasn't. I did try that, and got
the same result. For some reason now, it absolutely must have an
/dev/hdb otherwise
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 01 Aug 2003 14:21:13 -0600, Ashley M. Kirchner wrote:
cat /boot/grub/device.map
# this device map was generated by anaconda
(fd0) /dev/fd0
(hd0) /dev/hda
grub.conf was posted a moment ago.
Interesting. I had hoped to find hd0
Let's analyze it. Grub needs the grub.conf file. You deleted hdb and
now Grub can't find the .conf file. So you need to do something that
points GRUB to grub.conf. So maybe you had a link or something else
that pointed GRUB to the .conf file.
On Fri, 2003-08-01 at 15:27, Ashley M. Kirchner
Otto Haliburton wrote:
Let's analyze it. Grub needs the grub.conf file. You deleted hdb and
now Grub can't find the .conf file. So you need to do something that
points GRUB to grub.conf. So maybe you had a link or something else
that pointed GRUB to the .conf file.
You're not reading
What I'm saying is that we know what the problem is and that is GRUB
can't find the .conf file period. Your solution lies in getting GRUB to
find the .conf file.
On Fri, 2003-08-01 at 15:45, Ashley M. Kirchner wrote:
Otto Haliburton wrote:
Let's analyze it. Grub needs the grub.conf file.
Michael Schwendt wrote:
Interesting. I had hoped to find hd0 and hd1 being swapped and GRUB
trying to access hda with the drive id of hdb. Provided that it is
not a hardware problem (master/slave configuration on hda), boot
with boot disk or rescue mode and run grub-install /dev/hda as
root. That
Otto Haliburton wrote:
What I'm saying is that we know what the problem is and that is GRUB
can't find the .conf file period. Your solution lies in getting GRUB to
find the .conf file.
And my question since the very beginning was: WHY? There is nothing
on hdb that should affect how grub
On Fri, 2003-08-01 at 15:55, Ashley M. Kirchner wrote:
Otto Haliburton wrote:
What I'm saying is that we know what the problem is and that is GRUB
can't find the .conf file period. Your solution lies in getting GRUB to
find the .conf file.
And my question since the very beginning
it actually try to boot?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ashley
M. Kirchner
Sent: Friday, August 01, 2003 4:45 PM
To: [EMAIL PROTECTED]
Subject: RE: GRUB failure
Otto Haliburton wrote:
Let's analyze it. Grub needs the grub.conf
]
[mailto:[EMAIL PROTECTED] Behalf Of Ashley
M. Kirchner
Sent: Friday, August 01, 2003 4:52 PM
To: [EMAIL PROTECTED]
Subject: Re: GRUB failure
Michael Schwendt wrote:
Interesting. I had hoped to find hd0 and hd1 being
swapped and GRUB
trying to access hda with the drive id of hdb
: Friday, August 01, 2003 4:45 PM
To: [EMAIL PROTECTED]
Subject: RE: GRUB failure
Otto Haliburton wrote:
Let's analyze it. Grub needs the grub.conf file. You
deleted hdb and
now Grub can't find the .conf file. So you need to do
something that
points GRUB to grub.conf. So
Kenneth Goodwin wrote:
Did ya change the master/slave jumper on the HDa drive to
single drive when you removed
the hdb drive by any chance? Is this a compaq by any chance
that would now prefer you switched to cable select? Does the
drive show up in the bios?
does it actually try to boot?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01 Aug 2003 15:51:02 -0500, Otto Haliburton wrote:
What I'm saying is that we know what the problem is and that is GRUB
can't find the .conf file period. Your solution lies in getting GRUB to
find the .conf file.
No, no, no. You haven't
The problem is, I have understood the problem. You can't boot when GRUB
can't find grub.conf. You can when it can. When you remove hdb GRUB
can't find the .conf file and that is why you can't boot. That's your
problem. You are trying analyze why it can't find that file and that is
your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 01 Aug 2003 14:27:48 -0600, Ashley M. Kirchner wrote:
Barry Johnson wrote:
Just do a grub-install /dev/hda to reinitialize grub on the correct
partition and everything should be fine, KISS.
You'd think it'd be that easy. It
You are getting GRUB when you boot because it is properly transferring
to the MBR, but when it tries to determine where to locate the kernel
image it can't fine the .conf file which tells it where that image is
located. If you added a string to the boot instruction telling it where
the .conf file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01 Aug 2003 16:41:17 -0500, Otto Haliburton wrote:
The problem is, I have understood the problem. You can't boot when GRUB
can't find grub.conf.
GRUB doesn't even come that far as was explained in the first
message.
If it booted into GRUB
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01 Aug 2003 16:46:29 -0500, Otto Haliburton wrote:
You are getting GRUB when you boot because it is properly transferring
to the MBR, but when it tries to determine where to locate the kernel
image it can't fine the .conf file which tells it
Did ya change the master/slave jumper on the HDa drive
to
single drive when you removed
the hdb drive by any chance? Is this a compaq by any
chance
that would now prefer you switched to cable select? Does
the
drive show up in the bios?
does it actually try to boot?
Again, you're not understanding the problem. When you boot you transfer
to the MBR which loads GRUB. GRUB then loads the config file and prints
the boot images and identifies to itself where the kernels images are
located. When you select one it transfers to that kernel image
location. Sines it
For you to solve this problem I think that you need to read what happens
when you boot. I'm not trying to insult you but from what you are
stating you don't understand how the computer boots and therefore what
happens in GRUB.
On Fri, 2003-08-01 at 16:52, Michael Schwendt wrote:
-BEGIN PGP
On Fri, 2003-08-01 at 16:52, Michael Schwendt wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01 Aug 2003 16:46:29 -0500, Otto Haliburton wrote:
You are getting GRUB when you boot because it is properly transferring
to the MBR, but when it tries to determine where to locate the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01 Aug 2003 16:56:58 -0500, Otto Haliburton wrote:
For you to solve this problem I think that you need to read what happens
when you boot. I'm not trying to insult you but from what you are
stating you don't understand how the computer boots
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01 Aug 2003 16:54:23 -0500, Otto Haliburton wrote:
Again, you're not understanding the problem. When you boot you transfer
to the MBR which loads GRUB. GRUB then loads the config file and prints
the boot images and identifies to itself where
1 - 100 of 123 matches
Mail list logo
