From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] change grub_print_error to use stderr for the utils
Date: Sun, 17 Aug 2008 18:58:44 +0200 [thread overview]
Message-ID: <1218992324.4080.43.camel@fz.local> (raw)
In-Reply-To: <20080817163733.GB10862@thorin>
Am Sonntag, den 17.08.2008, 18:37 +0200 schrieb Robert Millan:
>
> If I understood correctly, nvidia's is a _software_ RAID solution which is
> implemented in Linux, in BIOS and in Windows (via non-native drivers), and
> is marketed as if it were hardware RAID.
Bah normally I even say myself to this `fake hardware RAID'.
But yes, this is neither a real hardware RAID controller nor like real
software RAID like mdraid on Linux.
> Anyway, this doesn't answer the question on where is this "out of disk"
> error issued, and why.
This is just from grub-probe -vv / where / is even on my IDE disk.
/home/fz/grub/grub2-1.96+20080816/kern/disk.c:368: Reading `hd1,2'...
/home/fz/grub/grub2-1.96+20080816/kern/disk.c:375: Read out of range:
sector 0x100f9b45 (out of disk).
/home/fz/grub/grub2-1.96+20080816/kern/disk.c:312: Closing `hd1,2'.
/home/fz/grub/grub2-1.96+20080816/partmap/pc.c:143: partition 2: flag
0x0, type 0x0, start 0x0, len 0x0
/home/fz/grub/grub2-1.96+20080816/partmap/pc.c:143: partition 3: flag
0x0, type 0x0, start 0x0, len 0x0
/home/fz/grub/grub2-1.96+20080816/kern/disk.c:312: Closing `hd1'.
error: out of disk
> > Oh I should have said in my case.
> > The BIOS presents GRUB only one (hd0) for the combined 2 disks.
>
> Ah, I see. Sounds like a very nasty situation. We'll probably need special
> logic at install time to sort this out? At least, just to skip raid.mod
> inclussion and use UUIDs for the rest.
Yes not very easy.
> Anyway, how is this related to the "out of disk" error?
The partiton table is for both disks.
It says there are 160 GB, but grub-probe sees only 2 80 GB one.
> > error: out of disk
> > Installation finished. No error reported.
>
> This "No error reported" seems to assume non-critical errors aren't
> possible. How about we remove that part of the message?
Yes, would be at least better and I don't have yet a different idea.
next prev parent reply other threads:[~2008-08-17 16:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 15:30 [PATCH] change grub_print_error to use stderr for the utils Felix Zielcke
2008-08-12 15:35 ` Felix Zielcke
2008-08-12 15:36 ` Vesa Jääskeläinen
2008-08-12 15:43 ` Felix Zielcke
2008-08-12 15:41 ` Robert Millan
2008-08-12 15:52 ` Felix Zielcke
2008-08-13 9:37 ` Marco Gerards
2008-08-12 16:54 ` Felix Zielcke
2008-08-13 9:38 ` Marco Gerards
2008-08-13 17:35 ` [RFC] " Felix Zielcke
2008-08-13 18:41 ` Marco Gerards
2008-08-13 19:14 ` Felix Zielcke
2008-08-14 7:07 ` Marco Gerards
2008-08-14 7:39 ` Felix Zielcke
2008-08-14 8:03 ` Marco Gerards
2008-08-14 8:05 ` Felix Zielcke
2008-08-14 17:54 ` Robert Millan
2008-08-14 18:57 ` Felix Zielcke
2008-08-16 15:06 ` Felix Zielcke
2008-08-17 15:07 ` Robert Millan
2008-08-17 15:24 ` Felix Zielcke
2008-08-17 15:34 ` Robert Millan
2008-08-17 15:47 ` Felix Zielcke
2008-08-17 16:37 ` Robert Millan
2008-08-17 16:58 ` Felix Zielcke [this message]
2008-08-17 17:04 ` Bean
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=1218992324.4080.43.camel@fz.local \
--to=fzielcke@z-51.de \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.