From: Robertm <robert.moeker@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: grub broken in IPFire upgrade from 85 to 87
Date: Fri, 20 Mar 2015 08:43:23 +0100 [thread overview]
Message-ID: <550BCF9B.303@ipfire.org> (raw)
In-Reply-To: <550BBCC0.7040103@dailydata.net>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
Hi Rod,
there are any differences in the grub.cfg.
Differences from the non working machine and the new working machine?
It would be nice if you could provide both configs
Am 20.03.2015 um 07:22 schrieb Rod Rodolico:
> I built a new router (core 85), loaded the config from the one that
> broke, then from the cli did the upgrade. It worked just fine. Same
> machine, same setup.
>
> I have no idea why the other one broke on upgrade, but attempting to
> replicate the issue did not work. I do still have the original image
> (the broken one) if it would be of any use.
>
> Rod
>
> P.S. thank you, whoever decided to do automatic backups when performing
> upgrades! That saved me.
>
> On 03/20/2015 12:20 AM, Rod Rodolico wrote:
>> I believe those are the correct versions. I upgraded the machine and now
>> get a grub error 15. I have no further information except the following:
>>
>> It is an HVM virtual, running on an LV (should not make a difference)
>>
>> To troubleshoot, I use kpartx to break it apart. When I mount the /boot
>> partition, I see grub.menu.old, then a grub/ directory. The config file
>> in the grub/ directory has none of the configuration options I expect.
>>
>> I have made a copy of the image in case anyone wants me to do anything
>> to it. Two other routers have worked just fine with this upgrade, but
>> they are not on an LVM partition?
>>
>> Anyone has any clues on what I should look for, let me know.
>>
>> Rod
>>
>
next prev parent reply other threads:[~2015-03-20 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 5:20 Rod Rodolico
2015-03-20 6:22 ` Rod Rodolico
2015-03-20 7:43 ` Robertm [this message]
2015-03-22 19:21 ` Rod Rodolico
2015-04-07 11:37 ` Michael Tremer
2015-04-07 21:09 ` Rod Rodolico
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=550BCF9B.303@ipfire.org \
--to=robert.moeker@ipfire.org \
--cc=development@lists.ipfire.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