From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Grub on a new disk
Date: Sat, 5 Jul 2008 22:14:19 +0100 [thread overview]
Message-ID: <200807052214.28298.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20080705183954.31fc875f@NOTE_GENTOO64.PHHEIMNETZ>
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]
On Saturday 05 July 2008, Florian Philipp wrote:
> On Sat, 5 Jul 2008 15:06:31 +0100
> Then I've installed grub into hda's MBR. Then something odd happened:
> Stage1.5 loads quiet fast but then Grub hangs once again of ~20sec
> with: "Grub loading, please wait ..."
>
> Since that is the moment when Grub accesses /dev/hdd for the first
> time, I think it could really be a problem with the hard disk, however,
> one that doesn't affect anything else. Maybe an automatic SMART
> self-test at boot-up? I'll investigate and as a workaround I'll get an
> SD-card or cheap USB-stick for Grub, since - unfortunately - the kernel
> is too big to fit on a floppy.
I know what I would have done - right from the start. Not used grub-install.
Not installed it in every single disk. Not installed it in any partition,
unless I intended to chainload separately the GRUB bootloader of the said
partition. Now, I know that this doesn't help and won't resolve your issue,
but perhaps next time . . .
I am not sure how GRUB goes about probing and reading boot sectors at boot
time. As I understand it at the time it is installed in an MBR, the position
of the grub fs is also written in there right after the boot code. At boot
time the boot code (stage1) jumps to the block device where grub's root fs is
stored to read and execute stage1.5 which can read the /boot device fs and
then read the stage2 files, which finally go and load the main OS kernel
image. Assuming this is correct, then what you have installed in the MBR of
hdb and hdd and the partition boot sector of hdd1 is irrelevant and it
*should not* make grub take so long.
That's the reason why I said something hardware-wise may be amiss, although I
can see that your checks and reasoning are sound.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-05 21:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 15:48 [gentoo-user] Grub on a new disk Florian Philipp
2008-07-03 22:04 ` Mick
2008-07-04 9:18 ` Florian Philipp
2008-07-04 10:11 ` Sebastian Günther
2008-07-04 11:12 ` Florian Philipp
2008-07-05 9:13 ` Florian Philipp
2008-07-05 11:18 ` Mick
2008-07-05 13:30 ` Florian Philipp
2008-07-05 14:06 ` Mick
2008-07-05 16:39 ` Florian Philipp
2008-07-05 21:14 ` Mick [this message]
2008-07-06 9:08 ` Mick
2008-07-06 11:43 ` Florian Philipp
2008-07-06 20:36 ` Dale
2008-07-20 8:52 ` Florian Philipp
2008-07-05 13:07 ` Alex Schuster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200807052214.28298.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox