From: adrian15 <adrian15sgd@gmail.com>
To: Andrey Borzenkov <arvidjaar@gmail.com>,
The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: How to deal with fatal device seeks?
Date: Sun, 16 Mar 2014 19:40:45 +0100 [thread overview]
Message-ID: <5325F02D.1000806@gmail.com> (raw)
In-Reply-To: <5325E7D1.5020100@gmail.com>
I have digged the git log for partition related commits just in case you
might think that they have something to do with my problem
(From 2.00 release to current head on master branch).
I have tried to filter them. So I have removed the ones related with
strange table partitions or emulation code.
Here there are the commits:
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=e88f0420b90c2565637962754cc26fa8a4ed9256
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=4bad23a15fc129218f611f51dcb268c246b207f1
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=25fc51a87929262c1cc132bc29cc083ce98f0e0e
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=df6da5a52dc2ec424203c0f8001903435b177fa8
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=b7b78edb1ca05f30dd07ebed4bcb3d5a39aa5358
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=258f43b7d7bf4b03799b6cd3004b5372e082d01b
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=86d08fdb18b0142c1ce1b95db1aae989502956c5
Just hope that you, that deal with GRUB source code every day, can find
what might be the faulty commit so that I can test that the special
commit source code and reproduce it (or not to reproduce it).
Thank you for any idea!
adrian15
El 16/03/14 19:05, adrian15 escribió:
> El 16/03/14 18:16, adrian15 escribió:
>> If I try:
>>
>> ls (hd2,msdos5)/
>>
>> from a 2.00-15 system mkrescue image (Super Grub2 Disk 2.00s1-beta6) I
>> get:
>>
>> error: unknown filesystem.
>>
>> So, it's ok, because it is not a fatal error.
>> It would seem that somewhere between 2.00-15 and 2.02~beta2-7 (Debian
>> version) the bug arises.
>>
>> Or maybe the error was before because grub did actually to arise a FATAL
>> error and it didn't.
>
> 2.00-22 does not have the error.
>
> So it narrows the search between 2.00-22 and 2.02~beta2-7.
>
> adrian15
>
>> Thank you for any indication on how to make more tests.
>>
>> adrian15
>
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
next prev parent reply other threads:[~2014-03-16 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 5:26 How to deal with fatal device seeks? adrian15
2014-03-16 16:05 ` adrian15
2014-03-16 16:43 ` Andrey Borzenkov
2014-03-16 17:16 ` adrian15
2014-03-16 18:05 ` adrian15
2014-03-16 18:40 ` adrian15 [this message]
2014-03-16 22:19 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=5325F02D.1000806@gmail.com \
--to=adrian15sgd@gmail.com \
--cc=arvidjaar@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 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.