From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Bug#709097: grub-pc: Boot failure after updating to 2.00-14 - cannot find normal.mod, grub-rescue reports /boot empty
Date: Mon, 12 Aug 2013 11:54:44 +0200 [thread overview]
Message-ID: <5208B0E4.8000304@gmail.com> (raw)
In-Reply-To: <20130811135306.GL27110@riva.ucam.org>
On 11.08.2013 15:53, Colin Watson wrote:
> Control: retitle -1 misdetects FAT-overwritten-with-ext2 as FAT
> Control: severity -1 important
> This is a pretty specialised (hence the severity downgrade), but
> interesting, corner case. It appears that the partition in question
> used to be a FAT filesystem (specifically, a Dell Utility partition).
> It has been overwritten sufficiently that the fstype magic has been
> overwritten:
>
> 00000000 eb 54 90 00 65 6c 6c 20 38 2e 30 00 02 08 01 00 |.T..ell 8.0.....|
> 00000010 02 00 02 00 00 f8 86 00 3f 00 ff 00 3f 00 00 00 |........?...?...|
> 00000020 92 2a 04 00 80 00 29 1c 0a d9 07 44 65 6c 6c 55 |.*....)....DellU|
> 00000030 74 69 6c 69 74 79 00 41 54 31 36 20 20 20 10 00 |tility.AT16 ..|
>
How does something like that come into existence? Why would only part of
BPB overwritten? The tools that I know either overwrite whole sector or
don't touch BPB.
> Vladimir, could you elaborate on this? Which mkfs implementations were
> involved here?
>
AFAIR it was some FAT images that are commercially distributed. AFAIR
neither Windows nor Linux check this field.
> It seems questionable to me for GRUB to be quite this liberal. Perhaps
> we can restore its previous strictness somehow without breaking the
> filesystems that Vladimir ran into?
>
> Thanks,
>
next prev parent reply other threads:[~2013-08-12 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130520185519.5798.65190.reportbug@wormtail.bear-cave.org.uk>
2013-08-11 13:53 ` Bug#709097: grub-pc: Boot failure after updating to 2.00-14 - cannot find normal.mod, grub-rescue reports /boot empty Colin Watson
2013-08-12 9:54 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-08-12 18:30 ` Andrey Borzenkov
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=5208B0E4.8000304@gmail.com \
--to=phcoder@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).